Hi,
We wish to kick off development of new windows based management client for our system. Our legacy application was an all-in-one server/client written in C++ using MFC. It contains portions of code that we do not wish to rewrite (a proprietary persistent database builder, among other things). However, the system was split up into a client and a server recently, so things are going in the right direction.
Understandably, 7 year old clients look very, very dated. It is my intention to adopt the latest in terms of thin client development enviroments - but remain in the application domain (no web based management). I've seen gorgeous .NET components for charting and diagrams which support C# and VB.NET. As an avid C/C++ developer (working in embedded systems) i prefer C# between the two.
My question, therefore, is whether or not we can and should use C# for our client. In terms of RAD, available components and documentation - it seems fantastic. On the other hand, we have large amounts of C++ code that we want to reuse. I also heard rumors that MS is pushing for Managed C++ in VS 2005 for such applications and wishes to keep C# for web-based clients (I have yet to find a source that approves this, though).
Any tips, hints, pointers to relevant articles are appreciated.
Most suitable env for windows based client?
Hot Topic
- Scope_identity equal to 0 from a stored proc as well
- Authentication error with web service on https
- Inconsistent InvalidCastException and FormatException errors
- Convert from byte array to float...
- access invisible characters?
- XSLTCompiledTransform And Caching
- Is this possible and if so, how?
- advice on different singleton implementations?
- How to query current processor load from .NET application?
- Viewing SOAP packet sent to a vendor's Web Service
Most suitable env for windows based client?
Brent Snyder
Personally, I prefer C#. But if you wanted to leverage some of your old C++, then you should consider managed c++. If you want a break, then go with c#.
raysblog
It's true that Managed C++ has received a lot of attention in Visual Studio 2005, but I have never heard anyone mention that it's supposed to be the primary language for Windows development.
Actually, you can use both languages in the same application. Your UI could be written in C#, making use of all design-time features and components available, and would call into a dll written in Managed C++.