Visual C++ and Borland C++ Builder :: Breakdown
-
Hello. I have extensive experience designing and developing applications using Visual C++ and its various Win32 tools including MFC. I have also used Borland C++ Builder, but only on Win32 console projects. I would like to discuss some essential differences including advantages and disadvantages between the two IDE. - How would you compare MFC and Win32 API to WinForm (Borland - correct?). - Is it possible to access raw Win32 API directly when working under Borland C++? - Are there message queues in WinForm? How does it handle messages? - How does Borland C++ handle multithreading and multiple processes? - What is the future of Visual C++ and Borland C++? Thanks, Kuphryn
-
Hello. I have extensive experience designing and developing applications using Visual C++ and its various Win32 tools including MFC. I have also used Borland C++ Builder, but only on Win32 console projects. I would like to discuss some essential differences including advantages and disadvantages between the two IDE. - How would you compare MFC and Win32 API to WinForm (Borland - correct?). - Is it possible to access raw Win32 API directly when working under Borland C++? - Are there message queues in WinForm? How does it handle messages? - How does Borland C++ handle multithreading and multiple processes? - What is the future of Visual C++ and Borland C++? Thanks, Kuphryn
kuphryn wrote: - How would you compare MFC and Win32 API to WinForm (Borland - correct?). Don't you mean MFC/Win32 and VCL? kuphryn wrote: - What is the future of Visual C++ and Borland C++? Can't say for Borland. But Visual C++ is certainly not dying any time soon. From Bjarne Stoustrup's web site: Microsoft: Literally everything at Microsoft is built using various flavors of Visual C++ - mostly 6.0 and 7.0 but we do have a few holdouts still using 5.0 :-( and some products like Windows XP use more recent builds of the compiler. The list would include major products like: Windows XP Windows NT (NT4 and 2000) Windows 9x (95, 98, Me) Microsoft Office (Word, Excel, Access, PowerPoint, Outlook) Internet Explorer (including Outlook Express) Visual Studio (Visual C++, Visual Basic, Visual FoxPro) (Some parts of Visual Studio like the Base Class Libraries that ship with the .NET Framework were written using C# but the C# compiler itself is written in C++.) Exchange SQL There are also "minor" products like: FrontPage Money Picture It Project and all the games. It will be some time before all of this can be rewritten in C#! Kevin
-
kuphryn wrote: - How would you compare MFC and Win32 API to WinForm (Borland - correct?). Don't you mean MFC/Win32 and VCL? kuphryn wrote: - What is the future of Visual C++ and Borland C++? Can't say for Borland. But Visual C++ is certainly not dying any time soon. From Bjarne Stoustrup's web site: Microsoft: Literally everything at Microsoft is built using various flavors of Visual C++ - mostly 6.0 and 7.0 but we do have a few holdouts still using 5.0 :-( and some products like Windows XP use more recent builds of the compiler. The list would include major products like: Windows XP Windows NT (NT4 and 2000) Windows 9x (95, 98, Me) Microsoft Office (Word, Excel, Access, PowerPoint, Outlook) Internet Explorer (including Outlook Express) Visual Studio (Visual C++, Visual Basic, Visual FoxPro) (Some parts of Visual Studio like the Base Class Libraries that ship with the .NET Framework were written using C# but the C# compiler itself is written in C++.) Exchange SQL There are also "minor" products like: FrontPage Money Picture It Project and all the games. It will be some time before all of this can be rewritten in C#! Kevin
Also Visual C++ will be used when you don't want to allow users to do reverse engineering on your code to see how it works. Companies will write their sensitive modules in standard (Visual) C++ that implements various business secrets. Then they will use managed C++ to write an interface that can easily be accessed from .NET code. This however means that you need to learn to code managed C++, but only so much to write these (relatively simple) kind of interfaces. For many companies, using Dotfuscator will not be enough. /Patric