MVC 3 Project Upgrade Tool

re: MVC 3 Project Upgrade Tool

Tony — Sun, 29 Jul 2012 09:11:24 GMT

@Nick. Try to download Process Monitor fra SysInternals. It can help you troubleshoot why you get an access denied.

re: MVC 3 Project Upgrade Tool

Nick — Wed, 27 Jun 2012 18:46:58 GMT

I got an erro while converting from mvc2 to mvc3 and i can't do te conversion is there any alternate way to do that.?

"Access to the path 'C:\Portal\Portal\Scripts\jquery-1.4.4.min.js' is denied."

re: MVC 3 Project Upgrade Tool

Chris Keeble — Sat, 14 Jan 2012 15:04:32 GMT

In case of any help to others...

The TagBuilder class has moved, so to resolve missing assembly reference, add a reference to:

System.Web.WebPages

(Found in Assemblies -> Extensions)

re: MVC 3 Project Upgrade Tool

Chris Keeble — Sat, 14 Jan 2012 14:45:01 GMT

Hi Marcin,

Thanks for your reply - and my apologies for not having spotted the issue in your limitations section.

I have since successfully upgrade, by removing the projects from Solution Folders and adding them directly to the solution. I didn't need to move them physically, just add the references again of course, and the upgrade has worked perfectly.

Thank you!!

Kind regards

Chris

re: MVC 3 Project Upgrade Tool

Marcin Doboz — Fri, 13 Jan 2012 17:56:34 GMT

Chris, at the end of this post I list some limitations of the tool. One of them is "Solutions with project files outside of the solution folder might cause problems". So yes, this is a known issue. One workaround that should work is to move the project so that's under the folder that contains the .sln file. Another would be to create a new temporary .sln file (in the directory above the project directory) and add a project to it.

re: MVC 3 Project Upgrade Tool

Chris Keeble — Fri, 13 Jan 2012 17:40:22 GMT

We have a solution which fails with the following error, I've replaced specific project and directory name with ProjectA and OurCompany, but otherwise this is exactly as is...

ERROR: There was an error loading the solution file

Could not find a part of the path 'C:\DefaultCollection\ProjectA\OurCompany\OurCompany.Framework-ProjectA\OurCompany.Framework\OurCompany.Framework.csproj'.

When I open the ProjectA solution in VS, the OurCompany.Framework project is located in a solution folder called Framework.

(To note, OurCompany.Framework is a branch of the Framework, specific to ProjectA.).

I imagine it was set up like that so that the dependent project (Framework) could sit outside the solution structure, though I think it's awful, and the developers that set this up are no longer with us to ask, so I may be wrong.

The solution I'm trying to convert is

C:\DefaultCollection\ProjectA\ProjectA\ProjectA.sln

It would appear that the Upgrade Tool is misunderstanding the relative paths, and considering the Solution Folder (Framework) as a true sub-folder of ProjectA incorrectly.

Is this a bug? Is there a workaround?

I'm guessing I need to remove the Framework project from the solution and add it back without the Solution Folder, but am keen to hear your thoughts / suggestions?

Many thanks in advance,

Chris

re: MVC 3 Project Upgrade Tool

Marcin Doboz — Fri, 24 Jun 2011 20:13:49 GMT

Fernando, your problem does not appear to be related to the upgrade tool itself.

forums.asp.net/.../1 is an excellent venue to ask such questions.

re: MVC 3 Project Upgrade Tool

Fernando — Fri, 24 Jun 2011 20:02:59 GMT

use the helper Html.Serialize in one of my views, to serialize an object, and then I deserialize it again in my Controller using the MvcSerializer like this:

(RegistrationViewModel) new MvcSerializer().Deserialize(serializedObject); This worked fine before, but after upgrading to MVC3 (And MVC3 Futures) The Deserialize method has changed so that it now has one more parameter: SerializationMode.

This I can set to either Signed or EncryptedAndSigned.

Regardless of which of these I use, I get an SerializationException asking me to verify that the data was serialized with the same mode I'm trying to deserialize with.

In my view, for some reason IntelliSense is not working for the Serialize method, so I don't know if this has gotten any additional overloads as well.

But the question is quite simply: How can I now, in MVC3, deserialize the data inside my controller that I have serialized inside the View with Html.Serialize?

re: MVC 3 Project Upgrade Tool

Fernando — Fri, 24 Jun 2011 19:22:51 GMT

I get the error

Deserialization failed. Verify that the data is being deserialized using the same SerializationMode with which it was serialized

re: MVC 3 Project Upgrade Tool

Marcin Doboz — Mon, 21 Mar 2011 19:41:26 GMT

Shawn, for now you would have to move your project closer to the root directory to achieve shorter file names. We will look at addressing this in the future. Sorry for the inconvenience.