OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
COM Interop - Registering COM+ component

From: Bradley, Peter (PBradleyUWIC.AC.UK)
Date: Mon Dec 06 2004 - 03:59:33 CST


Hi,

We have 3 areas where we need remote components: ASP.NET applications (business logic components), components (mainly business logic) accessed by our legacy development systems (especially Uniface) and BizTalk Server AICs. There may be some cases where the same component carries out the same role - i.e. provides business logic for all three purposes, or for any 2 out of the three. The BTS AICs must be COM+ components, and the components accessed by Uniface must be COM callable.

The plan therefore is to use .NET and COM interop to produce components that are callable by all 3 systems.

To this end, I've produced an AIC, in C#, which inherits from ServicedComponent and implements the BTSAppIntegration interface, as a test, which does nothing (except put up a message box on the server). It compiles just fine on my (developer) machine, and registers without a problem. The next step is to transfer it to the BizTalk server and register it there. However when I try to do that, it fails to register, with the following error message:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

H:\>c:

C:\>c:\regsvcs C:\WINNT\system32\BizTalkAIC\AICTest.dll
Microsoft (R) .NET Framework Services Installation Utility Version
1.1.4322.573 Copyright (C) Microsoft Corporation 1998-2002. All rights
reserved.

An unknown exception occurred during installation:
1: System.Reflection.ReflectionTypeLoadException - One or more of the
types in the assembly unable to load.

C:\>

Does anyone know what I'm doing wrong (this is my first try, I have to say)?

Some further information is that Visual Studio 2003 is installed on my developer machine, but not on the server (in fact it won't install for some reason on the server!); a RCW has been produced for the BTSAppIntegration interface on the developer machine - and obviously a CCW for the .NET component (when it registers!). I've run adepends on the component on my developer machine, and on the version copied to the server. The only difference in the configuration files produced by adepends is the codebase for the component (which I've put in c:\WINNT\system32\BizTalkAIC on the server). I've installed the .NET SDK on both machines, but is doesn't seem to make a difference.

Any help would be gratefully received.

Cheers

Peter

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.html
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM