I know this is a strange question, please do not flame me :)
I have An existing ASP.NET MVC3 (Net Framework 4) application is required to "downgrade" to Aspen MVC2 (Net Framework 3.5) because our shared hosting provider does not support Net 4 (I know it's crazy But the idea is that in retail and the first beta came out in May 2009, from 12 April 2010 The following is not the point of the post).
Can any device, or guide or process help? I'm losing a bit because I upgraded many applications but I never had to downgrade
In addition to strict MVC, I am using a data layer with EF code (probably nhibernate would be the best tool
thanks
Edit : Hosting is changing The provider is not an option, otherwise I can not post it at all. I am personally against this downgrade - I fully I think silly - but still this is the only option. I will replace the hosting provider if your provider does not support .NET 4.0, then do you really want to build a long-term relationship with them? What is the next great new feature How long will it take to implement it? I do not think there is a future there, if they provide such a service. By saying this, if you have an option to stay with them I do not think so The only option is For my web.config file I will create a new MVC 2 project and will work from that web site. Required settings from your old config. Based on the size of the project it is clearly going to be a huge task
Comments
Post a Comment