4

I know this is a rather odd question, please don't flame me :)

I have a concrete need to "downgrade" a current Asp.Net Mvc 3 (net framework 4) application to Asp.Net Mvc 2 (net framework 3.5) because our shared hosting provider does not support .Net 4 (I know it's crazy considering it's been in retail since 12 Aprli 2010 and first beta came out in May 2009 but it's not the point of the post).

Is there any tool, or guide, or anything that could help in the process? I'm getting a bit lost because I upgraded many applications but I never had to downgrade one.

Besides strictly MVC, I'm using a data layer with EF Code First (maybe nhibernate will be the best tool to replace that?)

Any help, tip, info, whatever is appreciated.

Thanks.

EDIT: Changing hosting provider is not an option, otherwise I wouldn't have posted this at all. I personally am against this downgrade - I find it totally senseless - but still it's the only option.

Andrew Orsich
  • 52,935
  • 16
  • 139
  • 134
Matteo Mosca
  • 7,380
  • 4
  • 44
  • 80

3 Answers3

5

I would change hosting provider. If your provider is not supporting .NET 4.0 now then do you really want to build a long term relationship with them? What happens the next new great feature is released, how long will they take to implement that? I don't think there's any future there if that's the kind of service they provide.

Saying that, if you have no choice but to remain with them, then I think your only option is to

  1. Change the project's target framework setting in Visual Studio to 3.5.
  2. Remove MVC 3 and add MVC 2
  3. Change all Razor views to the Web Forms view engine syntax
  4. Recompile and work through all the errors

For your web.config file I would create a new MVC 2 project and work from that web.config copying any extra settings needed from your old config.

Depending on the size of the project this is obviously going to a be a big task.

David Glenn
  • 24,412
  • 19
  • 74
  • 94
  • While I totally agree that such an hosting provider isn't reliable or professional at all, my company won't change it. Because we have dozens of websites hosted and "it would cost too much and take too much time to migrate everything". I know we could have 2 different providers (new stuff and old stuff) but they are totally against it. As I was negated to use Mercurial for new stuff because old stuff is on SVN and "we can't have 2 different versioning systems and we can't migrate everything". – Matteo Mosca Mar 28 '11 at 10:35
  • Ok, then it's manual update I'm afraid. If it's a big project using Razor with `dynamic` peppered everywhere then it's obviously going to be a big task. If your using the Web Forms view engine and don't really use `dynamic` then it may not be so bad. – David Glenn Mar 28 '11 at 10:46
  • It's using razor with ViewBag, so I'm doomed. – Matteo Mosca Mar 28 '11 at 10:52
2

The only way I can think of is to get a machine with MVC 2 installed, get the project and try to compile it targeting .NET 3.5.

This will generate lots of errors.

Actually - this might be the way to convince those that hold the purse strings that you need to change hosting provider. You can show them the error list and put an estimate on how long it will take to fix them. If this is a long time (a couple of weeks?) then it might be more cost effective to move.

ChrisF
  • 134,786
  • 31
  • 255
  • 325
0

You can convert asp.net 4.0 website to asp.net 2.0 easily

  1. Just make a new website
  2. Then Select .net Framework 2.0
  3. Copy the all files except web.config file from your asp.net 4.0 website folder in the new website folder
  4. remove the unused usings from all the .vb or .cs files
  5. Run the website easily
Blazemonger
  • 90,923
  • 26
  • 142
  • 180
Usman
  • 9
  • 1
  • My I read this only now, after a whole year and a half, it looks like you didn't even bother to read my question, and if you did, you clearly don't even know what I'm talking about. Downgrading an MVC project in both .Net version and Mvc version is no trivial task. You'd better check David Glenn answer as he nailed it quite well. – Matteo Mosca Dec 28 '12 at 15:49