StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>This is a question that will have answers based off opinion so I suspect you will receive a few. I have not personally performed such a migration so this is only opinion but is how I would approach it. However, my recommended approach would be:</p> <ol> <li>Retain the existing application/ Given its current simplicity, creating a new app and moving existing items into it seems unnecessary.</li> <li>You should be able to use your existing auth solution via SimpleMembership and use ServiceStack.Razor. I would proceed as such however it does depend on what other ServiceStack features you may use which <em>could</em> cause conflict. A ServiceStack expert could comment more on this. Even if that did occur, you would be able to work around it relatively easy. At worst, implementing a simple handler would get around almost all issues from an authentication perspective.</li> <li>Working with different razor engines is relatively easy to do and you can use/enable/disable existing or new build engines via a few lines of code. See <a href="http://www.dotnet-tricks.com/Tutorial/mvc/NcJP200113-Custom-Razor-View-Engine-for-C" rel="nofollow">here</a> for an example. This should alleviate any concerns around dependencies of other built in or custom engines.</li> <li>Consider looking at ASp.Net 4.5.1/VS 2013 (since your project is in early days) as it has enhanced membership support and is moving to a more "less dependent" model of components via the Owin stack <a href="http://msdn.microsoft.com/en-us/library/hh420390%28v=vs.120%29.aspx" rel="nofollow">Asp.Net 4.5.1 and VS 2013</a>. Katana is a microsoft project that also provides some Owin based authentication components <a href="http://katanaproject.codeplex.com/" rel="nofollow">see here</a> and <a href="http://channel9.msdn.com/Shows/Web+Camps+TV/The-Katana-Project-OWIN-for-ASPNET" rel="nofollow">here</a> which you could use now and this would remove a lot of dependencies and enable you to migrate other framework with relative ease. Downside is that Katana/Owin has a little ramp up time/learning curve. Again, given your project is in its formative days I would recommend looking into Katana and the ASP.Net vNext stuff as this will make it easier for you and means you dont have to migrate to the new version once it is released.</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload