I never understood how it is possible that Windows programmers accept they have to rewrite their applications every couple years: first they had to use Win32 API, then MFC, then ATL/COM, now they have to use .Net - and basically they are told to switch to new programming language for this last change - and who knows what comes next
Very interesting point. By the way, we are told every year to switch to upgraded platforms and the reason almost always stated is the platform agnostic nature of .NET. Here the talk goes about the structure exception handling mechanism which is expected to give a general overview about the preference of .NET over older platforms:
The obvious problem with these older techniques is the tremendous lack of symmetry. Each
approach is more or less tailored to a given technology, a given language, and perhaps even a given
project.
To put an end to this madness, the .NET platform provides a standard technique to send and
trap runtime errors: structured exception handling (SEH).
The beauty of this approach is that developers now have a unified approach to error handling,
which is common to all languages targeting the .NET platform. Therefore, the way in which a C#
programmer handles errors is syntactically similar to that of a VB programmer, or a
C++ programmer
using
C++/CLI.
As an added bonus, the syntax used to throw and catch exceptions across assemblies and machine
boundaries is identical. For example, if you use C# to build a Windows Communication Foundation
(WCF) service, you can throw a SOAP fault to a remote caller, using the same keywords that allow you to
throw an exception between methods in the same application.
Another bonus of .NET exceptions is that rather than receiving a cryptic numerical value that simply
identifies the problem at hand, exceptions are objects that contain a human-readable description of the
problem, as well as a detailed snapshot of the call stack that triggered the exception in the first place.
Furthermore, you are able to give the end user help-link information that points the user to a URL that
provides details about the error, as well as custom programmer-defined data.
The bold phrase is almost everywhere. Imagine the next version even better packaging all those advantages will be saying:
"
To put an end to this madness regarding the .NET platform ...
.NET++ provides a solution" << for example. And then .NET++ then .NET+=3 ...
And what will only be left from the current .NET version seems to be this:
Code:
for ( int i = 1; i <=10; i++)
{
Upgrade_To(".NET" + i.ToString());
Console.WriteLine(".Net upgraded to: {0} \nWaiting for the next decade", i );
}