what steps should I perform in order to run asp.net mvc 1.0 web application on mono?
It requires the same steps as for 3.0.
minus
System.Web.Razor.dll
System.Web.WebPages.Razor.dll
But why do you even want to run a 1.0 application, when 4.0 works already ?
Here:
Does the Razor View Engine work for Mono?
Related
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.
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.
We have an ASP.Net MVC 1.0 solution developed using Visual Studio 2008 and .net Framework 3.5SP1.
We would now like to upgrade Visual Studio to 2010.
If we just open the solution in VS 2010 and do not change the framework version, can we just continue to develop as before?
If we open the solution in VS 2010 and change the framework version to 4.0, will we automatically start using ASP.Net MVC 2.0, or will it continue to use ASP.Net MVC 1.0?
Is there anything we need to take into consideration when upgrading to ASP.Net MVC 2.0?
Thanks
Shiraz
Yes.
I don't know if this is supported, but I wouldn't go there. It would make more sense to update to MVC 2 first, then .NET 4.
Yes, lots. Look at the release notes on CodePlex. Many things have changed, including model binding, TempData handling, and the return types of HTML helpers. These are breaking changes. There's a wizard which tries to help, but you're going to have to fix some of this manually.
It will continue using ASP.NET 1.0 unless you run the tool to upgrade to 2.0. If I am not mistaken, all the tool does is update your web.config to point all MVC references to 2.0 instead of 1.0
I'm trying to migrate from ASP.NET MVC2 Priview 2 to MVC2 RC, because new version of Telerik is enforcing it.
I had big problems while migrating from MVC 1.0 to MVC 2.0 Preview 2, so I wanted to confirm with you guys before continuing.
Has anyone migrated from Prev2 to RC? Was there any problems? Are they easy to solve?
Any suggestions are greatly welcome.
Thanks.
Changes in ASP.NET MVC 2 RTM
No new breaking changes were introduced by the ASP.NET MVC 2 RTM release.
Changes in ASP.NET MVC 2 Release Candidate 2
Every property for model objects that use IDataErrorInfo to perform validation is validated, regardless of whether a new value was set. In ASP.NET MVC 1.0, only properties that had new values set would be validated. In ASP.NET MVC 2, the Error property of IDataErrorInfo is called only if all the property validators were successful.
Changes in ASP.NET MVC 2 Release Candidate 1
IIS script mapping script is no longer available in the installer
The IIS script mapping script is a command-line script that is used to configure script maps for IIS 6 and for IIS 7 in Classic mode. The script-mapping script is not needed if you use the Visual Studio Development Server or if you use IIS 7 in Integrated mode. The scripts are available as a separate unsupported download on the ASP.NET CodePlex site.
The Html.Substitute helper method in MVC Futures is no longer available
Due to changes in the rendering behavior of MVC view engines, the Html.Substitute helper method does not work and has been removed.
(See the Release Notes here for more information)
i need to have one project on asp.net mvc 1 but i want to upgrade for another project. is this possible?
Yes you can. See Scott Guthrie's blog for more information.
ASP.NET MVC 2 can be installed
side-by-side with ASP.NET MVC 1
(meaning you can have some apps built
with V1 and others built with V2 on
the same machine). We have
instructions on how to update your
existing ASP.NET MVC 1 apps to use
ASP.NET MVC 2 using VS 2008 here.
Note that VS 2010 has an automated
upgrade wizard that can automatically
migrate your existing ASP.NET MVC 1
applications to ASP.NET MVC 2 for you.