 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / General / February 2005Windows Services & .NET Controls
Hi, I'm currently stuck with a big problem. I must develop a Windows service and an application to configure it and display what is happening. The problem is not really on the service side, but on the application side. I explain: The service is composed of a kernel dynamicaly loading plug-ins modules and starts the process of each module. Until nous, it's not that hard. The hard part is when it comes to the application to configure the service and display what is happening. Each module has it's own configuration panel and it's own display panel. I'm not that familiar with which information I can pass from my service to my application, so I need to know if there is a way I can pass an instance of a control from my service to my application and how can I do it? I've been searching all over the net to find it, but it seems nobody ever did it (or they didn't put the solution on the net) And I would have something else. In fact I would like to have the opinion of someone else on that. My software is designed that way : Module1 ---- ---- Module2 \ / Module3 ----Kernel ---- Module4 / \ Module5 ---- ---- Module6 Service ----Using----- Kernel Application ----Communicating With ---- Service Application ----Displays---- ModuleX.ConfigurationPanel or ModuleX.ActionPanel that came from the Service First of all, would anyone see a better design involving a service for displaying the information? if you do, what is it and why(if possible)? thanks ThunderMusic P.S. Sorry for the other post, I just did not verify the subject before sending... ;) you can use the remoting solution. []'s Sushi But you'd have to implement ISerializable on the controls... > you can use the remoting solution. > > []'s > Sushi ok, do you have an example of this? is it available on MSDN? Thanks a lot, it gives me a hint for where to begin... ;) > But you'd have to implement ISerializable on the controls... > > > you can use the remoting solution. > > > > []'s > > Sushi ok, after checking on MSDN, I found something about MarshalByReference and I think it could be useful, but there are no example of how it can be used (well, I didn't find one). So I cannot say if this is the thing I need. Does someone know about an example? thanks > ok, do you have an example of this? is it available on MSDN? > [quoted text clipped - 6 lines] > > > []'s > > > Sushi You can't use MarhalByRef in your example. The root of the object inheritance chain would have to be MarshalByRef, and Control is not. That's why you' have to implement ISerializable, in order to control the serialization process. Have a look at: http://samples.gotdotnet.com/quickstart/howto/doc/ISerializable.aspx for an example > ok, after checking on MSDN, I found something about MarshalByReference and > I [quoted text clipped - 15 lines] >> > > []'s >> > > Sushi ok, but the controls I use are always controls ? created, so can I make them inherit from MarshalByRefObject? and then use them that way? thanks a lot > You can't use MarhalByRef in your example. The root of the object > inheritance chain would have to be MarshalByRef, and Control is not. That's [quoted text clipped - 24 lines] > >> > > []'s > >> > > Sushi No you can't. The base Control class itself is not a MarshalByRef object. If you inherit from MarshalByRefObject then your class is not a control. If you inherit from Control (or any of it's child classes) you're root object is Object not MarshalByRefObject. > ok, but the controls I use are always controls ? created, so can I make > them [quoted text clipped - 37 lines] >> >> > > []'s >> >> > > Sushi thanks a lot... now it's clear... ;) > No you can't. The base Control class itself is not a MarshalByRef object. If > you inherit from MarshalByRefObject then your class is not a control. If you [quoted text clipped - 42 lines] > >> >> > > []'s > >> >> > > Sushi Will this serialisation allow me to pass the control from my service to the application or will I need to create an instance of the control in my app and get the informations to display what I need to display from the service? I mean, to get a reference to the existing control from the service would be much more efficient, if it can be done. I don't understand much about the serialisation in this case and/or MarshalByRefObject. I don't know the differences and if one or the other can be used considering all the controls used will be made by me, so they can inherit from both (or can't they?) > You can't use MarhalByRef in your example. The root of the object > inheritance chain would have to be MarshalByRef, and Control is not. That's [quoted text clipped - 24 lines] > >> > > []'s > >> > > Sushi Serialization and MarshalByRef are two different ways to access objects from a different AppDomain (or "process"). Serialization is like passing an object ByVal - the contents is copied from one process to the other, so that the object can be re-created in the calling process. MarshalByRef is like passing an object ByVal - a reference is copied from one process to the other, and a proxy object is created in the calling process. The client application has a reference to the proxy object. Any calls to methods/properties on the "proxy" object in the client get serialized and passed to the "real" object running in the server process. The server object performs the work and then serializes any return value to pass back to the proxy and the calling client code. I think for the application you are trying to create, you would be better off using MarshalByRef. However, you do not necessarily have to make your existing objects/controls MarshalByRef. It might be a better design to create monitoring objects designed specifically for this purpose. They will inherit from MarshalByRef, and their methods will be designed not to chatty. They expose a simple interface that doesn't require a lot of serialization for the method parameters or return values. The implementation of the methods handles all of the communication with the real controls you are trying to monitor, running in the service. Take a little time to familiarize yourself with remoting before diving into a solution. Do a google search for ".net remoting" and you should find a number of good articles that explain the hows and whys. If you have the time for a book, check out Rocky Lhotka's "Expert One-on-One Visual Basic .NET Business Objects". -Joshua Flanagan > Will this serialisation allow me to pass the control from my service to the > application or will I need to create an instance of the control in my app [quoted text clipped - 41 lines] >>>>>>[]'s >>>>>>Sushi thanks a lot, I'll see what I can do with it... The difference you made between the two makes things clearer. > Serialization and MarshalByRef are two different ways to access objects > from a different AppDomain (or "process"). [quoted text clipped - 66 lines] > >>> > >>>"ThunderMusic" <NOdanylat@sympatico.caSPAMATALL> a ?crit dans le message > >>>de > >>>news:uam23MGHFHA.2156@TK2MSFTNGP09.phx.gbl... [quoted text clipped - 9 lines] > >>>>>>[]'s > >>>>>>Sushi Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.