.NET stuff: dispose guidelines and c++/cli

Monday 16 May 2005This is 18 years old. Be careful.

I haven’t even read all this stuff, much less understand it, but they seem like things in my future.

Dispose, Finalization, and Resource Management is an in-depth treatise on the nitty-gritty details about the end of life for .NET objects. Modern languages seem to prefer not promising much when it comes to destroying objects, and .NET is no different. Some day, this is going to save my ass.

Modern Language Features of Visual C++ 2005 is a detailed overview of the .NET features being added to C++. It seems a bit overwhelming trying to merge the complexity of C++ with the deep new features of .NET, but Microsoft has never been shy about loading on developer features. I think their strategy is to guarantee developers have enough Microsoft choices in front of them that they feel like they’re choosing among technologies without ever considering a non-Microsoft offering.


One thing that they have yanked from VC2005 is support for __asm code. Thank God. That will discourage those dinosaurs (are you reading this, Dennis?) from doing a little inline stack manipulation for fun.
reading the stuff about c++ it would seem c++ is the new asm. I presume there are massive advantages in using c++ in .Net that makes the amount of work (compared to even Java or C#) required worth while as well as seemingly needing to know where things are created in terms of heap/stack etc. I can understand using it for systems programming and interfacing with hardware etc. but I *thought* .Net was mainly aimed at the enterprise?

Add a comment:

Ignore this:
Leave this empty:
Name is required. Either email or web are required. Email won't be displayed and I won't spam you. Your web site won't be indexed by search engines.
Don't put anything here:
Leave this empty:
Comment text is Markdown.