Public Key changes on Rebuild All?

[rplaire]

Hi there,

Could someone help me over my lack of knowledge here? I am trying to
find out why, when I use the same key pair, and the assembly version is
constant, does the public key change with each Rebuild All in VS 2003?
This sort of behavior will change the assembly strong name which is a
Bad Thing when trying to actually use code beyond the development
environment...

I want the strong name to remain constant, and by all accounts it
should, given the same version number and key pair...

thanks,
-rory 8)

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Peter Koen]

rplaire <rory.plaire@no_spam_no.co.benton.or.us> wrote in
news:em**************@TK2MSFTNGP09.phx.gbl:

Hi there,

Could someone help me over my lack of knowledge here? I am trying to
find out why, when I use the same key pair, and the assembly version is
constant, does the public key change with each Rebuild All in VS 2003?
This sort of behavior will change the assembly strong name which is a
Bad Thing when trying to actually use code beyond the development
environment...

I want the strong name to remain constant, and by all accounts it
should, given the same version number and key pair...

thanks,
-rory 8)

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

seems like you have registered a custom build step that regenerates the
keyfile on each builds.

check your project build settings. what you described is not a default
behviour of vs.net

--
------ooo---OOO---ooo------

Peter Koen - www.kema.at
MCAD CAI/RS CASE/RS IAT

------ooo---OOO---ooo------

[Rory Plaire]

>

seems like you have registered a custom build step that regenerates the
keyfile on each builds.

check your project build settings. what you described is not a default
behviour of vs.net

Hi Peter,

Thanks for the insight. I followed this through on this thread:
news:eG**************@TK2MSFTNGP10.phx.gbl in the
microsoft.public.dotnet.framework group.

The issue was I was using sn -t to display the token, and not sn -T.

-r 8)