Copying a project into another solution

  • Thread starter Thread starter mrmagoo
  • Start date Start date
M

mrmagoo

I'm creating a VB.Net project. It's a small utility. However, my boss wants
me to put it in with a larger solution that the department uses, so that a
suite of tools are all in one place. That's fine, however, I am finding that
development is taking longer because, during my unit testing I have to build
and run the project a lot. Since there are many other projects in the
solution, it's taking quite a long time to build the solution just so that I
can run my own code.

My question is: can I build my own project separately as its own solution,
then when I am done, copy it in to the larger solution? Is there anything
that will happen when I copy it over into the solution that I should watch
out for, such as file locations, etc?
 
No need to copy it anywhere. Just create a new solution and add that
project to it. The project can exist in two or more solutions at the
same time. Both solutions will point to the same project.
 
There is an easy way to do this using the configuration manager in VS.
Use the main solution file and create a new configuration. Select which
projects you would like to build and run using the checkboxes. To
access the config manager go to Build--> Config manager. This will
create a new config that can be selected just like the "Release" and
"Debug" configurations that are there by default.
 
Back
Top