By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,962 Members | 1,889 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,962 IT Pros & Developers. It's quick & easy.

Moving VB .NET 2002 projects to VB .NET 2003 on a multiboot system

P: n/a
On a multiboot system, I have VS .NET 2002 installed in the OS on the G
drive, and VS .NET 2003 installed in the OS on the J drive.

Whilst booted to the OS on the G drive, I create a project using VB .NET
I then boot to the OS on the J drive and upgrade the project to VB .NET

I have noticed that the project's "Start External Program" and "Working
Directory", and maybe other things, still point to the G drive even tho the
project was updated under VB .NET on the J drive.

This might cause grief if, say, the "Start External Program" identified an
application. such as Word, that was a different version in each OS.

Is there a list of the project/solution properties that need to be manually
modified in such circumstances?

--; See Howard Kaikow's web site.
Nov 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.