Loc, One final thought. As Paul Stevens mentioned earlier, this appears to be a combination of assembly versioning and the way your solutions/projects have been created. I would strongly recommend that you have all your developers carefully read the following guide from MS -- ignore the part about VSS -- the discussion of proper solution setup is great:
"Team Development with Visual Studio .NET and Visual SourceSafe" http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/h tml/Tdlg_rm.asp [downloadable Word version] http://microsoft.com/downloads/release.asp?ReleaseID=35981 John > -----Original Message----- > From: The DOTNET list will be retired 7/1/02 > [mailto:[EMAIL PROTECTED]] On Behalf Of Loc Nguyen > Sent: Friday, June 07, 2002 10:39 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] VS.Net "Copy Local" feature > > > Thanks all you who've replied. I faintly remembered an MS > guy at one of their free MSDN presentation specifically > discuss not using the wildcard that the IDE defaults the > value to during project generation. I don't remember the > context for this, but I have a feeling assembly hell is the > situation it corrects. This is what we're going to follow. > I have a feeling it may fix this issue -- it seems to have > solved it for others. > > 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.
