"The primary purpose of the tool is to be able to quickly detect node-level changes between versions of an XML document, and with enough granularity to support efficient patch and merge scenarios. The patch format can be used for fairly terse delta-encoding to transfer incremental changes across the wire as well. The tool is officially called "XmlDiff and Patch" and is implemented in managed code (sorry, no MSXML version). Currently you can only perform XML Diff through the web page, but the assembly should be available on that site very soon. I think it is considerably better than anything else available today, in terms of both performance and accuracy, and the API is a good fit with the System.Xml libraries, so it should be really easy for any VB/J#/C#/F# programmers to use."
[netcrucible.com/blog]
"Microsoft’s Rotor project, recently refreshed on June 25, 2002, includes source code for the Common Language Infrastructure (CLI) execution engine and frameworks, as well as compilers and other developer tools. The Rotor code can be used, modified, and re-distributed, for non-commercial experimentation, as a basis for courseware or lab projects, or as a guide to those who are developing their own CLI implementations under a simple shared-source license."
[radio.weblogs.com/0105852/]
"Welcome to the Windows Forms FAQ. Questions & Answers in this FAQ are from newsgroup posts, various mailing lists and the employees of Syncfusion. I have tried to mention the source wherever I could."
George is a long-time colleague of mine at DevelopMentor as well as the chief author on MFC Internals, which spawned ATL Internals.
[radio.weblogs.com/0105852/]
From Keith Wedinger: Rumble in the jungle: J2EE versus .Net, Part 1 from JavaWorld.com. Heard a lot about .Net versus J2EE (Java 2 Platform, Enterprise Edition)? Wondering what that conflict means for you? Well, we wondered the same thing. So, drawing on our combined experiences from both sides of the fence, we put together an unbiased explanation as to how J2EE and .Net match up. Make no mistake, finding unbiased opinions is difficult—both camps' marketing hype has kicked into overdrive. This two-part series will help you better understand how the two technologies differ and how they are alike, all in the context of building a Web application from design right through to deployment.
"The .NETCF Resource Site is a joint venture between Developmentor and JW Hedgehog, Inc. We've been working fevereshly to bring things online. We are very proud of our Compact Framework Reference Page, which is the most complete reference of .NET CF supported classes and methods we know of."
From Francis Upton: Explore any ActiveX/COM object with the nogoop ActiveX/COM Inspector.
Make Automation programming easier by viewing or modifying properties,
and invoking methods on these ActiveX/COM objects. The Inspector
includes a graphical control design surface, a complete type library
browser, and can register and unregister type libraries. It
automatically converts type libraries/controls to .NET assemblies, and
allows you to browse and access .NET objects (it includes the complete
capabilities of the .NET Component Inspector). Requires the .NET
Framework runtime (CLR).