Signing apps causing problems

  • Thread starter Thread starter Smokey Grindel
  • Start date Start date
S

Smokey Grindel

I signed all our apps with the same digital key file. It ran perfectly fine
on my local machine... but when I build it as as setup project and install
it on another machine I get errors like

System.IO.FileLoadException: Could not load file or assembly
'AssembyNameHere', Version=1.0.2901.21807, Culture=neutral,
PublicKeyToken=6059e736472c812f' or one of its dependencies.

the first tiem it installs then if i uninstall it and reinstall I dont get
that error... what in the world would cause this? I know it thinks the file
is the wrong one but why when installing in an "upgrade" situation does it
not put the correct file in that location?
 
Smokey said:
I signed all our apps with the same digital key file. It ran perfectly fine
on my local machine... but when I build it as as setup project and install
it on another machine I get errors like

System.IO.FileLoadException: Could not load file or assembly
'AssembyNameHere', Version=1.0.2901.21807, Culture=neutral,
PublicKeyToken=6059e736472c812f' or one of its dependencies.

That version looks highly suspect to me.

Change the Assembly Version property to remove the wild-card,
auto-generation values (i.e. change it to be "1.0.0.0").

The Framework sees different /versions/ of Strongly Named assemblies as
totally /different/ entities and, unless you tell the application
different, will not "cross-load" versions. The application will /only/
run against the specific version that you built it against and [unlike
the 'Studio IDE] it won't even "auto-upgrade" to use a newer version if
it finds one.
the first tiem it installs then if i uninstall it and reinstall I dont get
that error... what in the world would cause this?

No idea - never come across that one before ...

HTH,
Phill W.
 
I have 36 projects attached to this solution... is there any way to make
version changes to all them at once? like share partial assembly.vb file
across all them or something? thanks!

Phill W. said:
Smokey said:
I signed all our apps with the same digital key file. It ran perfectly
fine on my local machine... but when I build it as as setup project and
install it on another machine I get errors like

System.IO.FileLoadException: Could not load file or assembly
'AssembyNameHere', Version=1.0.2901.21807, Culture=neutral,
PublicKeyToken=6059e736472c812f' or one of its dependencies.

That version looks highly suspect to me.

Change the Assembly Version property to remove the wild-card,
auto-generation values (i.e. change it to be "1.0.0.0").

The Framework sees different /versions/ of Strongly Named assemblies as
totally /different/ entities and, unless you tell the application
different, will not "cross-load" versions. The application will /only/
run against the specific version that you built it against and [unlike the
'Studio IDE] it won't even "auto-upgrade" to use a newer version if it
finds one.
the first tiem it installs then if i uninstall it and reinstall I dont
get that error... what in the world would cause this?

No idea - never come across that one before ...

HTH,
Phill W.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top