S
Sam Marrocco
Guest
I have a complete vs.net/vb.net solution that works fine.
Vb.net seems to be using an absolute path instead of a relative path for my files if they are left open and a solution is copied. For example:
1-If I open my solution and open any code document for a class or module and leave it open.
2-Save the solution and close VS.net.
3-Make a copy of the entire folder containing the solution.
4-Now open the copy of the solution in the new location.
All the "closed" file document point to their location in the new solution folder, but any documents that were left *open* are still pointing to their original location. This, of course, causes a problem when you start to edit the open documents and don't realize you are actually editing the original solution's project instead of the copy.
I don't seem to remember this happening with vs 2017.....or perhaps this is some preference/setting in vb.net that I am overlooking that causes this behavior with open documents?
Continue reading...
Vb.net seems to be using an absolute path instead of a relative path for my files if they are left open and a solution is copied. For example:
1-If I open my solution and open any code document for a class or module and leave it open.
2-Save the solution and close VS.net.
3-Make a copy of the entire folder containing the solution.
4-Now open the copy of the solution in the new location.
All the "closed" file document point to their location in the new solution folder, but any documents that were left *open* are still pointing to their original location. This, of course, causes a problem when you start to edit the open documents and don't realize you are actually editing the original solution's project instead of the copy.
I don't seem to remember this happening with vs 2017.....or perhaps this is some preference/setting in vb.net that I am overlooking that causes this behavior with open documents?
Continue reading...