Solutions files and project references, probem
-
Hi folks, if you got 2 projects nested in one solution, you could add a project related reference and the project dependencies are also managed by VS. Also the solution configuration like "debug" or "release" is set by VS to all projects nested. We've got 12 project, each produce a assembly dll file. It's impossible to add these project to our Solution, in which we build the main application. The main application is based on these other projects. Now my problem is, that i cannot add project related references, i had to reference these assemblys by path. But if i reference the bin\debug\*.dll, i will never be able to do a "release" build, cause all these assemblys are still in debug configuration. which way is the best for this issue ? I know about the object directory, where vs stores the file also, would it be better to reference these assemblys ? In this case i've got the current solution configuration in my reference. Hope i explain it well :confused: .:Greets from Jerry Maguire:.
-
Hi folks, if you got 2 projects nested in one solution, you could add a project related reference and the project dependencies are also managed by VS. Also the solution configuration like "debug" or "release" is set by VS to all projects nested. We've got 12 project, each produce a assembly dll file. It's impossible to add these project to our Solution, in which we build the main application. The main application is based on these other projects. Now my problem is, that i cannot add project related references, i had to reference these assemblys by path. But if i reference the bin\debug\*.dll, i will never be able to do a "release" build, cause all these assemblys are still in debug configuration. which way is the best for this issue ? I know about the object directory, where vs stores the file also, would it be better to reference these assemblys ? In this case i've got the current solution configuration in my reference. Hope i explain it well :confused: .:Greets from Jerry Maguire:.
We've created an empty C++ makefile project which runs a batch file (in its post-build step) that copies with output of the current configuration (using macros) to a final 'bin' directory. The other projects all then reference these assemblies. Cheap and nasty but works. Welcome to better solutions?
-
We've created an empty C++ makefile project which runs a batch file (in its post-build step) that copies with output of the current configuration (using macros) to a final 'bin' directory. The other projects all then reference these assemblies. Cheap and nasty but works. Welcome to better solutions?
Hi, is there no problem when you open VS.Net (2 instance) with locked files, if all the assemblys are stored in the same directory, if the opened project is dependant to those files ? .:Greets from Jerry Maguire:.
-
Hi folks, if you got 2 projects nested in one solution, you could add a project related reference and the project dependencies are also managed by VS. Also the solution configuration like "debug" or "release" is set by VS to all projects nested. We've got 12 project, each produce a assembly dll file. It's impossible to add these project to our Solution, in which we build the main application. The main application is based on these other projects. Now my problem is, that i cannot add project related references, i had to reference these assemblys by path. But if i reference the bin\debug\*.dll, i will never be able to do a "release" build, cause all these assemblys are still in debug configuration. which way is the best for this issue ? I know about the object directory, where vs stores the file also, would it be better to reference these assemblys ? In this case i've got the current solution configuration in my reference. Hope i explain it well :confused: .:Greets from Jerry Maguire:.
Why are you not able to add project-related references? Is it because of locking issues during compilation? Michael CSO, ActiveWare LLC http://www.ActiveWareSolutions.com
-
Why are you not able to add project-related references? Is it because of locking issues during compilation? Michael CSO, ActiveWare LLC http://www.ActiveWareSolutions.com
Hi, our projects are normal c# WindowsApplication and ClassLibrary projects. If the project is not nested in a solution file, you could only add file related references, or is there something i missed ? .:Greets from Jerry Maguire:.
-
Hi, our projects are normal c# WindowsApplication and ClassLibrary projects. If the project is not nested in a solution file, you could only add file related references, or is there something i missed ? .:Greets from Jerry Maguire:.