I don't know what the problem is, but there is no such thing as .NET COM.


>We're getting this error in an ASP.NET application.
>
>Exception Details: System.Runtime.InteropServices.COMException: securityservice.recorderror f:\source code\codebook\flash\codebook\common\libs\csession.prg Error in line 379 Class definition ENTRESYSTEMSERVICES.SYSTEMSETTINGS is not found. 1733
>
>We are calling a VFP COM component from ASP.NET and the VFP COM component happens to call another COM component (which is a .NET COM component)
>
>Call path:
> ASP.NET
> calls SecurityService(VFP COM)
> calls EntreSystemServices (.NET COM)
>
>It works fine on the machine that everything is compiled on (iow, the developer machine) but once it's moved to a different box, it seems that the VFP component can't find the .NET COM component registration.
>
>On the test machine the .NET COM component intellisense works in VFP so it appears that the registration is correct.
>
>We've registered the COM component manually and registered the typelib, etc. but this one is dogging us.
>
>Oh, BTW, the VFP COM component is from the COMCodebook libs (that shouldn't affect anything in this scenario, but I mention it for interest's sake).
>
>TIA,
>Chris