Sharing a class library within same TFS Project

We have a TFS project that represents a single product. This product has two possible installations, one web based and the other windows client based each with different installers. The two installations share the same class library. We're trying to determine the best way to structure the source control in TFS with respect to the class library so that it can be managed and built as efficiently as possible without having to create a separate TFS project to do so. Any suggestions

Visual Studio Team System24

I think you can create two installer projects in one build solution . or else you can go with two solutions (ie web-installer and WIN-Installer)which include all the class liberaries and only one installer project . you can keep both solutions in same directory and in same team project . also you can build both in single team build . These all are out of box features .

as always any .net project (.csproj, .vbproj or .DBP etc ) can be member on any number of .net Solutions , this feature is same since VC++ days .

Let me know if you have specific questions .

Samant B Jain