Re: Random DLLs and Web Hosting Services

The strangely named DLL or DLLs are part of the just-in-time compilation
feature of ASP.NET.  I believe that this will occur only once unless you
change your source code.

A better approach in this situation might be to give the DLL a strong name
(see MSDN for more information) and have your service provider register it
in the Global Assembly Cache (GAC).  These DLLs are not copied and re-named
as are other ASP.NET DLLs.


-----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



The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.