Using relative paths in SUO file.

[Guest]

Hi

The SUO solution file appears to have absolute file addresses. Is it
possible to force it to use relative addresses to make it easier to move
projects and solutions. Or maybe I'm going about moving things all the wrong
way.

 

[Nicholas Paldino [.NET/C# MVP]]

Paul,

You shouldn't be touching the SUO file. This is a file generated by the
IDE, not your actual solution file. If you look in the SLN file, you will
see that the references are not absolute.

What are you looking in the SUO file for?

 

[Bruce Wood]

When you move the solution, don't move the .suo (or .csproj.user) file
with it. Or, stated another way, don't check .suo or .csproj.user into
source control.

Having said that, I should point out that if you're using a source
control system and you don't check in .suo, then when you check your
solution out, Visual Studio 2003 gets all pissy and complains that your
solution is missing critical source control information and says that
it will "now attempt to reconstruct it," which it then proceeds to do.
I've never had it fail.

<rant>
I have no idea why MS chose to: 1) put two IDE-generated, apparently
superfluous files in the source directory so as to confuse most source
control systems out there, especially when said files contain absolute
paths which cause havoc if you check them into a source control system;
and 2) put in one of those IDE-generated, apparently superfluous files
"important" source control information that makes the IDE angry if the
file is missing.

I do enjoy working in VS2003... except for this stupid issue. I wonder
if they've fixed it in 2005?
</rant>

 

[Guest]

<grin id="iotic" />


: