Does ServiceStack work with .NET 4.5? - asp.net-mvc

Does ServiceStack work with ASP.NET MVC 5 and .NET 4.5? Calling the service from my ASP.NET MVC project. It appears System.Net, Version 5.0.5.0 is called by ServiceStack.Interfaces 3.9.60.0. I can't find System.Net, Version 5.0.5.0 while looking up references.

Related

System.Web.WebPages.Razor 3.0.0 missing

I would like to add reference to my ASP.NET MVC4 project, but in Add reference dialog (Assemblies->Extensions), there are only version 1.0 and 2.0 of System.Web.WebPages.Razor.dll
I have installed Visual Studio Professional 2013 and ASP.NET MVC4 from Web Platform Installer. What I am missing.
The web application does not work without this reference and complains that it cannot find System.Web.WebPages.Razor.dll 3.0
Razor 3.0 is only compatible with MVC 5. In your question, you stated that you are using MVC 4, which is only compatible with Razor 2.0.
So, the real question is, why are you trying to add Razor 3.0 to MVC 4? Either stick with Razor 2.0, or upgrade your project to MVC 5.
If you have a project dependency that was designed for MVC 5 (and Razor 3.0), you might be getting this error. The same advice goes for the dependency - either change it to use Razor 2.0 and MVC 4 (assuming you can make changes to it), or upgrade the project that requires the dependency to MVC 5.

Is servicestack MVC powerpack compatible with ASP.NET MVC 4?

I am currently using the servicestack powerpack (ServiceStackController) in an ASP.NET MVC 3 project but I am now considering upgrading to VS2012, .NET 4.5 and ASP.NET MVC 4. Has anybody tested whether the powerpack works with ASP.NET MVC 4?
Ok, I have tested it myself now and it seems to work fine.

Is MVC4 baked into .NET 4.5?

A lot of release notes for Visual Studio 2012 talk about .NET 4.5 and MVC4, but I can't tell if MVC4 is actually part of the .NET 4.5 release. Anybody know for sure? I would love not to have to install MVC separately on my server.
No, ASP.NET MVC 4 is baked into VS2012, exactly the same way ASP.NET MVC 3 was baked into VS2010 but not part of .NET 4.0 (there was a separate download that you could install on your servers). But there will also be a separate download of ASP.NET MVC 4 for VS2010 SP1 in which you obviously won't be able to use the .NET 4.5 specific features, such as async/await, but you will still be able to develop an ASP.NET MVC 4 application and target .NET 4.0.
ASP.NET MVC has made a point of NOT being tied to a particular .NET incarnation. That way, you can use the latest and greatest irrespective of what .NET version your hosting provider uses.
If the provider supports ASP.NET, that's all you need to know.
For this precise purpose, ASP.NET MVC is bin-deployable, meaning you can deploy the MVC dlls yourself, along your application - without requiring special rights from the hosting provider.
Phil Haack has a great article describing how to bin-deploy MVC3. There's even tooling support in VS for this scenario!
I assume the workflow for newer MVC incarnations is similar.

asp.net mvc 2 to mvc 4

I would like to update my project from:
ASP.NET MVC 2 with Entity Framework 4.
to
ASP.NET MVC 4 and Entity Framework 4.1
How can this be done?
You may take a look at the ASP.NET MVC 4.0 release notes which explain how to upgrade from an ASP.NET MVC 3 application. And the release notes of ASP.NET MVC 3.0 explain how to upgrade from ASP.NET MVC 2.
As far as upgrading from EF 4.0 to EF 4.1, it's as simple as updating the assembly reference. Of course if you wanted to do Code First approach you will have to make more extensive modifications.
Instead of doing it manually which will indeed take a lot of effort....why not check out my answer to a similar question and use ASP.NET MVC 3 Application Upgrader to go from MVC2 -> MVC3 and UpgradeMvc3ToMvc4 to go from MVC3 -> MVC4.

Integration from MVC2 .net 3.5 to MVC3 .net 4.0

Like to know what are the step need to do for integrating MVC2 .net 3.5 to MVC3 .net 4.0 without using any upgrading tool.
The only thing this should require is a .NET framework upgrade on the box serving IIS. Any MVC2 .NET 3.5 app should work seamlessly side-by-side with an MVC3 .NET 4.0 app.

Resources