server application unavailable An error message detailing the cause of

July 3, 2008 – 12:00 pm

server application unavailable
An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur. how to resolve this??

Microsoft fixes Xbox 360 license transfer
Microsoft has finally fixed a long-standing irritation with the Xbox 360: the inability to transfer licenses for purchased games from one console to another. The new license transfer tool lets you consolidate all your download purchases to a specific Xbox 360, even if some were downloaded onto a con…
Tim Anderson

OpenSUSE Goes to 11
Easier installation, 3D desktop effects, digital music and video management and an up-to-date OpenOffice are among the enhancements in openSUSE 11.0, which became generally available this week. Designed for the novice as well the advanced, installation options include a choice of Gnome 2.22 or KDE 4 desktop environments and the ability to boot from disc rather than the hard drive. Available now for download , openSUSE 11.0 adds Compiz Fusion (version 0.7.4), a windowing system that resulted in the marriage of the Beryl composite window manager with the community-built Compiz Extras. The…

TestDriven.Net 2.10: Smart Build

There are a number of new features in TestDriven.Net 2.10 that I want to highlight (apart from the VS 2008 crash workaround). The one I’m going to focus on here is subtle, but significant I believe - especially for people working with large solutions.

Smart build is a new optimization that allows you to skip the build step before test execution when there are no source code changes. Anyone working on a solution with a large number of projects will know how time consuming the build can be before any tests can be executed. Somewhat surprisingly this remains true even when no actual source code edits have been made and nothing needs to be compiled. I’ve had reports of the build check taking as long as 45 seconds before any tests could be executed! (Thanks to Brian Genisio in particular for bringing this to my attention)

The new smart build feature overcomes this particular problem by monitoring your solution for source code edits and automatically skipping the build step if there is nothing new to compile. This can significantly improve performance when running multiple tests in the same solution. For example there is now no penalty for choosing to execute all tests in a fixture after an individual test starts to pass: a common usage pattern.

I will elaborate further on other new features in future posts. In the meantime you can read the latest release notes and download TestDriven.Net 2.10 from here. If you find any issues, please don’t hesitate to contact me.

You must be logged in to post a comment.