>I don't know if the confussion is something like this, Guenter, but the important thing is that this deployment method only works for the .NET application consumption. When you use this feature the DLL is NOT registered, and then it doesn't need to be unregistered at all. Also, you CAN'T instantiate it from a COM environment (i.e: other VFP application) in the target machine (except that it the DLL is found in the app path, but this is not the proper way to do things).
>
>Please, Ken, let me know if I'm wrong at this.

Correct. The COM object is isolated (encapsulated) within the manifest of the .NET managed code application (EXE or DLL) created in which it is contained in.