MVC App Conversion.
I’ve been having issues upgrading VS2008 ASP.Net MVC1 projects to VS2010 ASP.Net MVC2. In short, it doesn’t work so great. OK. It’s really lame. There are two problems to address. The VS2010 solution file uses a different format plus we’re upgrading library references in the background. There’s more to it than that but you get the idea.
I had been creating a new project and sliding things over, but that sucks. So… I get lazy and work on my older projects in VS2008 and the newer ones in VS2010. Like I said, lame.
Basically, I ignore the issue.
(time passes)
For some unknown reason I felt compelled to look around for a solution this morning. What can I say, the Red Bull isn’t working. <yawn>
Anyway…
I found a nice, simple, and easy to use tool to solve my problem. Eilon Lipton’s has a MVC App Converter is available on his blog.
Cool.
But does it work?
I found an old/unused VS2008 MVC project, massaged the project with MVC App Converter, opened the solution in VS2010, upgraded the solution, and built it. No Joy.
Hmm… I had a handful of library errors related to System.Web.Abstractions. Time to look for warning icons in the references. Bingo. I needed to delete the old System.Web.Abstractions file and associate the newer version for my test project.
(NOTE: The problem was not in the MVC project. It was in the test project.)
Library reference updated.
Rebuild.
Success.
Run the tests.
All green.
Run the website.
Oy! I’ve got a running MVC2 project in under 3 minutes. Nice. Very nice.
For my (admittedly) simple MVC app, the tool worked like a charm. One reference update and I had a working app.
As always your mileage may vary.
Now, if I could just find a way to bang out this Excel 2003 VSTO app would building a new development VM from scratch… <yawn> I need another Red Bull.
