Can't open a project by iteself? Solution opens every time!

[cmay]

I have a big solution filled with a bunch of projects.

I add a project to the solution (not adding any references mind you).

Now, if I close down everything and try to just open that single
project, just the vbproj file, not anything to do with the solution, it
ends up loading the entire solution!


Why is it doing this, and how can I stop it from doing it?

 

[Sam Malone]

What I'd try is (totally outside of VS) move (not copy) the files associated
with your new project to a separate directory on your hard drive.
Open the project there. I suspect though when you go back and open the
solution in the previous directory it'll whine about the missing project but
you just "OK" your way past that.
I don't know if this is what you're attempting to accomplish but it should
"detach" the project from the solution. You can always put it back later if
that's what you want.

 

[Claes Bergefall]

I think the OP is complaining about what seems to be a new "feature" in
VS2005
In previous versions you could open the vbproj file and it would
automatically give you a new solution with only that project in it. However,
in 2005 it seems to remember what solution is was previously attached to and
open that instead. Personally I find this highly annoying (especially when
working with large solutions). If I open a single project it should open
*only* that, not bring in the rest of whatever solution it may have been
part of (let me worry about whatever references might get broken).

I haven't found a way to turn this feature off (but I haven't really looked
much either), so if you find a way please share it

/claes

 

[cmay]

Claes,

Exactly!!

That is exactly what I am dealing with and it is driving me nuts!

I can't even seem to find a way to change the solution a project is
"associated" with.

When I first did my conversion to 2005 I put all my projects into 1 big
solution. Now, even if I create new solutions (which I will complain
about below) when I go back to those projects in the new solution, it
seems to only remember that giant solution and not the more recent
solution.

The other thing about this that pisses me off, is that... how do you
add a project to a new solution? You can't open a "blank solution"
like you used to, so the only way I see to create a solution is to
start by opening a project... but if you open a project you get the
solution it was first assigned too!! So how can you get out of this?
I have yet to find a good way to deal with this stuff.

Very frustrating!

 

[Claes Bergefall]

Claes,

Exactly!!

That is exactly what I am dealing with and it is driving me nuts!

I can't even seem to find a way to change the solution a project is
"associated" with.

When I first did my conversion to 2005 I put all my projects into 1 big
solution. Now, even if I create new solutions (which I will complain
about below) when I go back to those projects in the new solution, it
seems to only remember that giant solution and not the more recent
solution.

Highly annoying, I agree.

The other thing about this that pisses me off, is that... how do you
add a project to a new solution? You can't open a "blank solution"
like you used to, so the only way I see to create a solution is to
start by opening a project... but if you open a project you get the
solution it was first assigned too!! So how can you get out of this?
I have yet to find a good way to deal with this stuff.

Actually you can still create blank solutions. Took me a while to find it
though. It's under Other Project Types/Visual Studio Solutions.


/claes

 

[cmay]

Ok that will help get around that little circle of logic.
Thanks.

I hope do away with this, or offer a way to turn it off.