Dov Kleinman wrote:
> IMHO, it is a bug, by design, but still a bug.
>
Then please file a bug so we can see if it meets the bar to add a switch.
--
sig://boB
http://joyofsetup.com/
--
Register Now & Save for Veloci
Bob Arnson wrote:
>
>It appears to be by design, based on this comment in the code:
>
IMHO, it is a bug, by design, but still a bug.
According to Aaron Stebner's blog
http://blogs.msdn.com/astebner/archive/2005/02/12/371646.aspx the fusion bug
was fixed long time ago (.Net 1.1 SP1 & .Net 2.0) a
Dov Kleinman wrote:
> Well, I've tried both "3.0.5217.0" and "3.0.5224.0". Still the same.
> Any idea?
>
It appears to be by design, based on this comment in the code:
// there is a bug in fusion that requires the assembly's "version" attribute
// to be equal to or longer than the "fileVersion
Bob Arnson wrote:
>
Sounds familiar -- try upgrading to the RC2 release for a fix.
>
Well, I've tried both "3.0.5217.0" and "3.0.5224.0". Still the same.
Any idea?
Thanks,
Dov
--
Register Now & Save for Velocity, the
Dov Kleinman wrote:
> It all worked fine when file version and assembly version were the same
> number. Oddly enough when assembly version has less meaningful digits,
> "light" adds zeros to have both versions with the same number of digits.
>
Sounds familiar -- try upgrading to the RC2 relea
Hi,
I have a .Net assembly file with file version "4.0.763.0" and assembly version
"4.0.0.0".
In order to install it into the GAC I have used latest Wix3 toolset and faced a
wrong registration issue.
Taking a look into the MSI file with Orca tool shows that in MsiAssemblyName
table the file ver
6 matches
Mail list logo
