I/We keep references under source control. This way when project files are checked out the user receives all dependencies. The references in the project files are relative references, so they always resolve correctly.


Manish Jain wrote:
I would like to know best practice as well as options available to
maintain project files on build server (in case of .NET, .sln,.vbproj
and .csproj files) for those who are using either solution task or exec
task with devenv.exe.

1.Since references maintained are at different locations for developers
desktop and build server, If developer changes project files for
references or add source files to project, Server needs to be manually
updated to match references - I need AUTOMATED solution for this.

2.How third party references are maintained on build server, its in /BIN
folder or common folder for all projects? Should it be added under
source control?

3.All projects should be compiled or just changed projects on every
build.

Any other resources, links would be appreciated...

Thanks for your responses-Manish








------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users

---------- Scanned for viruses by ClamAV


------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to