I was recently working on creating a custom configuration section (deriving from ConfigurationSection) to provide some configuration metadata to an app I’m working on. In creating a ConfigurationElement, I wanted to validate that one of the attributes of the element was a valid value for the application. While looking at the example here I noticed the use of various validation attributes applied to validate the format of configuration values. The CallbackValidatorAttribute and CallbackValidator seemed...

I've been trying to get NCover to run successfully on Vista Ultimate x64 on and off for the last month. We're still using one of the free versions of NCover available from here, so there is no built-in x64 support. I came across this post today that mentioned using corflags to set the 32BIT flag in both NCover and your testing application (the post is describes using NUnit, but this worked for me with MBUnit as well). Those changes got me past the Profiled process terminated. Profiler connection...

I've been playing with the National Digitial Forecast Database (NDFD) provided by the National Weather Service. You can retrieve a forecast via a SOAP web service by providing your latitiude and longitude and a few other details. The web service worked fine when I called it from Python, but I was getting an error when calling it from .NET (using the generated proxy classes in VS 2003 and VS 2005). It turns out that the service needs HTTP version 1.0, not 1.1 (the default in .NET). Unfortunately,...

We have a web service that is exposed on the internet but is only used by our client application. The client uses SSL to connect to the server and we are using WS-Security to provide authorization. Even so, I wanted to prevent someone from viewing the interface of the service by going to the default WSDL generated by ASP.Net (http://domain/Service.asmx... It turns out that this is actually pretty easy to do. I found documentation on it related to Visual Studio Team System Application Designer,...

Now that the release of VS2005 and the .NET Framework 2.0 is imminent, I'm able to justify more time at work for reviewing its impact. This list of breaking changes for 2.0 is definitely useful in that regard. I think one of the most important changes is the fact that unhandled exceptions will now always end a process (search for “Unhandled exceptions will always be fatal to a process”on this page). The 1.1 behavior was that unhandled exceptions on threads other than the main thread would...

Geoff Appleby posts a link to a Microsoft support page that can tell you what DLL came from what package. Very cool. Where'd that DLL come from