This project is read-only.

How do I install the db?

May 26, 2009 at 1:46 PM

I ran the scripts in the Setup folder but the Mvc site in the Oxite folder errors when I start it up.

 

Server Error in '/' Application.

Invalid column name 'SkinsPath'.
Invalid column name 'SkinsScriptsPath'.
Invalid column name 'SkinsStylesPath'.
Invalid column name 'Skin'.
Invalid column name 'AdminSkin'.

 

What am i doing wrong?

May 26, 2009 at 5:37 PM
Is this from the latest release or the latest source code checkin?

(sent from WinMo 6.1 phone)


From: CVertex <notifications@codeplex.com>
Sent: Tuesday, May 26, 2009 5:46 AM
To: Erik Porter <Erik.Porter@microsoft.com>
Subject: How do I install the db? [oxite:57472]

From: CVertex

I ran the scripts in the Setup folder but the Mvc site in the Oxite folder errors when I start it up.

Server Error in '/' Application.

Invalid column name 'SkinsPath'.
Invalid column name 'SkinsScriptsPath'.
Invalid column name 'SkinsStylesPath'.
Invalid column name 'Skin'.
Invalid column name 'AdminSkin'.

What am i doing wrong?

May 27, 2009 at 3:03 AM
Edited May 27, 2009 at 3:47 AM

I think this is from a recent checkin.  I saw the same thing when using the latest code as of this past weekend.  I thought that what was checked in would be working as well.  Is there any thought about how contributions could be allowed for this project?  Many people could help with this kind of work, at least.  Does someone need to fork it?  Would the current contributors be ok with that?  To the degree of switching their contributions to the forked version?

 

May 27, 2009 at 3:47 AM

Hi Erik,

 

I took my version from the latest svn.

CV

Jun 3, 2009 at 11:52 PM

@CVertext

Yah, we don't keep the install/update scripts up to date with the current checkins.  We do keep OxiteSite/App_Date/Oxite.Database.mdf pretty much in sync with the current schema so you can connect to that file to test things out.

@harpreet

We can take contributions from those who sign an agreement and show that they'd be dedicated to the project and have good things to contribute (as in, you have to prove it to us  :)).  What would you like to contribute?

Jun 4, 2009 at 3:56 AM

That's great that there's at least some way to contribute.  I assume from your response that you wouldn't be able to contribute to a forked (more open) version. Is that right?  I'm not sure if I would meet your standards for quality of contributions but I'll tell you what change/contribution was on my mind when I asked the question.  It may be that the change I'm thinking of will not matter once you are done with all your recent changes of creating a plugin system.  

At the time, I wanted the view that displays a single post to maintain the sidebar as it is shown on the home page.  (I'm speaking here of the default skin).  I noticed that you were using an Html.RenderPartial to create that sidebar but when an individual post was shown the Model for that partial view didn't have what it needed to render the sidebar in the same way.  I wanted to use the MVC contrib and add in the subcontroller functionality so that indivdiual partial views could exist with their own logic or ability to independently get whatever Model they needed. Basically an Html.RenderAction instead of Html.RenderPartial but using the MVC contrib project to accomplish this.  Like I said, your recent work with plugins may make this completely unnecessary.   At least I can imagine a plugin approach as an alternative (and likely) better strategy.

I'd still be interested in contributing but there's no way for me to know if I would meet your quality expectations or if you expect some minimum weekly time commitment.

 

Jun 4, 2009 at 5:48 AM

So I may have gone overboard on making it sound like there's a super high bar to "get in" to contribute to Oxite.  There's not.  What I'm trying to get across is that we need to be able to understand you or anyone as a potential contributor.  We want to keep the "party" small and tight with people of varied talents, ideas and time they can spend on it.  All you or anyone needs to do is help us gauge what you would bring as a contributor.  Go off and run Oxite as your blog (or don't...not a requirement) and built some things for it.  Modify it in a cool way and say "hey, you guys should do it like this" or "look what I added" or show off something cool in Oxite to the world and get people jazzed about it.  Get our attention.  :)  That's how you or anyone can become a contributor.

Regarding your idea, it's definitely a good one.  A few other people have brought up wanting to see the sidebar rendered on all pages.  It's tricky on the "best" way to accomplish that however.  The easiest is to just go into the controller action and stuff the data into the model that you need, then use it in a modifies skin.  That way doesn't scale to new versions of Oxite though.  There is a more extensible way that won't break in future versions of Oxite, but it's a bit complicated at the moment.  If you go into our source tree and grab /Implementations/MIXVideos you can get an idea of how we did custom work for the skin it uses by looking at the Oxite.MIXVideos project.  You'll find some filters that do some extra work and stuff other data into the model.  Those filters are then registered on specific controller actions in a filter registry class.  That class is then registered with the container in the web project so it will get loaded after Oxite's main filter registry does.  You could use this same pattern to accomplish getting other data down for the sidebar.

You would think plugins would be perfect for this, but that type of thing isn't our goal with plugins.  We have something else we're working on (that will come after plugins, but still in the next release with plugins) we're calling modules (how original, huh?  :P).  The goal of plugins is to enable anybody to easily (with a few lines of code) build some code that will do something useful based on events in the Oxite pipeline and also be able to display UI at key places in the app.  Good examples of the things we're trying to enable with plugins are things like "insert my xbox gamercard or twitter stream in the sidebar of the homepage" or "add share links after the post body on permalinks" or "tweet new posts that get published" or "spam filtering and adding UI on comments to allow people to report spam", etc.  Very simple and very limited (on purpose).  The target audience for plugins are breadth developers, meaning those who toy with code.  This ranges from people who write macros in Excel to people who build WordPress themes or plugins to professional developers.  The goal of modules is to allow developers access to the entire Oxite and MVC pipeline to realy customize how Oxite works without touching our code and keeping it fairly future proof.  Building forums or social networking support or new authentication schemes into Oxite are good examples of modules.  The target audience for modules is professional .NET developers.

Let me know if you have any other questions.