Need help getting started with a broadcasting tool
-
Hi, I'm quite new to the whole .NET/C# thingy (reading some books now) and I was thinking of something useful to build @ the office. This is - basically - what I've got in mind: We have a server on which we build our application. On the server, there should be an application running which accepts commands. The commands can be sent from an application every workstation has to run. If someone sends a command (like: start new build) this single person has to be notified if it was possible to start the command (perhaps there was a build already running?). If the command is executed, the app on the server has to broadcast a message to everybody who has the app running so they know a new build was started. At the moment all programmers log in to the server (via remote desktop) and double clicks an icon on the desktop. We - obviously - want to limit the access so programmers don't need to log in on the server. I am thinking of concepts like TCP/IP and/or WCF. Who can help me on my way? Where to start? Thanks in advance for any information given! Regards, Ted
- Life would be so much easier if I had the source code! - If C# had true garbage collection, most applications would delete themselves upon execution ;)
-
Hi, I'm quite new to the whole .NET/C# thingy (reading some books now) and I was thinking of something useful to build @ the office. This is - basically - what I've got in mind: We have a server on which we build our application. On the server, there should be an application running which accepts commands. The commands can be sent from an application every workstation has to run. If someone sends a command (like: start new build) this single person has to be notified if it was possible to start the command (perhaps there was a build already running?). If the command is executed, the app on the server has to broadcast a message to everybody who has the app running so they know a new build was started. At the moment all programmers log in to the server (via remote desktop) and double clicks an icon on the desktop. We - obviously - want to limit the access so programmers don't need to log in on the server. I am thinking of concepts like TCP/IP and/or WCF. Who can help me on my way? Where to start? Thanks in advance for any information given! Regards, Ted
- Life would be so much easier if I had the source code! - If C# had true garbage collection, most applications would delete themselves upon execution ;)
-
Use WCF. Make your own method, for example : Build(). If build already running, just throw exception. Use event or callback to broadcast to all members, for example : Build is running... Build is finished...
I got that far :S I need help getting started up with the whole communication stuff in WCF.
- Life would be so much easier if I had the source code! - If C# had true garbage collection, most applications would delete themselves upon execution ;)
-
I got that far :S I need help getting started up with the whole communication stuff in WCF.
- Life would be so much easier if I had the source code! - If C# had true garbage collection, most applications would delete themselves upon execution ;)