L
Luther Miller
There is a small windows forms piece to a larger ASP.NET application
that integrates and uses web services.
I have done some experimenting on the deployment side of things, and
it appears that when I either embed the forms control in a page, and
thus reference the DLL assembly, or when I link to a standalone EXE,
the web server (IIS) tries to process the EXE or DLL as if were going
to execute a CGI program and return a reponse.
Instead, I want IIS to simply "download" the EXE or DLL... I have
found I can work around this by deploying my assemblies in another
virtual web folder, but I would like to deploy everything all in one
place. I imagine there must be an easy configuration setting to turn
off IIS's processing of the EXE and DLL files (since it is handling
them differently than, say, a .HTM file).
Ideas?
that integrates and uses web services.
I have done some experimenting on the deployment side of things, and
it appears that when I either embed the forms control in a page, and
thus reference the DLL assembly, or when I link to a standalone EXE,
the web server (IIS) tries to process the EXE or DLL as if were going
to execute a CGI program and return a reponse.
Instead, I want IIS to simply "download" the EXE or DLL... I have
found I can work around this by deploying my assemblies in another
virtual web folder, but I would like to deploy everything all in one
place. I imagine there must be an easy configuration setting to turn
off IIS's processing of the EXE and DLL files (since it is handling
them differently than, say, a .HTM file).
Ideas?