Russell Pooley's .NET Blog

As the chief developer of the mixer for the Oomix site I feel I need to tell the world.

It's been ages since I posted about the development of our collaborative music creation and sales website / application but we're now on the run-up to launch. The site's got numerous ways for developers of all sorts to connect in to it so I'd like to open up a forum to see if anyone has any ideas or would like to build a plugin.

This is a problem I have been trying to resolve for over three weeks now with no success. I shall try to explain the problem as clearly as I can as it can get very confusing.

I have a Visual Studio 2005 .NET 2.0 Web Service Project which has a single web service class called HelloService. This service has the following content:

I have spent probably 4 hours of my life trying to figure out why I keep getting a bizarre error message when I try to browse to a .NET 2.0 Framework Web Service, so after figuring it out I thought I would post this so I never forget it. The solution to the problem was so simple but it took a long time to find it. So what happened:

I have been working on a project for over 6 months and we are about to release it to the world, you may ask what has this got to do with weblogs.asp.net and .NET well read the introduction below and it will all make sense.

Previously in the past I have found myself constrained to keeping certain posts to myself due to company policies and so forth. But now is very different, I have just started my own limited company providing development and consultancy services.

Having just read Kenny Kerr's blog on the Attributes Do Nothing post (http://weblogs.asp.net/kennykerr/archive/2006/06/02/Attributes-That-Do-Nothing.aspx) I have decided to partially repost the bit about the DebuggerDisplay attribute so I don't forget it.