Consuming dot net serviced component from .Net client?

[Eric Mamet]

I have created a .Net class that I configured to use through Component
Services (using regsvcs MTSWord.dll). The "Server" app.

I intend to use this "COM+" object in another .Net app: the "client"
app.

In visual studio, if I try to add a reference to my Com+ "Server" app,
I get the following error

"Converting the type library to a .Net assembly failed. TypeLibrary
MyLibrary was exported from a CLR assembly and can not be re-imported
as a CLR assembly."

Question 1: Any way around this?


Just in case you think I'm mad, this is what I am trying to do...
I need to use Word Automation from my ASP.Net app but I'd rather keep
anything to do with Word in another process space and that's why I was
trying to encapsulate this into a Serviced Component.

Question 2: Is there a better way to achieve the same?


Thanks


Eric

 

[JohnFol]

Is the MTSWord.dll of your own making? ie is it a wrapper written in .Net
that exposes the Word.Application object?

If so, how do you add the reference in the client app, via COM or via .Net?