I can successfully export a .NET COM+ Application Proxy from a freshly
installed Windows Server 2003 machine that resides within our Active
Directory. I can also successfully install the COM+ Cpplication proxy on my
remote Windows XP Professional machine.
My issue is that when I add the COM+ reference into my .NET Application, the
reference does not contain all of the compiled resources that I had installed
on the COM+ server.
For example, I compiled a dataset into the .NET COM+ Application, but some
of the datatable columns do not appear in the exported proxy application.
To complicate matters more, when I install the exact same .NET COM+ dll on a
domain controller within our Active Directory and then create an application
proxy from the domain controller, the proxy contains all of the correct
dataset references.
I'm very puzzled by this problem. Any help and suggestions is much
appreciated.
Thank you in advance.
Mike B - 18 Jan 2005 16:43 GMT
I was able to resolve this.
In short, the issue was that everytime I installed a new code version of the
.NET COM+ Application on the Windows 2003 Server, I never changed the
Assembly Version within the AssemblyInfo.vb file. Technically, I should not
need to do this; however, COM+ would say it "updated" my COM+ App everytime I
ran regsvcs.exe; however, it did not update the app to reflect code changes.
In order to force COM+ services and regsvcs.exe to update the assembly, I
had to change my Assembly Version of my dll. Once changed, I had no problems
exporting applciation proxies and installing them on remote computers. All
code changes were brought over.
> I can successfully export a .NET COM+ Application Proxy from a freshly
> installed Windows Server 2003 machine that resides within our Active
[quoted text clipped - 17 lines]
>
> Thank you in advance.