Note that there are some explanatory texts on larger screens.

plurals
  1. POUpdating Visual Studio project references programatically
    text
    copied!<p>I wish to programatically update the references in the projects in my Visual Studio solution.</p> <p>I have roughly 15 projects in my solution and when I am developing/debugging I want the references to point to the projects within the solution.</p> <p>As part of my release procedure I sometimes need to make a copy of one project and then update the references to point to built dlls in a certain folder.</p> <p>I can work out the structure of the project files and how references work within them and I am thinking of building a command line tool to parse the project files and change references as required.</p> <p>My questions are:<br> 1. Does this sound a sensible thing to do<br> 2. Has anyone experience of this and/or how do they handle switching between developing and release modes<br> 3. Does anyone have any libraries that deal with parsing Visual Studio project files.</p> <p>CLARIFICATION:</p> <p>Thanks for the responses. Perhaps I should clarify a few situations where I wish to use this.</p> <p>a) My application contain 15 projects. I try and keep the solution as small as possible for what I am working on, so say I have 5 projects in my solution. I now need to debug/develop one of the projects not in the solution so I add this project but I have to: - set the references in the original projects to point to project references rather than compiled dlls - change the references in the newly added project to point to the appropriate project references</p> <p>I would like my tool to do this automatically and the only way I know to so this at present is manipulating the project files</p> <p>b) As part of a service pack build procedure I take a copy of one of the projects, make the necessary code changes and build using Visual Studio. To do this I have to change all the references to the compiled dlls</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload