Re: Random DLLs and Web Hosting Services

As I understand it, every time that you restart the IIS Server, or make
changes to the application, ASP.NET will write a copy of the DLLs to the
Temporary directory.  In fact, this is how ASP.NET got around the old
problem of ASP making it difficult to roll out changes in applications
without rebooting the server.

If the hosting service is a fully-qualified ASP.NET hosting facility,
then they should know this already, and allow changes to a temporary
directory to occur.  If they want to have these DLL files go into a
particular directory, they can set that directory by adjusting
Machine.config -- and setting the temporary directory that they are
supposed to go into -- maybe make it \\HostingServer\ASPNetTemps for
example.


Walt Crosby
Executive VP
Terabase Corporation
10 Elm Street
Danvers, MA 01923
(978) 774-7999 x114

-----Original Message-----
From: Discussion of implementing SOAP applications today
[mailto:[email protected]] On Behalf Of Siegfried Heintze
Sent: Friday, September 10, 2004 12:56 AM
To: [email protected]
Subject: [SOAP] Random DLLs and Web Hosting Services

We have a commercial web hosting service that told us they would support
ASP.NET. I told my client: great, I'll write a XML Web Service for you.



Many thousands of dollars later we now have a C# web service that uses
P/Invoke to call native C functions in a DLL.



Our hosting service uses software to detect whenever a new DLL is loaded
on their system. It appears that ASP.NET copies my DLL into the
temporary directory with some random file name. This makes our hosting
service very upset because it looks like they are under attack whenever
ASP.NET makes a DLL in the temporary directory.



How often does ASP.NET make a copy of my DLL in the temporary directory?
Has anyone else encountered this problem?



Thanks,

   Siegfried