You're not going to find the version number in a human readable format. The
version is generated by the compiler and stored in the manifest of the
generated assembly. What you need to do is look in each projects
assemblyinfo.cs (I think that's the file name) for something like this
[assembly:AssemblyVersion("1.0.*.*")]. You should change this to 1.0.0.0 or
whatever version is appropriate for your project.
For what it's worth, I too battled this for some time and the problem was
that I was attempting to get all projects to build to a common output
directory and I had copy local set to false. As soon as I abandoned this
approach and set copy local to true, my solution began building without
problems.
Good luck,
Seang
-----Original Message-----
From: Loc Nguyen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 06, 2002 12: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.
