Linked by Eugenia Loli-Queru on Wed 20th Feb 2002 18:45 UTC
A lot of people have trouble understanding what .NET really is and what its goals are. Mostly because Microsoft has done a good job of confusing everybody using terms that are not self-explanatory or with terms that mean more that one thing. This editorial will present my thoughts on .NET, what it really is, what its motivations and goals are, and why it is the next "big thing." Should we embrace it or fear it? Both, I daresay.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Actually, with .NET server and XP, you can expose COM+ objects via SOAP without any code changes. I didn't make that eminently clear, but it basically takes the .NET infrastructure and applies it to the legacy COM+ platform.
As to the performance, your results are markedly different from mine. In comparing the same objects in VB6, VC(ATL), and C#.NET, I found that VC was noticable faster and scaled better than C#, and C# was roughly equal to VB6. For the sake of the test, I used a simple object, the ran did both raw processing and DB reads via OLEDB.
I still feel that there is no compelling reason for Apple to develop a .NET implementation in house though.