Solution file : loading only selected projects

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi ,

Visual Studio 2003, VB.NEt

my VB.Net solution has 10 project files, 1exe and 10 dlls in it and when i
load up the solutions it takes for ever to load up and is pretty slow. Is
there any way (like in VB6) that i could have multile solution files having
combination of different project files and when i load up those solutions
only the selected projects loads up in source code and the others in dlls and
i shuld still be able to run the application.

thanks
sameer
 
Why not?

Th solution is simply a logical grouping. If you want to set up one solution
with a single project and references to compiled code, and then another with
all 10, there is nothing to stop you. I would make sure you have a good
naming convention for the different solution files, but I see no problem
with the idea.

In general, you try to put some software "to bed" and thin down solutions.
This is not always possible, so multiple solution files can fit the need, if
you can keep track of them.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************
 
Cowboy,
i tried doing it and this is the message that i get. I forgot to mention
this project with the source file is under source control. What do yo think
about it? Thanks

the project file appears to be missing some required source control
information. this may be caused by

deleted or missing solutions optins file (.suo)
opening a project from the local disk without it;s solution
adding a project controlled by a differnet source control database
opening the solutions when source control is not avaialbe.
 
Source Control makes it fun. You have a couple of options, none of which are
super:

1. Branch the files and create a "new" project file. Downside on adding
files as you have multiple project files.
2. Have a read only project file on projects without the "normal" binding.
This can also get out of sync, so you have to have discipline.
3. Have discipline to remove and add references and not check in the
project. Yuck!

Best bet is to put the "finished" pieces to bed (meaning compile and
reference those components you feel fairly confident you are finished with).
Create a "components" folder in source control and reference the controls
there. This way, if you need to recompile, it is not in this directory and
messing up other devs. Be sure you are not actively working on these
libraries/components, or it will be a royal mess.

Outside of that, you have to keep all projects in your solution.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************
 
Back
Top