Friday, May 03, 2002

Charles Cook was wondering about MC++-only features for doing 100% managed work (when verifiability doesn't matter, of course). Some examples of this are: exception filters, family-and-assembly member accessibility, and on-heap manipulation of boxed value types without adjustor interfaces. Although C# doesn't expose these features directly, there are reasonable workarounds, and these differences aren't meaningful enough to make me switch to MC++ for all my new, 100% managed coding. Productivity is a feature, too! [Peter Drayton's Radio Weblog] Peter then has two examples. 9:32:40 PM

C# striking a chord with programmers. Microsoft's new programming language is gaining in popularity, with usage nearly doubling in the last six months, a study shows. [CNET News.com] I have been doing a lot of C# programming lately (as opposed to MC++). What a refreshing and enjoyable experience. 9:13:30 PM

Did you ever need to call one function with the same name from more than a one class, or just make an object based on a class name which you got as an function parameter? Well, here's how. Article. May 3, 2002. 8:21:38 AM

Use a simple Windows form to verify .NET's capability to consume Apache, CapeClear, Delphi, and other rpc/encoded Web services. The Visual Basic .NET code is available for downloading. Article. May 3, 2002. I espeically liked: Sun's Scott McNealy accused Microsoft of "hijacking XML" during his March 2002 JavaOne conference keynote. The accusation undoubtedly relates to Web services, where Microsoft and IBM have taken the reins with the SOAP, WSDL, UDDI, and, more recently, the WS-Inspection Language (WSIL) and the Web Service Interoperability Organization (WS-I). To see for myself whether Microsoft had nefarious intentions in the SOAP interoperability sector, I decided to write a simple Windows form app to exercise Web References from a few rpc/encoded sample Web service created by competitors' toolkits (see Figure 1). ... My tests so far indicate that Microsoft is sticking to today's Web service standards and Scott's accusation isn't credible. No one can gain a monopoly on XML tag names and namespaces, regardless of their marketing and financial clout. My take is that McNealy made the claim in a fit of pique over a late invitation from Microsoft and IBM to join WS-I as a regular member, not a founder. (J2EE release 1.4's delay to January 2003 might be a contributing factor.) Hopefully, WS-I—with or without Sun as a member—will deliver soon on its promise of implement 8:19:36 AM

Survey Finds .NET and J2EE Neck-and-Neck [ActiveWin] 8:11:35 AM

Ok, I did it. I was playing around and I have an Instant Outliner. Pretty cool. 1:09:03 AM

© Copyright 2002 Sam Gentile.