Here. From Michael Weinhardt: "Microsoft plans to deliver this fall a minor update to its Visual Studio.Net suite of development tools, said Eric Rudder, senior vice president of Microsoft's developer and platform evangelism."
Here. "Some of the highlights of the new release include the following:
"- Attribute based mechanism for specifying test and test fixtures.
"- New Forms Interface that displays Tests and TestSuites in an Explorer like fashion. The interface allows you to run individual tests and/or suites from the forms interface.
"- Automatic construction of suites based on namespaces. Just provide an assembly and the test runner constructs a suite of all TestFixtures in the assembly.
"- Minimal amount of effort to upgrade due to inclusion of a backwards compatibility class called TestCase and the framework also looks for methods that begin with "test" regardless of case as it did in the past.
"- XML output from the console program."
[DOTNET-PRODUCTS]
Here. "Basically the class keeps track of the list of outstanding handles, and when it reaches a certain threshold it can force a GC. Basically the goal here is to do a cheap and easy extension to the GC to try and teach it about the relative expensive of unmanaged objects."
This is the way that GDI+ deals with unmanaged resource reclamation and can be used for your own non-memory resources.
Here. "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]
Here. "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/]
Here. "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/]
Here. "Guest columnist Jim Wilson shows you how the .NET Compact Framework and Smart Device Extensions enable you to develop rich Windows Forms applications for mobile devices."
