Best Practices - Versioning Third-Party Controls

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
emarthinsen
Posts: 10
Joined: Fri Dec 03, 2004 5:48 pm

Best Practices - Versioning Third-Party Controls

Post by emarthinsen » Tue Jun 07, 2005 1:00 pm

Hello-

I'm trying to find the best solution for versioning and referencing third-party controls in a VS.NET project. Right now, I have four ideas:

1. Have the project reference a copy of the controls present in the bin folder.

2. Create a new project that gets added to the solution that only contains third-party controls.

3. Put all of the third-party controls in a network share folder with versions controlled separately from my main solution.

4. Create a new folder in my project called "ThirdPartControls" and reference the assemblies in that.

I'm leaning towards number 4, but my research has only just begun. Does anyone have any guidance? Is this a solved problem?

Regards-
Eric

Post Reply