Welcome to Imar.Spaanjaars.Com

You may be aware of the new ASP.NET 2.0 Profile feature that allows you to store and retrieve information for the currently logged on user. This Profile feature makes it extremely simple to store user specific information, like a user's address, phone number, or site preferences. (Note: if you're not familiar with ASP.NET 2.0 Profiles check out the section Storing User Profiles in the ASP.NET Quick starts).

But what if you want to access the Profiles data for another user? For example, what if you want to allow a site administrator to change the personal data of all users in your site? The trick to make this possible is to use the ProfileCommon class, which inherits from ProfileBase. This article shows you how you can use this class to access the Profile data for arbitrary users.

You may be aware of the new ASP.NET 2.0 Profile feature that allows you to store and retrieve information for the currently logged on user. This Profile feature makes it extremely simple to store user specific information, like a user's address, phone number, or site preferences. (Note: if you're not familiar with ASP.NET 2.0 Profiles check out the section Storing User Profiles in the ASP.NET Quick starts).

But what if you want to access the Profiles data for another user? For example, what if you want to allow a site administrator to change the personal data of all users in your site? The trick to make this possible is to use the ProfileCommon class, which inherits from ProfileBase. This article shows you how you can use this class to access the Profile data for arbitrary users.

Today I finished writing on my new book called ASP.NET 2.0 Instant Results. At 2:40 p.m. I sent in my last chapter and other related materials.

You may be aware of the new DefaultButton and DefaultFocus properties that a few ASP.NET 2.0 controls, including the HtmlForm have. These properties allow you to determine which button gets "clicked" when you hit enter on the page, and which form control gets the focus when the page loads. (If you're not familiar with them, check out this MSDN help file) But how do you use this feature in a page based on a Master Page?

Yoohoo, just before the weekend, Microsoft released the RTM (final) versions of Visual Studio 2005 and SQL Server 2005.

Some of you may have noticed that my web site was off-line for a long time. The site went down at the end of August and is only up again for a few days...

You may have the need to be able to get the URL to a page in a web application from the server code. This might be because the page could move or because the URL is dynamic in some way. While this would be a nice feature to have in .NET, there are reasons it is not. We'll discuss this and a simple solution for getting a page's URL in server-side code that saves us from hard coding it in the referencing pages.

Today I was experiencing unexpected 404 "The resource cannot be found" errors when working with Visual Web Developer 2005 Express Edition beta 2 in combination with the ASP.NET Development Server. No matter what I tried, and what file I tried to open, I kept getting the same error.

The new ASP.NET 2 data controls, like the SqlDataSource and the AccessDataSource grealty simplify data access in your Web Applications. However, they have one major drawback: they flood your pages with Sql statements. Not so with the ObjectDataSource, that enables you to bind to the results of a standard method in your Business Logic Layer. The ObjectDataSource can in turn be bound to a data aware control, like the new GridView or DetailsView controls

I recently downloaded and installed the Microsoft Enterprise Library and I must say it's an amazing piece of technology. I've been using several of the separate Application Blocks in the past and they have saved me a lot of development time.