Please confirm this

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I am about to yank more hair form my head here. I created a COM+
Application. It uses the following dlls

3party.dll
Microsoft.Practices.EnterpriseLibrary.Data.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll

The com+ application (Server) works fine on my development machine. I even
created a webservice on my machine that comsumes this com+ dll and it works
excellent. I am even able to consume the webservice form another machine via
a vb.net app. (remember the COM+ PACKAGE and WEBSERVICE is hosted on my
development machine).

I then exported the the COM+ package, as server applicaion, to .MSI file and
then installed it on my server. The installation was successful. From the
server I then expotred an "Application Proxy" to be installed on client
machine. During the installation of the proxy on the client machine, which
will be consuming the COM+ package and hosting the webservice to do so, I get
the error

{"An error occurred creating the form. See Exception.InnerException for
details. The error is: Could not load file or assembly 3partydll,
Version=3.0.2070.0, Culture=neutral, PublicKeyToken=cdc18889cffe9cf' or one
of its dependencies. The system cannot find the file specified."}

Question1:
Do I also have to deploy all the .dlls used by the COM+ component to the
client machine(s)? If so, doesn't this defeat the purpose of the COM+ Server
Component as being the server hosted on a separate machine?
Question2:
Why didn't my app prompted for the additional .dlls
Microsoft.Practices.EnterpriseLibrary.Data.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll?
Question3:
What's a good book available for reference on COM+. I have been on this
project for weeks and ready to deploy to production and finelly these issues?
This COM+ CRAP IS DEFINITELY NOT EASY!!!

Thanks guys.
 
¤ Question1:
¤ Do I also have to deploy all the .dlls used by the COM+ component to the
¤ client machine(s)? If so, doesn't this defeat the purpose of the COM+ Server
¤ Component as being the server hosted on a separate machine?

Yes, which is why all you need on the client is the proxy.

¤ Question2:
¤ Why didn't my app prompted for the additional .dlls
¤ Microsoft.Practices.EnterpriseLibrary.Data.dll
¤ Microsoft.Practices.EnterpriseLibrary.Common.dll
¤ Microsoft.Practices.EnterpriseLibrary.Configuration.dll?

Don't know but they probably need to be in the GAC or your application directory.

¤ Question3:
¤ What's a good book available for reference on COM+. I have been on this
¤ project for weeks and ready to deploy to production and finelly these issues?
¤ This COM+ CRAP IS DEFINITELY NOT EASY!!!

I've only worked with COM+ and VB 6.0 components so I'm afraid I can't recommend a .NET book.


Paul
~~~~
Microsoft MVP (Visual Basic)
 
"Yes, which is why all you need on the client is the proxy."

Are you saying that the .dlls need to be on the clinet on which I installed
the proxy?
 
¤ "Yes, which is why all you need on the client is the proxy."
¤
¤ Are you saying that the .dlls need to be on the clinet on which I installed
¤ the proxy?
¤

Nope. That would defeat the purpose of remoting your component.


Paul
~~~~
Microsoft MVP (Visual Basic)
 
Actually my "Application Proxy" needed the dll to be on the client before it
could be installed. I had to load them in the GAC.

Thanks
 
Back
Top