Hi,
I have been working on Win32/MFC/COM for quite sometime. Now i am planing to make a move - to .NET/C#.
I have some dobuts regarding the same :-
1) What are the architectural challenges one may face when making such a change
How different is it to architect solutions in C#/.NET than in Win32/MFC
2) What are the design challenges one may face when designing solution in .NET/C# (compared to Win32/MFC)
3) What are the challenges associated with WinForms when compared to MFC
Thanks in advance
Shine
Migrating from Win32/MFC to .NET Platform - Challenges ?
Hot Topic
- Parsing;
- Can not creat Site collection in wss 3 release version
- IE Crashing when opening Sharepoint list
- Problem in installing SPS 2007
- Development Approach
- UML STATIC MODELING IN PRODUCT LINE ENGINEERING (PLE) with SPARX EA
- IE Crashes on view of Office document on SPS2003
- Integration of web app to Sharepoint Portal 2007
- Restoring Share Point DB with a different Name
- The participant 'HelloWorldParticipant' does not support action
SharePoint Products
- Image displayed based on content type
- Transaction across Applications
- DSl, Software Factory and Banking Software
- DOM Reference
- Applying Policy to participant CSFService
- Has the official release of Sharepoint Server 2007 been released?
- Message visualizer
- rename documents in document library
- Special characters and paged grouped views
- Passing the Excel parameters to the backend
Migrating from Win32/MFC to .NET Platform - Challenges ?
jackdchen
.NET doesn't enforce any specific architecture or design.
It give you better productivity compared with MFC
Arnon