Why not handle rights on the source control level? Multi File Assemblies (besides just having a namespace spearated over multiple dll's) are not supported by VS.NET.
The easiest way is to have every peson KNOW which components he is responsible for and just edit them :-) Maybe with some rights enforced in the source control level. Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -----Original Message----- From: Tim Sargent [mailto:[EMAIL PROTECTED]] Sent: Montag, 22. April 2002 09:08 To: [EMAIL PROTECTED] Subject: [DOTNET] Multi-File Assemblies and Builds Hi - I'm working with a group of developers on a .NET application project (using VB.NET). Each person is responsible for certain components of the application, and I'm trying to figure out a simple method for doing builds of the application as we move forward with development. What I'm envisioning is each developer checks his/her code (classes, forms, etc) into VSS, and we do builds off the latest versions. My question is how best to go about this? I have a limited (but growing) understanding of .NET, and from what I know so far it seems that a multi-file assembly is the best route to go. Is that line of reasoning correct, and if so, are there some resources/examples available that will give me some guidance on how to go about doing this? Thanks. Tim You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
