Re: .dll assembly security changes at each compilation
From: richlm (rich_lm_at_h0tmai1.com)
Date: 02/25/04
- Next message: Sherif ElMetainy: "Re: Security makes .Net a JOKE....."
- Previous message: Mary Chipman: "Re: Code Access Security, Evidence Based Security, Code Access Permission, Role Based Permission, etc"
- In reply to: cybertof: ".dll assembly security changes at each compilation"
- Next in thread: cybertof: "Re: .dll assembly security changes at each compilation"
- Reply: cybertof: "Re: .dll assembly security changes at each compilation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 25 Feb 2004 21:34:11 +0100
Check the AssemblyVersion attribute in AssemblyInfo.cs/vb.
It probably looks something like AssemblyVersion ("1.0.*"). - the * get's
incremented each time you build.
If so, change it to e.g. AssemblyVersion ("1.0.0.0").
"cybertof" <cybertof2003nospam@gmx.net> wrote in message
news:MPG.1aa6d43ee5338df298969a@msnews.microsoft.com...
> Hello,
>
> I have a custom Excel 2003 .dll assembly, and each time i rebuild the
> assembly and place it on the client PC, i have to apply again the
> security on the new assembly (same location).
>
> Is there a way to deploy an assembly without having to enable again full
> permissions on it once it is place back to its destination ?
>
> Regards,
> Cybertof.
>
- Next message: Sherif ElMetainy: "Re: Security makes .Net a JOKE....."
- Previous message: Mary Chipman: "Re: Code Access Security, Evidence Based Security, Code Access Permission, Role Based Permission, etc"
- In reply to: cybertof: ".dll assembly security changes at each compilation"
- Next in thread: cybertof: "Re: .dll assembly security changes at each compilation"
- Reply: cybertof: "Re: .dll assembly security changes at each compilation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]