MRU support, including both in-menu and sub-menu support.
A much more robust set of validation components modeled along the lines of the ASP.NET validation components, including required, regex, range and comparison validators.
FileDocument component for document/dirty bit handling.
Wizard support, including changing page groups on the fly!
Custom state treeview so that you can set and show all three checkbox states.
A class to expose the WinForms HandleCollector so that you can put your own custom resources into it.
A Screen Saver class.
A bunch of file utility classes, including retrieving mapped drives, retrieving shares and path resolution.
A cursor changer class that works with the using block.
A WebCommandLineHelper class to parse command line arguments from the URL used to launch href-exes.
Update to the FileNameDialog to include newish flags.
Here. From Bernard Vander Beken: Highlights of the updated unit testing framework for .NET:
- Attribute based mechanism for identifying test fixtures and test methods.
- Automatic creation of test suites.
- Improved GUI runner allowing dynamic reloading of test assemblies.
- The Console runner supports XML output.
- Mostly backward compatible with NUnit 1.0.
Here. From Jesse Ezell: If the .NET show wasn't enough for you, Microsoft is producing another show. Supposed to be slightly irreverant and not for the faint of heart.
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. "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. "The approach that we take with treecc is similar to that used by yacc. A simple rule-based language is devised that is used to describe the intended behaviour declaratively. Embedded code is used to provide the specific implementation details. A translator then converts the input into source code that can be compiled in the usual fashion."
“The Typed DataSet that Microsoft generates from Visual Studio.NET (or from the XSD.exe tool), does not support derivation directly. In order to allow us to derive from Typed DataSets, Chris Sells and I created this tool that fixes the couple of issues with inheriting from Typed DataSets.”
