Client-server distributed applications, what's the best .Net technology
-
I have the need to build a client-server system. It will all be working on an intranet, distributed on multiple PCs. One will be a server application, hosted on a PC, that will manage the data. The second will be a client application. It will be used to read and modify the data. This application already exists, for the most, and is a C++ application. It is huge so it cannot be done from scratch again. I have seen that I can expose a COM interface from .Net, so I will probably do a library that will be used as an interface between my old C++ app and the .Net architecture. I also need the server to be able to send notifications to the client applications when some changes occurs, so I need a subscription mechanism. I am relatively new to .Net so I am not sure what the best technology is. I have looked at WCF, but it does not seem ideal for the subscription/notification part. Am I wrong? What else is there that could be better?
-
I have the need to build a client-server system. It will all be working on an intranet, distributed on multiple PCs. One will be a server application, hosted on a PC, that will manage the data. The second will be a client application. It will be used to read and modify the data. This application already exists, for the most, and is a C++ application. It is huge so it cannot be done from scratch again. I have seen that I can expose a COM interface from .Net, so I will probably do a library that will be used as an interface between my old C++ app and the .Net architecture. I also need the server to be able to send notifications to the client applications when some changes occurs, so I need a subscription mechanism. I am relatively new to .Net so I am not sure what the best technology is. I have looked at WCF, but it does not seem ideal for the subscription/notification part. Am I wrong? What else is there that could be better?
Instead of the COM dll you might consider using managed C++ for the old app. This will let you mix both managed (.NET) and unmanaged code in the same files and will give you all of the .NET stuff you might want. The other stuff, someone else might have to comment on. I use c# for my client server apps but I use straight sockets for my information.
-
Instead of the COM dll you might consider using managed C++ for the old app. This will let you mix both managed (.NET) and unmanaged code in the same files and will give you all of the .NET stuff you might want. The other stuff, someone else might have to comment on. I use c# for my client server apps but I use straight sockets for my information.
-
I have the need to build a client-server system. It will all be working on an intranet, distributed on multiple PCs. One will be a server application, hosted on a PC, that will manage the data. The second will be a client application. It will be used to read and modify the data. This application already exists, for the most, and is a C++ application. It is huge so it cannot be done from scratch again. I have seen that I can expose a COM interface from .Net, so I will probably do a library that will be used as an interface between my old C++ app and the .Net architecture. I also need the server to be able to send notifications to the client applications when some changes occurs, so I need a subscription mechanism. I am relatively new to .Net so I am not sure what the best technology is. I have looked at WCF, but it does not seem ideal for the subscription/notification part. Am I wrong? What else is there that could be better?
-