Migrate my visual studio projects from windows 7 to 10

Question

0.00/5 (No votes)

See more:

, +

I recently upgraded from windows 7 to windows 10. I also updated my visual studio from 2008 to 2013. I have two laptops connected, one with VS 2008 & Win7 and the other is VS2013 and Win10. On my win 10 laptop I have the VS installer which seems to migrate the projects fine from the old laptop to the new one.

I click on the solution file and the app upgrades the the .sln & .vbproj and it comes back with the warning...

'Project.sln: Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior.'

So when I go to VS I run the project and it says 'the source file is different from when the module was built.' & one of my private sub is not a member of the global system.

What I have tried:

The code works fine with the old laptop with VS2008 and Win7...It must be something different between the win 7 and 10. Or VS2008 to 2013

Posted 12-Dec-18 4:19am

BH2016

Updated 12-Dec-18 5:29am

Add a Solution

Comments

F-ES Sitecore 12-Dec-18 10:32am

Have you cleaned and re-built the solution?

BH2016 12-Dec-18 11:06am

What do you mean by cleaned

Afzaal Ahmad Zeeshan 12-Dec-18 12:46pm

You need to migrate the projects from an older VS to a newer VS. Windows has no connection in this aspect. :laugh:

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2018-12-12T05:30:00

Solution 1

Go to the Menu bar, and Select "Build ... Clean Solution" to remove all intermediate files - in theory you don't have to do this, but I'm a trusting soul.
The Go to "Build ... Rebuild Solution" to do a full rebuild (in theory, this starts with a "Clean", but as I said - I'm a trusting soul, but not that trusting.)

You problem should be gone.
If it isn't, manually go to the solution with Windows Explorer and navigate to each projects "Bin/Debug" folder and delete it. A full rebuild should now make new versions for you that are up to date.

Posted 12-Dec-18 5:30am

OriginalGriff

Comments

BH2016 12-Dec-18 11:53am

I have my project on a copy on my C drive so I am willing to try anything. I tried the clean and the rebuild and it came back with the same errors. 'The system cannot find the file specified.'

OriginalGriff 12-Dec-18 12:04pm

That's a different error: which file is it complaining about?

BH2016 12-Dec-18 12:32pm

Setup. The other errors are there too. Because the code was rebuilt this is a new error

OriginalGriff 12-Dec-18 12:42pm

OK, it's probably something external to the solution - a missing reference or similar.
Go back to the original lappy, and check ever project reference - are any of them non-standard DLL's which are not in your solution?

Now copy the original solution files onto the new one, and open it in VS. Check the references again. If any of them are to projects in the solution, go to that specific project and clean it, then rebuild just that project. when they are all done, clean and rebuild the whole project.

The chances are that either you have missing project references, or the file copy you did has changed the modification date on files so the make utility - which relies on them - is confused as sources are later than assemblies.

This isn't an easy one to help fix when you can't see the screen at all!

BH2016 12-Dec-18 15:19pm

I agree, it is most likely something where its referenced to somewhere that changed from going from version to version. I just dont understand how it doesnt just work if its the same correct code just on a different version of vs and windows. The only error i get when I first try the code is

'Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior.'

BH2016 12-Dec-18 15:38pm

But when you get in the code there are three identical errors in the three sub menus under my project that all end in .xsd. Each has one error looking at a variable that is 'not a member of '<default>'.'

BH2016 12-Dec-18 15:49pm

UPDATE: I looked online for help and it said just delete the global...line of code and I did and now those three errors are gone... One is left and it is a bigon.

An unhandled exception of type 'System.InvalidOperationException' occurred in MinsterCalibration.exe

Additional information: An error occurred creating the form. See Exception.InnerException for details. The error is: Could not load file or assembly 'NationalInstruments.UI.Styles3D, Version=13.0.35.242, Culture=neutral,
PublicKeyToken=18cbae0f9955702a' or one of its dependencies. The system cannot find the file specified.

The line of code it points at is 'Me.MainForm = Global.MinsterCalibration.LinearCalibrationUI'

OriginalGriff 13-Dec-18 4:19am

So try removing the reference and adding it back in - chances are the assembly is not installed on the new machine.

BH2016 13-Dec-18 17:07pm

I think this will work since between the vs2008 and vs2013 the references changed so Im going to rerout them to the correct file and see. Will update