Any solutions?

[pfurb]

Hi.
I have seen alot of cases on google where people having the same
problem, but I have not seen a comprehensive solution yet. I really
hope someone can solve this once and for all.

I have created a SmartClient (No touch deployment) and it runs Ok. But
when I change the program and retry it fails the first time.

"An unhandled exception of type 'Systme.IO.FileLoadException' occurred
in IEexec.exe."
"The located assembly's manifest definition with name
'Application.exe' does not match the assembly reference."

When trying a second time, reloading the URL from IE, it works fine.
If I change the program and Deletes the temporary internet files and
retry, it also works fine.

I have set up the security permissions for the assembly (public key)
to full trust, so I am pretty sure it has nothing to do with
permissions.

Thanks in advance.

 

[Noonu]

Not sure if this is anything related, but...

AssemblyInfo.cs by default auto increments the build no (using a *)

eg 1.0.0.*

As this changes on each compile, if you compile one assembly without the
other something similar happens. not sure if this is in anyway related but
you could give it a whirl (ie fix the version no to 1.0.0.0, not 1.0.0.*

 

[pfurb]

Thanks for answering.

I do not think it is related. I am using only one assebly and it has a
fixed verionsnumber 1.0.0.1.

If i compare the manifest of an old version and a new version(using
ILDasm) the only thing that has been changed is the MVID...

..module MyApplication.exe
// MVID: {016013D1-2511-4636-BD6F-F2EE3E668797}

Reading about CLR, and how it identifies assemblies, have not directed
me closer to the solution. CLR should be able to handle this.

Anyone, any suggestions.

 

[Anthony Coelho]

pfurb,

I have the same problem, have you found a solution?

Thanks,
Anthony

 

[pfurb]

Hi Anthony.

I am sorry, but I have not found a solution yet.

I hope that someone can shed a light on this problem...

br/