Where do you keep your solution file?

[Bruce W.1]

I've been keeping my solution .sln files for ASP.NET projects off in
some remote location, along with all my other .sln files.

This confuses things and I think it really belongs with the web app in
wwwroot. It would make more sense anyway.

What's the best practice on this, and is this what you do?

Thanks for your help.

 

[Kevin Spencer]

It makes sense to keep your Solution files where youcan find them easily.
Any other criteria for making sense doesn't make sense. ;-)

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Mike Newton]

I've been keeping my solution .sln files for ASP.NET projects off in
some remote location, along with all my other .sln files.

This confuses things and I think it really belongs with the web app in
wwwroot. It would make more sense anyway.

What's the best practice on this, and is this what you do?

Thanks for your help.

I would keep the solution files away from the project root. Keeping
them there works in cases where you only use one project for one
purpose, but once you start sharing projects among many solutions, it
makes less sense to keep them in the project directory.

This also applies to SourceSafe / whatever repository you use. Solution
files store paths that are relative to your own machine, so either mass
standardization is needed, or the file needs to be edited in a big way.
It's easier just to include a text file that lists the other projects
that the project in question depends on.

I have a []:\Development directory that has a tree structure of
languages->solution types->solution. I know exactly where to look for a
solution. The project files stay with the project.

 

[Bruce W.1]

I would keep the solution files away from the project root. Keeping
them there works in cases where you only use one project for one
purpose, but once you start sharing projects among many solutions, it
makes less sense to keep them in the project directory.

This also applies to SourceSafe / whatever repository you use. Solution
files store paths that are relative to your own machine, so either mass
standardization is needed, or the file needs to be edited in a big way.
It's easier just to include a text file that lists the other projects
that the project in question depends on.

I have a []:\Development directory that has a tree structure of
languages->solution types->solution. I know exactly where to look for a
solution. The project files stay with the project.

========================================================

That makes good sense. So I should continue what I'm doing.

Just for grins however I tried putting it in the project's wwwroot
folder. First I created the folder with Windows Explorer. Then I set
VS to put the .sln file there. Then I created the new project with VS
and it made a subdirectory (with the same name as its parent). Good grief!

If it's this difficult then it probably wasn't meant to be done in the
first place.

Assuming one wanted to create a simple ASP.NET project, any idea on how
one could put the .sln file in its wwwroot folder?

Thanks.