re: "Does it work for protocols other than HTTP", even though it uses SOAP in places the thing is hardwired to HTTP and WAP. Other protocols (Jabber, SMTP, etc.) need not apply:-(.
There's plenty of other things to complain about in the current set of specs, I wrote up some of them on my weblog.
Digital Identity also has some initial comments here, and Doug Kaye is promising comments soon, too.
ArsTechnica article inaccuracies
on
What is .NET?
·
· Score: 1
Normally I like the ArsTechnica stuff, and this one was good in that it separated out managed code and managed data (mosts people shmoosh them together), but this one had tons of annoying technical innaccuracies. They bugged me so much I posted a rebuttal here.
Actually, no, C# is _not_ a version of C++ bastardized to work with COM. C# & the.Net runtime (CLR) is a type-safe programming language & runtime designed for building component-based apps, NOT COM-based apps. There is a BIG difference. There is technology to allow C# components call into DLLs and COM objects, but this is referred to as 'interop', and the DLLs and COM objects are considered 'legacy'. Microsoft has done many questionable things in the past, but in my opinion they're doing this one 100% right.
Slashdot Mirror
re: "Does it work for protocols other than HTTP", even though it uses SOAP in places the thing is hardwired to HTTP and WAP. Other protocols (Jabber, SMTP, etc.) need not apply :-(.
There's plenty of other things to complain about in the current set of specs, I wrote up some of them on my weblog.
Digital Identity also has some initial comments here, and Doug Kaye is promising comments soon, too.
--Peter
http://www.razorsoft.net/weblog
Yes, it can. And design-by-contract, too.
Normally I like the ArsTechnica stuff, and this one was good in that it separated out managed code and managed data (mosts people shmoosh them together), but this one had tons of annoying technical innaccuracies. They bugged me so much I posted a rebuttal here.
Effectively, yes. The Sytem.Reflection.Emit.ILGenerator class can emit IL opcodes into the instruction stream.
Actually, no, C# is _not_ a version of C++ bastardized to work with COM. C# & the .Net runtime (CLR) is a type-safe programming language & runtime designed for building component-based apps, NOT COM-based apps. There is a BIG difference. There is technology to allow C# components call into DLLs and COM objects, but this is referred to as 'interop', and the DLLs and COM objects are considered 'legacy'. Microsoft has done many questionable things in the past, but in my opinion they're doing this one 100% right.