Re: No-Touch deployment - IEExec - Duplicate Entries in Assembly Cache - Strongly Typed Datasets - InvalidCastException
From: Paul Linhardt (linhardt_at_aol.com)
Date: 04/28/04
- Next message: Matt Berther: "Re: Creating Optional Commandline Parameters"
- Previous message: Justin Rogers: "Re: Multiple Instances of a Form"
- In reply to: Paul Linhardt: "No-Touch deployment - IEExec - Duplicate Entries in Assembly Cache - Strongly Typed Datasets - InvalidCastException"
- Messages sorted by: [ date ] [ thread ]
Date: 28 Apr 2004 09:41:13 -0700
In case anyone out there (besides Chris) is interested, I did find a
solution to the problem.
IEExec was loading two copies of the assembly into the download cache
(one ending in '.exe' and one ending in '.EXE'). The download cache
which hashes the name, date, etc. for identification decided they were
different even though the code was exactly the same. If I ran
'myClientApp.EXE' from a browser, it would run fine, but if I ran
'myClientApp.exe' I would get an InvalidCastException (somehow there
was a mismatch between the strongly typed dataset definition in the
client & web service).
Anyway, the solution was relatively simple and painless. I made my
client app assembly strongly named by adding a key pair:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconcreatingkeypairforuseincreatingstrongly-namedassembly.asp
Strongly Named assemblies are only downloaded once by IEExec. Problem
solved.
-Paul
- Next message: Matt Berther: "Re: Creating Optional Commandline Parameters"
- Previous message: Justin Rogers: "Re: Multiple Instances of a Form"
- In reply to: Paul Linhardt: "No-Touch deployment - IEExec - Duplicate Entries in Assembly Cache - Strongly Typed Datasets - InvalidCastException"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
