471,570 Members | 957 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,570 software developers and data experts.

Using relative paths in SUO file.

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.

--
Paul
Jan 23 '06 #1
3 3149
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?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Paulustrious" <msdn_whoisat_paulcotter.com> wrote in message
news:D9**********************************@microsof t.com...
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.

--
Paul

Jan 23 '06 #2
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>

Jan 23 '06 #3

<grin id="iotic" />
"Bruce Wood" wrote:

<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>

Jan 23 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by Doug | last post: by
7 posts views Thread by mark | last post: by
3 posts views Thread by epigram | last post: by
2 posts views Thread by Joe | last post: by
11 posts views Thread by MBS | last post: by
19 posts views Thread by Jerry M. Gartner | last post: by
8 posts views Thread by JJ | last post: by
15 posts views Thread by Lars Eighner | last post: by
reply views Thread by leo001 | last post: by
reply views Thread by lumer26 | last post: by
reply views Thread by Vinnie | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.