Migrating ASP.NET MVC 2 applications to ASP.NET MVC 3 Preview 1

21 Comments

• Successfully converted to MVC 3.
  Though status text is slightly disappointing:)
  
  "The project was successfully converted
  The solution was successfully converted to ASP.NET MVC 2"
  

• Hi Sergey,
  
  I think I uploaded an old version of the tool by mistake! I changed the ZIP to be the updated version.
  
  Thanks for the report!
  

• Worked fine except for one of the project on my solution, which was targeted to .NET 3.5 so the added reference was not found, since MVC 3 is targeted to .NET 4. Just updated the target framework and worked fine.
  Thanks a lot :)
  

• strongly typed views are having issues thinking the Model is of type object getting
  'object' does not contain a definition for ...
  
  I used the converter but this is busted ... all in web.config looks on the up and up. Anyone else?
  

• @Phil
  
  >>>>>>>> strongly typed views are having issues thinking the Model is of type object getting
  >>>>>>>>
  >>>>>>>> 'object' does not contain a definition for ...
  >>>>>>>>
  >>>>>>>> I used the converter but this is busted ... all in web.config looks on the up and up. Anyone else?
  
  Are you having issues with strongly-typed views with the WebForm view engine or the Razor view engine? There may have been a bug in the WebForm view engine that we just recently fixed. I think there was also a small bug in the Razor view engine that we also just recently fixed.
  
  If you can share the file that isn't working we'll take a look.
  
  Thanks!
  

• Compilation Error
  Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
  
  Compiler Error Message: CS1061: 'object' does not contain a definition for 'SetDate' and no extension method 'SetDate' accepting a first argument of type 'object' could be found (are you missing a using directive or an assembly reference?)
  

• @TRS
  
  Can you share some more details about the code that you have that is experiencing the compilation error? One possibility is that you have an item that is declared as 'dynamic' (possibly by using a strongly-typed view page that has its model declared as 'dynamic') and you then try to call an extension method on it. Extension methods are supported only by the compiler itself and not by dynamic objects at runtime.
  
  If that's the case you'll have to either declare the page as the proper strong type (e.g. a "Customer" model type), or case the object to the correct type and then call the extension method.
  
  Thanks,
  Eilon
  

• I followed your instructions. It worked! Thanks!!
  

• The MVC 3 Preview 1 ViewTypeParserFilter was unable to handle a partial view declared like this:
  
  <%@ Control Language="C#" Inherits="System.Web.Mvc.ViewUserControl" %>
  
  I recompiled it with a modified source, basically using the MVC 2 RTM source for ViewTypeParserFilter (the only change was using IMvcControlBuilder in ParseComplete), and after that it worked.
  

• @CJ
  
  Is this the same issue as the one reported on the following StackOverflow post?
  http://stackoverflow.com/questions/3516130/upgrade-mvc-2-to-mvc-3-issues-with-views
  
  If so then we've identified the issue and it will be fixed for the next preview. Sorry for the inconvenience!
  
  Thanks,
  Eilon
  

• @Eilon
  
  Yes, I believe it's the same bug. No worries, though, after all it's the first preview! :-) As such, it's very stable.
  
  By the way, how often do you plan on releasing previews? Whenever you feel you have something that is interesting enough and sufficiently stable, or on a more scheduled basis?
  

• @CJ
  
  We generally do previews roughly every 6 - 8 weeks, which gives us a comfortable enough amount of time to get new features, bug fixes, and other improvements in. We have a lot of existing stuff in the pipeline so stay tuned! :)
  

• @mike -
  
  If you're using ASP.NET MVC 3 Beta then you might be running into a bug that wasn't caught in time.
  
  To work around the bug you'll need to make sure you have these two items in your ~/web.config file:
  
  
  
  
  
  
  This should disable some new features that weren't supposed to be enabled by default in MVC 3. These flags won't be necessary with the next release.
  
  Thanks,
  Eilon
  

• Regarding the issue: 'object' does not contain a definition for ...
  
  Just add inyour web.config:
  
  
  
  
  
  

• Nice tool. Is it possible to add an indication as to whether the targetted file is Read-Only?
  
  Thanks,
  
  Mike
  

• fyi, I have a SQL database in App_Data that caused the backup to barf (file was in use). I elected to "Continue" with the installation but it aborted anyway. The solution was to detach the database so the backup could do its thing. Thanks and looking forward to working the MVC 3!
  

• I converted the mvc 2 application with the tool, and I am getting the error, in production server, [Could not load file or assembly 'System.Web.Mvc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified].
  
  I have upload the mvc 3 application in a subdomain before upload it in main domain.
  
  I checked the web config, and nowhere has the version 2.0.0.0.
  
  I would appreciate any suggestion.
  
  Thanks
  

• SOLUTION
  
  I change the to
  
  Thanks
  

• Tried to manually do this a few times but could never seem to quite get it. Ran this tool and had my app converted with no problems. Thank-you!!!
  

• Any chance of getting the source code? We want to produce a command line tool that just converts lots of web.configs.
  

• @Shuval - We'd like to release the source code at some point, but for now feel free to use a tool such as Reflector to extract the code and then reuse it in any way you like.
  
  The latest version of the binaries is available here: http://aspnet.codeplex.com/releases/view/59008
  
  Thanks,
  Eilon