COM+ and Remoting

dotnet framework

    Next

  • 1. QueryInterface for System.IDisposable failed
    I am having a serviced component which is working fine when i run with a test windows application. The same when i deploy on com+ server and call it through webservices, i am getting the following erro "QueryInterface for System.IDisposable failed can anyone help me in this.
  • 2. Newbie: Do I still have to create and Register COM+ components ?
    Hello, I need to make a decision on what is the most effective technology for the Middle tier in a Web and Thick Client based system. CORBA, J2EE and maybe EJB or .NET. I am running in MS based environment with other MS services, so would prefer to develop a .NET based solution. The solution will need Transactions and possibly Queued components. I need high performance so I don't see Web servcies as being the answer. But I am confused on .NET Enterprise Services, because it seems that I still have to create COM+ components, and register them. My Boss doesn't like this because he has had bad experience of COM and keeps refering to 'dll hell' problems and having to keep registering and unregistering compoenents in the registery, which he is unhappy with. Is this true ? I would like to know how I can make use of Enterprise Services like Transactions and Queued components in the .NET environment without having to register COM objects ? I have searched around and not found any clear guidance. The .NET Pet Store does seem to imply having to develop COM+ components ? Thanks for any help and clarification on my understanding
  • 3. COM+ Application Administration
    I need to change the identity (user name and password) that a COM+ application is running under on a remote machine. Does anyone have an example of remotely administering COM+ applications in .NET? Thanks, -Tres
  • 4. MessageMover FormatName buffer error in Win 2000
    I'm getting error(0xc00e001f) only in windows 2000 while moving message from one queue to another if sourcePath and destPath is very long, but same code is working fine in win 2003 and win xp Csharp code: Messaging.MsgMover MessageMover= new MsgMover(); IMessageMover mc= (IMessageMover) MessageMover; mc.SourcePath(".\\PRIVATE$\\ Business_message_processor_deadqueue")); mc.DestPath(".\\PRIVATE$\\ Business_message_processor")); mc.MoveMessages(); vbscript code: Set OMessageMover = Wscript.CreateObject("QC.MessageMover") OMessageMover.SourcePath = ".\private$\Business_message_processor_deadqueue" OMessageMover.DestPath = ".\private$\Business_message_processor" cMessages = OMessageMover.MoveMessages Wscript.Echo cMessages, " messages moved from ", OMessageMover.SourcePath, " to ", OMessageMover.DestPath but its work fine if supplied AppName is small in sourcePath and destPath, like ".\private$\BMProcessor" instead of ".\private$\Business_message_processor_deadqueue". what I'm doing wrong ? Thanks! Syed.

COM+ and Remoting

Postby Ashish Sheth » Sat, 24 Apr 2004 16:42:47 GMT

Hi Dot net gurus..
Can I access a COM+ component in an application running on different
machine? How can I do this?
Can I use .NET remoting for this? what are the design issues I should
consider when accessing COM+ components using .NET remoting? what other
options I have if I want my components to be accessed by applications
running on other machines?

Please help me... this is urgent..

-- 
regards,
Ashish Sheth



Re: COM+ and Remoting

Postby JosMiguel Torres » Sat, 24 Apr 2004 19:56:08 GMT

yes, you can access with proxy. I think you need SOAP, see web services....

"Ashish Sheth" < XXXX@XXXXX.COM > escribien el mensaje


>> Hi Dot net gurus..
>> Can I access a COM+ component in an application running on different
>> machine? How can I do this?
>> Can I use .NET remoting for this? what are the design issues I should
>> consider when accessing COM+ components using .NET remoting? what other
>> options I have if I want my components to be accessed by applications
>> running on other machines?
>>
>> Please help me... this is urgent..
>>
>> --
>> regards,
>> Ashish Sheth
>>
>>



Re: COM+ and Remoting

Postby Ashish Sheth » Sat, 24 Apr 2004 22:05:41 GMT

thanks Jose,
but i need some more info??
from past 4 hours i m looking for this..
can you provide more info on how i can expose COM+ server application and
COM+ library application using remoting? what are the pros and cons?
It is so urgent for me

regards
Ashish




>> yes, you can access with proxy. I think you need SOAP, see web
services....
>>





Re: COM+ and Remoting

Postby JosMiguel Torres » Sat, 24 Apr 2004 22:33:43 GMT

hi, here a few links with more info....

-  http://www.**--****.com/ ;en-us;322627
-
 http://www.**--****.com/ 
pgdeployingapplications_65gz.asp
-
 http://www.**--****.com/ 
ml/comwscheckb.asp

is not easy, but very powerfull technology....

I hope this info let you undertstand .net remoting and com+...

regards


"Ashish Sheth" < XXXX@XXXXX.COM > escribien el mensaje


>> thanks Jose,
>> but i need some more info??
>> from past 4 hours i m looking for this..
>> can you provide more info on how i can expose COM+ server application and
>> COM+ library application using remoting? what are the pros and cons?
>> It is so urgent for me
>>
>> regards
>> Ashish




>>>> > Hi Dot net gurus.>
>>>> > Can I access a COM+ component in an application running on differen>
>>>> > machine? How can I do this>
>>>> > Can I use .NET remoting for this? what are the design issues I shoul>
>>>> > consider when accessing COM+ components using .NET remoting? what
othe>
>>>> > options I have if I want my components to be accessed by application>
>>>> > running on other machines>
>>>> >
>>>> > Please help me... this is urgent.>
>>>> >
>>>> > ->
>>>> > regards>
>>>> > Ashish Shet>
>>>> >
>>>> >
>> >
>> >
>



Similar Threads:

1.dcom vs com+ vs remoting

Hello.

I am doing a research on dcom, com+ and remoting.

We are about to develop a web application consisting 3 tiers ( web server,
application server, db server )

We are going to develop front end in asp.net and ms sql in the back end.

The middle tier mostly will be grabbing data from the db and give the result
to the front end.

I'd like to know what would be the better way to do this.

Should I use only one object in the middle tier that communicate to all the
threads requested from the web server? ( i'd like to know the pres and
cons )

I heard that dcom is better than com+ in particular situation so I'd like to
know in what situation remoting would be the best fit in the middle tier and
why

Thanx in advance


2.COM and Remoting

I am having the following problem using 1.1 Framwork. Before moving to 2.0 I 
would like to know if anyone had the same kind of problem!

I have a class A which uses a COM component (third party, so it can't be 
changed). This A class comunicates with another another class, B. This is a 
bi-directional comunication (B calls a method of A which, then, calls a 
method of the COM component).
Everything works fine until I the comunication between A and B is done 
through remoting.

When B resides in an application server the comunication between A and B 
works fine but when B calls a method of the COM component the system hangs. 
I have no idea of why this happens!

Thank you!

Rogio Manente
 XXXX@XXXXX.COM  


3.COM+ to Remoting Transition

We are a corporate shop that builds apps to run behind the firewall. In the
"Visual Studio Classic" world, we had used COM+ to host mid-tier components,
the primary purpose of these components to communicate with the SQL Sever
back end and return data.

Our clients are authenticated to run the app via Integrated Windows
authentication. Their captured credentials then allow them to run components
hosted by COM+.  The COM+ application is run under a domain identity that is
used to authenticate to SQL Server (we use Integrated Security=SSPI in the
SQL Server connection strings). So, in effect, the component executes based
on the calling users credentials, but makes data calls on that users behalf
using its own identity to talk to the db.

This has worked quite well for us in that we don't need to watch out for
exceeding our SQL Server licensing, and the identity used to access
production data is in one place and secure, known only to a select few
people. Our auditors seem happy with this approach, too. (We use a similar
type identity scheme for our development and test environments).

My question: How can we build a remoting environment (SAO, Single Call,
hosted in IIS) that allows us the same transparency as to identity passed to
the db? We really don't want to have the db access credentials sitting in a
bunch of web.config files. Granted, access to these can be limited, but it
still leaves a lot of maintenance should we have to start changing
passwords.

Has anyone had to encounter these transitional issues? There's absolutely no
literature out there that deals with it.

We would be very interested in what y'all have to offer.

TIA,
Bill


4.COM+ and Remoting

I haven't dug very far into remoting yet and I'm wondering if Remoting as
the same features as COM+ (queuing, pooling, transactions) or is Remoting a
whole different distributed computing animal separate from what COM+ tries
to achieve?

Thanks,
Jason


5.State COM+ and remoting

6. COM+ and Remoting

7. COM and Remoting

8. COM+ Web Services (ie remoting com+ from IIS)



Return to dotnet framework

 

Who is online

Users browsing this forum: No registered users and 22 guest