Suds
6/7/2007 12:48:00 PM
Hi,
Well I observed that the when my .NET assemblies are not signed, the
[assembly: AssemblyVersion("1.0.*")] way of incrementing version numbers
works (provided I specify 1.0.0.0) as my version in the manifest file). I
does not work if the assembly is signed unless the manifest file has the
exact version.
I will manually specify my version number, when my assembly is signed.
Thanks for you answering my questions.
Suds
"Walter Wang [MSFT]" <wawang@online.microsoft.com> wrote in message
news:AJcGK7MqHHA.2304@TK2MSFTNGHUB02.phx.gbl...
> Hi Suds,
>
> Thanks for the update.
>
> Currently Visual Studio 2005 doesn't do very well for the manifest file;
> many tasks still require to be done manually.
>
> For the version issue, you have to manually control the version number,
> don't use the auto-increment version feature, such as:
>
> [assembly: AssemblyVersion("1.0.*")]
>
>
> After manually editing the version number, you need to update the manifest
> too.
>
> If you really need to make it update the manifest automatically, you can
> create some script/tool to sync it, and you can use a Pre-Build rule to
> call this script/tool.
>
> Hope this helps.
>
>
> Regards,
> Walter Wang (wawang@online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
>
> ==================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>