Keep in mind, it is possible to either create a project without an AssemblyInfo file, or to delete it from the project. So, just verify that all projects have one... Of course, your issue is slightly different than what I was trying to resolve, which related to the locking of the .pdb file, so ymmv.
John > -----Original Message----- > From: The DOTNET list will be retired 7/1/02 > [mailto:[EMAIL PROTECTED]] On Behalf Of Loc Nguyen > Sent: Thursday, June 06, 2002 9:04 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] VS.Net "Copy Local" feature > > > Hmm... I remember someone from MS mentioning something about > the assembly version number. I do not remember what it was > he said about it. However, in my second posting to this > issue, I mentioned that I did a grep on *.* at the root of > our source tree for the offending version number string and > could not find any file with this string. In addition, I > only have exactly one copy of the offending assembly on my > system. It is the newer version. Therefore, I believe > VS.Net is caching the old version number somewhere. This > issue is hugely hindering productivity. > > MS is up to their old automagic crap (e.g. IE security > settings, cross scripting, COM integration in outlook). Has > anyone at MS heard of the KISS rule of thumb? > > 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.
