Sam Gentile: "they confuse the language with features that are actually available in the BCL." Thanks, Sam. That's definitely food for thought. I wonder if this is a title issue, or if it needs to be addressed at a lower level in the article? Can you publish a book or article on a Framework Class Library capability, use examples in one language, and let users of other languages figure it out? Or do you publish something that has examples in several languages? This is something I've thought about a lot. My preference with books is to see most of the examples in C#, and have a few VB.NET and Managed C++ examples lightly sprinkled on top. I'd like to here what other folks think. [Brian Jepson's Radio Weblog]
Well, with a title "C# Object Serialization" it is right away a title problem. ".NET Object Serialization Using C#" or something like that would be a step in the right direction. And then in the article, The important thing is to empahasize that the features are in the Runtime and BCL, and not the language. All .NET languages do is express the semantics of the runtime and the BCL. Period. Drew makes the same point here. Its a subtle thing some people think but it is fundamental to understanding .NET versus the "old way" of doing things. As for my preference, I know from growing with COM+ 2.0, then NGWS and then .NET, that C# is THE system language of .NET. I would prefer to see samples in that. I personally don't read anything that has VB.NET code in it but that's me and my opinion only. I, of course, have fondness for MC++, as you know, but realize it is too complex for samples and books in the general case.
7:25:23 PM 
|
|
