22 May 2009 09:48
It is official... Visual Studio 2010 and .NET Framework 4 "Beta 1" are available for download now!
Visual Studio 2010 and .NET Framework 4 focuses on the core pillars of developer experience, support for the latest platforms, targeted experiences for specific application types, and core architecture improvements.
Here are some highlights of what to expect:
- IntelliSense now parses 2 to 5 times faster, so there is virtually no processing delay, even with large script libraries.
- You can now publish to a server by using the Web Deployment Tool, FTP, folder copying, or FrontPage Server Extensions in one click. Visual Studio stores all the setting information, such as publish method, server information, and user credentials.
- The new Code Editor makes code easier to read. You can zoom in on text by pressing CTRL and scrolling with the mouse wheel. Also, when you click a symbol in Visual C# or Visual Basic, all instances of that symbol are automatically highlighted.
- In Visual Studio 2010, the Visual Basic and C# languages continue to evolve toward feature parity. This enables you to choose a language based on personal preferences because both languages are equally capable. This section lists some of the new features in C# and Visual Basic.
- Visual Studio 2010 includes F#, a new .NET Framework language that supports functional programming and traditional object-oriented and imperative (procedural) programming. F# combines the succinct, expressive, and compositional style of functional programming with the runtime, libraries, interoperability, and object model of .NET. In other words, you get the best of both paradigms.
Check out the “ASP.NET 4 and Visual Studio 2010 Web Development Beta 1 Overview” whitepaper for more information about the new features in this release.
14 May 2009 11:22
C# 4.0 introduces a new static type called dynamic. Dynamic lookup provides a means of bypassing C#’s static typing, in favor of dynamic typing. This means that you will be able to use a special syntax to code against arbitrary objects and avoid compile-time type checks. The type resolution will occur at runtime instead, dynamically.
dynamic d = GetDynamicObject(...);
The type dynamic can be thought of as a special version of the type object, which signals that the object can be used dynamically. It is easy to opt in or out of dynamic behavior: any object can be implicitly converted to dynamic, “suspending belief” until runtime. Conversely, there is an “assignment conversion” from dynamic to any other type, which allows implicit conversion in assignment-like constructs:
dynamic d = 7; // implicit conversion
int i = d; // assignment conversion
11 May 2009 13:22
Although only a small version number change (from 2.4.8), NUnit 2.5 represents a large amount of new functionality and has been nearly a year in the making.
Here are a few highlights of what to expect in the new release:
- A new syntax element, Matches(Constraint), allows use of custom constraints, predicates or lambda expressions in constraint expressions.
- The MessageMatch enum used with ExpectedExceptionAttribute has been extended with a new value StartsWith, indicating that the exception message must start with the string provided.
- TestCaseAttribute now supports a MessageMatch property.
- The File menu now allows selecting an alternate runtime, such as Mono, on a machine with multiple CLR implementations installed. This feature is still considered experimental and may change in the future.
- The combo box in the Project Editor allowing selection of a particular runtime type such as Mono for loading the test has been re-enabled.
- Provided a workaround to a Mono 2.4 bug in handling remote references to an interface, where the provider is running under MS .NET and the implementation is explicit.
- The Console Runner display now shows the settings for ProcessModel, DomainUsage and RuntimeFramework actually provided, before resolution of any defaults.
- Removed references in the docs to pages that no longer exist.
This new release also now includes pNUnit, an extended NUnit 'runner' for distributed parallel tests. The pNUnit program was developed at Codice Software for use in testing the Plastic SCM and has been contributed to NUnit. For more info about using pNUnit see the pNUnit site.
In addition Jamie Cansdale has released a new version of TestDriven.NET, a tool that allows developers to run their NUnit (and other frameworks) Tests inside Visual Studio.
Download nUnit 2.5 from the official website.
Other .NET Unit Test tools include: MBunit, CSUnit, xUnit.Net, NBehave and Gallio - an open, extensible, and neutral test runner designed to support all .NET test tools.