Best Practices document for new .Net Dev * SC

[jayjay]

Has any one come across a site or document that describe basic source code control principles for a .Net dev shop. For example should we check in 3rd party DLL, should we check in solution / project files etc etc.

Thanks

Jay

[lbauer]

It depends on the development process. Visual Studio doesn't add .dll files to source control, but some users want to add third-party .dlls to keep them with the rest of the files. DLLs can be added with the GUI Client.

If everyone is using the same solutions with the same projects, then you can add the solution and project files to source control.

If users have solutions that use a different mix of projects (UserA's solution has ProjectA and Project C, UserB's solution has ProjectA and ProjectB) then the users might not check in the solution file.

[ant]

Hi jayjay,

Eric Sink documents version control processes and best practices at url below. Well worth scanning theu' the chapters and noting the 'best practices' boxes.

[url]http://www.ericsink.com/scm/scm_intro.html[/url]

Is there anything special about .net with regard to version control? Eric 'best bractice' suggestion is to control 'canonical' artifacts only: c# source instead of DLLs for instance. I agree with this but 3rd party DLLs are another story.

I think 3rd party dlls should be version controled as otherwise how do you create old versions of your version controled app. The downside is that you can end up with bulky dlls in vault.

Anyway, opinion appreciated.

Regards

Ant


[quote="jayjay"]Has any one come across a site or document that describe basic source code control principles for a .Net dev shop. For example should we check in 3rd party DLL, should we check in solution / project files etc etc.

Thanks

Jay[/quote][/url]

[lbauer]

Some users store .DLLs in the repository. They use the GUI client to add them. They are not always included in the Visual Studio.net project though.