This site uses cookies. By continuing you accept the use of cookies.I Accept

During this week, ten years ago, we began developing our first solution using Microsoft Visual Studio .Net and Microsoft .Net Framework.

When starting our company Mindbite back in 2000, ASP development (Active Server Pages) using Visual InterDev was really cool, so that became our area of expertise. In 2002 Microsoft released .Net Framework with Visual Studio .Net and I can remember us giving that a try. The tools and languages were completely different than ASP and the learning threshold was a lot higher, so it wasn’t until the summer a year later that we decided to leave ASP in favor of .Net Framework.

The easiest route from ASP till .Net Framework was to choose the language Visual Basic .Net, so that’s what we did. I can also remember us bringing in a lot of crappy thinking from ASP to .Net Framework. Looking back at our earliest .Net solutions feels like a train wreck.

Fortunately, we learned quite quick and very soon we had left ASP development behind us, and we haven’t looked back since. During the years we have delivered hundreds and hundreds of solutions developed with Microsoft .Net.

In 2010 we decided to leave the programming language Visual Basic .Net in favor of C# (which is also a .Net programming language). This was one of our biggest, yet most important, decisions in our history.

During our ten years with Microsoft .Net we’ve worked hard to get as much as possible out of it. That’s why we partnered up early with Microsoft. We’ve gone through several partner stages, from MAPS to Empower Program and in 2009 we became a Microsoft Silver Partner. Two years later we reached Gold level Partnership. This is a level that we work hard on to keep.

Recently we also successfully Gold Certified our flagship product SiteFactory CMS, which is built on Microsoft .Net, for Windows Server 2012.

Over these ten years we’ve adopted every release of Visual Studio, Visual Source Safe and Team Foundation Server. These great tools has empowered us to deliver great solutions for our customers. We’ve worked with six different major versions of Visual Studio, starting with Visual Studio .Net (2002) and we’re currently using Visual Studio 2012. Very soon Microsoft will release Visual Studio 2013 which we’re very excited about.

So I hope this story will continue for at least another ten years.

For the moment I’m working on a project with the Swedish Police, building an Adapter for an existing data application. The adapter that I’m developing communicates with a SOAP Web Service hosted on Apache. The data that is received is then transported back to the existing application. Quite the simple task, if it wasn’t for a very strange behavior in Microsoft .Net.

The SOAP Web Service requires authentication and if authentication fails it responds with a 401 error.

So I wrote this code and thought it should work.


As soon as we called a method in the Web Service, it responded with the 401 error. So I set the property PreAuthenticate to true.


That didn’t work either, so my first thought was that something must be wrong with the Web Service, or that I had been given the wrong credentials.

After a few hours of searching various forums I finally found the solution. Apparently the authentication is not added to the Http Header (as it should have been). So the solution was to subclass the Web Service class and implement some additions.


With this code in place, it’s now possible to add the authentication header to the Web Service.



Finally the call is authenticated and I received data from the Web Service.