David B. Bitton [mailto:[EMAIL PROTECTED]] wrote:
> new sk00l Heheh... cool. ;) First, if you just need signaling you might want to consider firing WMI events. It's abstract and easy to hook into with System.Management, though there will be a slight learning curve if you've never used WMI before. If it's not just signaling, what would probably want to do then is register a well-known object in a Windows service using the TCPChannel. Then in both your ASP.NET and WinForms applications, make the proper client remoting config entries that point the afforementioned well-known object. Then your both applications can be oblivious to remoting all together. The type would appear to be running within the application's space as far as programming goes, but due to the remoting configuration, actually be calling out over the TCPChannel to the Windows service instance. This would also allow you to switch protocols without the application even needing to know. Check out this tibit on server activation[1]. Next, here's the base link for info on remoting configuration[2], but of specific interest is the client configuration[3]. Finally, this has been hashed over numerous times and several discussions on the topic can be found in the archives. HTH, Drew .NET MVP [1] ms-help://MS.VSCC/MS.MSDNVS/cpguide/html/cpconserveractivation.htm [2] ms-help://MS.VSCC/MS.MSDNVS/cpgenref/html/gnconsystemruntimeremotingelement. htm [3] ms-help://MS.VSCC/MS.MSDNVS/cpgenref/html/gnconwellknownclientinstance.htm You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
