|
|
You're in the
dotnet distributed apps
group:Process to process communication with COM+ or .Net remoting interf
dotnet distributed apps:
I would like to create a Windows service application which is always alive.
Clients can connect and monitor activity or change settings. To allow the clients to connect I want to use COM+ or .NET remoting but all examples I've seen are not applications, they are esentially libraries. It is possible to use componennts for process to process communication? Does anyone know of an example of doing so? --
The project I am working on does exactly what you are describing, so I can
say that yes, it is possible to do so. I haven't seen a specific example, but I can describe in general terms what you need to do. First, take an example of building a .Net Remoting application as a regular exe application.. You should be able to find a sample application for one of those easily enough. In the MSDN library, there is an article entitled, "Buiding a basic .Net Remoting Application". Part of that process involves building a remotable object, which is something that inherits from MarshalByRefObject. Any application that can include a remotable object can then serve as the host server application for the remotable object. So, instead of including the remotable object in a regular application, create a new Windows Service, and include it in there. Do everything exactly as you would do it for an executable application, but start it as a service instead. (If you don't know how to do that, there are plenty of samples around. It's easy.) If you are trying to work through the process, but get a little stuck, ask a more specific question. [quoted text, click to view] "Ralph Flaugher" wrote:
> I would like to create a Windows service application which is always alive. > Clients can connect and monitor activity or change settings. To allow the > clients to connect I want to use COM+ or .NET remoting but all examples I've > seen are not applications, they are esentially libraries. It is possible to > use componennts for process to process communication? Does anyone know of an > example of doing so? > --
Check out these links for some examples:
Chat Client example http://support.microsoft.com/default.aspx?scid=kb;en-us;312114 and on GotDotNet there are several examples: http://samples.gotdotnet.com/QuickStart/howto/default.aspx?url=/quickstart/howto/doc/Remoting/firstserver.aspx Thanks, Sam -- _______________________________ Sam Santiago ssantiago@n0spam-SoftiTechture.com http://www.SoftiTechture.com _______________________________ [quoted text, click to view] "David" <David@blackdeck.com> wrote in message news:C4B01947-404E-4638-908F-D01E7418ACD5@microsoft.com... > The project I am working on does exactly what you are describing, so I can > say that yes, it is possible to do so. I haven't seen a specific example, > but I can describe in general terms what you need to do. > > First, take an example of building a .Net Remoting application as a regular > exe application.. You should be able to find a sample application for one of > those easily enough. In the MSDN library, there is an article entitled, > "Buiding a basic .Net Remoting Application". > > Part of that process involves building a remotable object, which is > something that inherits from MarshalByRefObject. Any application that can > include a remotable object can then serve as the host server application for > the remotable object. So, instead of including the remotable object in a > regular application, create a new Windows Service, and include it in there. > Do everything exactly as you would do it for an executable application, but > start it as a service instead. > > (If you don't know how to do that, there are plenty of samples around. It's > easy.) > > If you are trying to work through the process, but get a little stuck, ask a > more specific question. > > > > "Ralph Flaugher" wrote: > > > I would like to create a Windows service application which is always alive. > > Clients can connect and monitor activity or change settings. To allow the > > clients to connect I want to use COM+ or .NET remoting but all examples I've > > seen are not applications, they are esentially libraries. It is possible to > > use componennts for process to process communication? Does anyone know of an > > example of doing so? > > -- > > Ralph Flaugher
Thanks for your reply. Here is a link I found after my post which might help
you as well: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod29.asp Ralph [quoted text, click to view] "David" wrote:
> The project I am working on does exactly what you are describing, so I can > say that yes, it is possible to do so. I haven't seen a specific example, > but I can describe in general terms what you need to do. > > First, take an example of building a .Net Remoting application as a regular > exe application.. You should be able to find a sample application for one of > those easily enough. In the MSDN library, there is an article entitled, > "Buiding a basic .Net Remoting Application". > > Part of that process involves building a remotable object, which is > something that inherits from MarshalByRefObject. Any application that can > include a remotable object can then serve as the host server application for > the remotable object. So, instead of including the remotable object in a > regular application, create a new Windows Service, and include it in there. > Do everything exactly as you would do it for an executable application, but > start it as a service instead. > > (If you don't know how to do that, there are plenty of samples around. It's > easy.) > > If you are trying to work through the process, but get a little stuck, ask a > more specific question. > > > > "Ralph Flaugher" wrote: > > > I would like to create a Windows service application which is always alive. > > Clients can connect and monitor activity or change settings. To allow the > > clients to connect I want to use COM+ or .NET remoting but all examples I've > > seen are not applications, they are esentially libraries. It is possible to > > use componennts for process to process communication? Does anyone know of an > > example of doing so? > > --
I have a question may be you can answer. I have a got my service app to host
a .Net remote component but there is seems to be no point. The .Net remote component has no access to my service's data which is what I want. I want the .Net remote component to provide an interface to the service. Is this possible? It seems the service is just a container for the .Net remote component and there is no shared data. Ralph [quoted text, click to view] "David" wrote:
> The project I am working on does exactly what you are describing, so I can > say that yes, it is possible to do so. I haven't seen a specific example, > but I can describe in general terms what you need to do. > > First, take an example of building a .Net Remoting application as a regular > exe application.. You should be able to find a sample application for one of > those easily enough. In the MSDN library, there is an article entitled, > "Buiding a basic .Net Remoting Application". > > Part of that process involves building a remotable object, which is > something that inherits from MarshalByRefObject. Any application that can > include a remotable object can then serve as the host server application for > the remotable object. So, instead of including the remotable object in a > regular application, create a new Windows Service, and include it in there. > Do everything exactly as you would do it for an executable application, but > start it as a service instead. > > (If you don't know how to do that, there are plenty of samples around. It's > easy.) > > If you are trying to work through the process, but get a little stuck, ask a > more specific question. > > > > "Ralph Flaugher" wrote: > > > I would like to create a Windows service application which is always alive. > > Clients can connect and monitor activity or change settings. To allow the > > clients to connect I want to use COM+ or .NET remoting but all examples I've > > seen are not applications, they are esentially libraries. It is possible to > > use componennts for process to process communication? Does anyone know of an > > example of doing so? > > --
You have total control over that. The remoted object is simply a component
of your windows service, so you can decide how you want to provide whatever data required to it and it can expose it as remoted methods to the clients. For example, you could have another object that acts as a data provider to the remoted component and is contained within it. Whenever the remoted component needed data it could invoke this data provider for the required data. Essentially your remoted object is simply a facade for another object that provides the data. Thanks, Sam -- _______________________________ Sam Santiago ssantiago@n0spam-SoftiTechture.com http://www.SoftiTechture.com _______________________________ [quoted text, click to view] "Ralph Flaugher" <RalphFlaugher@discussions.microsoft.com> wrote in message news:AE5895F1-5E93-4903-A719-45B5BFBEA215@microsoft.com... > I have a question may be you can answer. I have a got my service app to host > a .Net remote component but there is seems to be no point. The .Net remote > component has no access to my service's data which is what I want. I want > the .Net remote component to provide an interface to the service. Is this > possible? > > It seems the service is just a container for the .Net remote component and > there is no shared data. > > Ralph > > "David" wrote: > > > The project I am working on does exactly what you are describing, so I can > > say that yes, it is possible to do so. I haven't seen a specific example, > > but I can describe in general terms what you need to do. > > > > First, take an example of building a .Net Remoting application as a regular > > exe application.. You should be able to find a sample application for one of > > those easily enough. In the MSDN library, there is an article entitled, > > "Buiding a basic .Net Remoting Application". > > > > Part of that process involves building a remotable object, which is > > something that inherits from MarshalByRefObject. Any application that can > > include a remotable object can then serve as the host server application for > > the remotable object. So, instead of including the remotable object in a > > regular application, create a new Windows Service, and include it in there. > > Do everything exactly as you would do it for an executable application, but > > start it as a service instead. > > > > (If you don't know how to do that, there are plenty of samples around. It's > > easy.) > > > > If you are trying to work through the process, but get a little stuck, ask a > > more specific question. > > > > > > > > "Ralph Flaugher" wrote: > > > > > I would like to create a Windows service application which is always alive. > > > Clients can connect and monitor activity or change settings. To allow the > > > clients to connect I want to use COM+ or .NET remoting but all examples I've > > > seen are not applications, they are esentially libraries. It is possible to > > > use componennts for process to process communication? Does anyone know of an > > > example of doing so? > > > -- > > > Ralph Flaugher
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |