Microsoft Visual Basic 2010 Express to 2008.
- Thread starter Number_25
- Start date
1. Make back up of your .sln file
2. Open your VS 2010 .sln in notepad.
It should look something like this:
Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{FAE04EC0-3 ......
...........................
3. Change the Version 11.0 to Version 10.0 and Visual Studio 2010 to 2008
It should look something like this:
Microsoft Visual Studio Solution File, Format Version 10.00
# Visual Studio 2008
Project("{FAE04EC0-3 .....
..........................
4. Save the file.
5. Open in vs 2008 all projects should load, compile etc.
Source:
http://social.msdn.microsoft.com/Fo...s/thread/4345a151-d288-48d6-b7c7-a7c598d0f85e
Hope this helps
2. Open your VS 2010 .sln in notepad.
It should look something like this:
Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{FAE04EC0-3 ......
...........................
3. Change the Version 11.0 to Version 10.0 and Visual Studio 2010 to 2008
It should look something like this:
Microsoft Visual Studio Solution File, Format Version 10.00
# Visual Studio 2008
Project("{FAE04EC0-3 .....
..........................
4. Save the file.
5. Open in vs 2008 all projects should load, compile etc.
Source:
http://social.msdn.microsoft.com/Fo...s/thread/4345a151-d288-48d6-b7c7-a7c598d0f85e
Hope this helps
In VS2010, what version of .NET are you using?
If using 4.0, you will need to change it to 3.5, because VS2008 does not recognise .NET 4.0.
Also, my understanding is that VS2010 uses a different method to store and name its files. Have a search on the internet and look for a program which can do the conversion for you.
In total, you have 15 errors, which is nothing. I remember, when I converted my VB.NET project to C#.NET, I had to correct around 1500 errors. It took me about 1-2 weeks, before I could try out my program, using C# code.
One thing I dislike about schools/colleges is their reluctance to teach the bleeding edge stuff and hanging on to older languages/programs/software. In 2008, you are missing the use of Threading.Task...which is something I use on an almost daily basis now and makes the programming of multi-threads so much more easier.
I remember, back in 1995, we were being taught Fortran77....I mean seriously, what the hell?
BTW: Why are you using VB and not C#? If you look at the job market, there are plenty more jobs in C# than in VB, for this reason, I would much rather learn .NET programming in C# than in VB. Even though they are similar in syntax and methods, C# does differ from VB.
If using 4.0, you will need to change it to 3.5, because VS2008 does not recognise .NET 4.0.
Also, my understanding is that VS2010 uses a different method to store and name its files. Have a search on the internet and look for a program which can do the conversion for you.
In total, you have 15 errors, which is nothing. I remember, when I converted my VB.NET project to C#.NET, I had to correct around 1500 errors. It took me about 1-2 weeks, before I could try out my program, using C# code.
One thing I dislike about schools/colleges is their reluctance to teach the bleeding edge stuff and hanging on to older languages/programs/software. In 2008, you are missing the use of Threading.Task...which is something I use on an almost daily basis now and makes the programming of multi-threads so much more easier.
I remember, back in 1995, we were being taught Fortran77....I mean seriously, what the hell?
BTW: Why are you using VB and not C#? If you look at the job market, there are plenty more jobs in C# than in VB, for this reason, I would much rather learn .NET programming in C# than in VB. Even though they are similar in syntax and methods, C# does differ from VB.
Last edited: