B
Bill Dines
I'd be interested to know if anyone else has had problems
when trying to use the Zero admin deployment features
of .NET (i.e. running applications from a URL so they are
hosted in the IEExec.exe process)
I'm trying to use this technique with a couple of
relatively complex applications that use COM interop and
remoting.
I'm currently struggling with 2 major problems as follow:
On some machines the applications don't seem to run at
all - theres no errors or indication that the application
has been run on the PC. You can see the .exe file has
been downloaded to the temporary internet files
directory, but its dependent .dlls have not. The PC's
are using Windows XP and IE 6
The other issue is an ExecutionEngineException and
subsequent crash when running one of the applications.
The exception always occurs on the some line of code, but
does not seem to bare any relation to the executing code
(for example, if I remove the code that fails, the
application just fails somewhere else completely
unrelated). This error is not predictable meaning code
can be executed successfully several times before the
error occurs. This error has never occured when the
application is running locally.
I'd be interested to know if anyone has come across
similar problems, and also would like to know if anyone
has successfully used this method of deploying software.
ta
Bill
when trying to use the Zero admin deployment features
of .NET (i.e. running applications from a URL so they are
hosted in the IEExec.exe process)
I'm trying to use this technique with a couple of
relatively complex applications that use COM interop and
remoting.
I'm currently struggling with 2 major problems as follow:
On some machines the applications don't seem to run at
all - theres no errors or indication that the application
has been run on the PC. You can see the .exe file has
been downloaded to the temporary internet files
directory, but its dependent .dlls have not. The PC's
are using Windows XP and IE 6
The other issue is an ExecutionEngineException and
subsequent crash when running one of the applications.
The exception always occurs on the some line of code, but
does not seem to bare any relation to the executing code
(for example, if I remove the code that fails, the
application just fails somewhere else completely
unrelated). This error is not predictable meaning code
can be executed successfully several times before the
error occurs. This error has never occured when the
application is running locally.
I'd be interested to know if anyone has come across
similar problems, and also would like to know if anyone
has successfully used this method of deploying software.
ta
Bill