Welcome to Imar.Spaanjaars.Com

If you're working with files (creating, copying, deleting etc) in your ASP applications, you have probably configured the permissions for the IUSR_MachineName account so it is allowed to write to the folder where your files reside. However, if you want to write to a folder on another machine you'll run into problems. This FAQ describes a few common scenarios to overcome these problems.

Let's face it. We're not living in a perfect world. I am not a perfect programmer, and the same probably applies to you (otherwise you would be stinkin' rich, laying on the beach somewhere drinking a Bacardi and Coke, instead of reading this article).

Because we aren't perfect, we know we are going to run into errors in the applications we write sooner or later. This article will explain how you can catch these errors in your ASP.NET applications and log them to the Windows Event log, so it's easy to review them later. The article focuses on ASP.NET, but the principle applies to other .NET applications as well.

I would like to welcome a new author for my Web site. Peter Lanoie has offered to contribute articles and FAQs to my Web site whenever he finds something interesting to write about.

You may have the need to be able to access the same instance of a class variable from multiple object instances of that class. This is known as a "class" scope variable. Here I'll explain how it's done.

With the .NET Framework 1.0 it was already possible to enable Visual Styles for your .NET Windows Forms so the application took on that shinny new Windows XP look. Enabling Visual Styles was quite a hassle, though. You had to create a manifest file that contained a lot of gobbledygook and it wasn't as straight-forward as you'd hope.
With the .NET Framework 1.1, however, things have become much easier.

How do I set up my ASP.NET Web application to notify me with the details of an error when one occurs on my Web site? And how do I give the user a friendly message telling them an error has occurred?

When you're working with files, it is sometimes necessary to write to temporary files. Of course you could drop those files in the application's folder, but it's good practice to save those files in the user's Temp folder instead. This snippet will return the full path to the user's temp folder, e.g. C:\Documents and Settings\Imar\Local Settings\Temp\, so you know where to save your temporary files.
For this code to work, you'll need to import the System.IO namespace.

When you're working with files, it is sometimes necessary to write to temporary files. Of course you could drop those files in the application's folder, but it's good practice to save those files in the user's Temp folder instead. This snippet will return the full path to the user's temp folder, e.g. D:\Documents and Settings\Imar\Local Settings\Temp\, so you know where to save your temporary files.
For this code to work, you'll need to import the System.IO namespace.

Regular visitors may have noticed a new feature on the details page for articles, news and other categories of the site. The Details section of the page now has a Listened To item.

When you are trying to debug your ASP or ASP.NET pages, it's important to get detailed information about your errors. Knowing the cause of the error is often the biggest part of solving the problem.
By default, Internet Explorer will hide most of the raw error message from you, and instead will give you a “Friendly” HTTP error message. This FAQ will show you how to disable this feature so you can see the original error that the ASP run-time threw at you. This will help tremendously in debugging your ASP applications.