I have come across a situation recently where I am coding in DEBUG mode and things are working perfectly. When I go and try to get things running in RELEASE mode, I get an error.
Recently, a co-worker ran into a problem I had run into many times in the past. After taking a few minutes to figure things out I was able to help him. It surprised me that I hadn’t blogged about this before. So here we go…
Does this look familiar to you?
The type or namespace 'SomeNamespace' could not be found (are you missing a using directive or an assembly reference?)
I bet you’ve probably seen it before. It happens when you forget to include a reference in your project or if you don’t use a ‘using’ directive to include the assembly.
I’m working on an MVC Website. In development in Visual Studio, things are working perfectly. My app needs to run in IIS. Easy enough, right? Just set it up in IIS and you’re off and running.
Recently though, my IIS instance of the site stopped working. What?! I began to get the following error:
HTTP Error 503. The service is unavailable.
Wha wha wha?! I checked IIS and it’s running properly. What the heck? SQL Server is okay. The thing works perfectly in Visual Studio. ARG.
Recently, I’ve been working on a project that relies on a backend business object layer. The business object (BO) layer, requires authentication in order to be used. For most of the systems, this is okay, but my project is to be used by end users. We don’t need to authenticate the users… we need to authenticate the system.
This is easy enough using the CustomPrincipal object in Rocky Lhotka’s CSLA framework (which is also being used). We simply create the CustomPrincipal and add that to the ApplicationContext.
There’s a commonly known piece of information that pretty much everyone knows… use it or lose it. It applies to foreign languages, computer language, cooking techniques… all sorts of things.
Things like the code to unlock restrictions on an iPhone!