Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > C# and C > C# 2005 > C# 2005
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
C# 2005 For discussion of Visual C# 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the C# 2005 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
 
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old February 24th, 2009, 06:43 PM
Authorized User
 
Join Date: Nov 2006
Location: Valparaiso, IN, USA.
Posts: 93
Thanks: 0
Thanked 1 Time in 1 Post
Default Problem with Remoting

I'd like to use remoting to alert a users desktop when an event occurs on a server.

Having never used remoting before I reviewed a couple of samples on the subject. And I have a question.

How do I access the client activated object on the remote-server application?
__________________
What you don\'t know can hurt you!
  #2 (permalink)  
Old March 5th, 2009, 10:49 AM
Authorized User
 
Join Date: Nov 2006
Location: Valparaiso, IN, USA.
Posts: 93
Thanks: 0
Thanked 1 Time in 1 Post
Default Problem with Remoting

I resolved the issue I was having. It turns out that the service that runs on the remote server doesn't need to know much about the object that will be instantiated on itself. Just the type and name that the object will be created as.

After instantiating and registering the Channel. You setup the listener and you are through with the server.
Code:
 
RemotingConfiguration.RegisterWellKnownServiceType(
  System.Type.GetType("RemoteXport.myRemoteClass, RemoteXport"),
  "RemoteTest", WellKNownObjectMode.SingleCall);
What I learned was that the remote class can be as complicated as you like. In my case I wanted to alert the user when an event occured on another server. So the remote server class runs on the user's machine and listens. The remote client runs on the machine on which important events will occur. When the event happens, the remote client is started up which instantiates the remote object on the user's machine. That object can open a windows form to alert the user, sound alarms or launch another appllication all of which depend on the access rights of the object and the user it runs as.

That's where I'm stuck now, figuring out how to navigate the complex security restrictions in a corporate environment. But this will be the subject of another post.
__________________
What you don\'t know can hurt you!
 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Remoting Callback problem downboat BOOK: Professional C#, 2nd and 3rd Editions 2 June 8th, 2011 02:13 AM
NET Remoting problem baga General .NET 0 March 23rd, 2007 12:58 AM
Remoting Problem Pallavs20 General .NET 0 October 21st, 2005 09:12 AM
.Net Remoting Problem farhan_iac General .NET 0 June 11th, 2004 03:13 AM
Remoting problem roypjob .NET Web Services 1 January 20th, 2004 09:12 AM



All times are GMT -4. The time now is 12:36 AM.


Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.