The Digital Tool Factory Blog

The Problem: You are trying to access a sql server database from your new ASP.net 4.0 site and get the error Login failed for user ‘IIS APPPOOLASP.NET v4.0’ error in IIS7 and Sql Server 2008 when logging in with the integrated security.

The Cause: The new default user for asp.net 4.0 does not have default login permissions.

The Solution: I was going to write this up, but GotToKnow.com does such an excellent job I thought I would just link to their post Login failed for user ‘IIS APPPOOLASP.NET v4.0’ error in IIS7.  It is an excellent site for that sort of information.

This post originally appeared on the Stronico blog – with the absorption of Stronico into Digital Tool Factory this post has been moved to the Digital Tool Factory blog

The Problem: You want to use the standard European Date Format, DD/MM/YYYY instead of the American Date Format MM/DD/YYYY.  You change the “Format” feature of the CalendarExtender to “DD/MM/YYYY”, but then the CompareValidator (which you’re using to ensure valid dates) calls out that you have entered an invalid date.

The Cause: The Compare Validator is expecting a different date format than it receives, and throws the error.   You will then notice that there is no “Format” attribute on the CompareValidator.

The Solution: Add the following line to the System.Web portion of your web.config file.

<globalization culture=”fr-FR”/>

That’s it!

This post originally appeared on the Stronico blog – with the absorption of Stronico into Digital Tool Factory this post has been moved to the Digital Tool Factory blog

The Problem: You are using an asp.net PlaceHolder control and populating it with a collection of custom web controls.  You then get “Null Reference Exception” and “Are you missing an assembly?” errors.  Your code looks much like this

foreach (string str in strStringList)
{
CustomWebBox cb=new CustomWebBox()[
cb.CustomTitle=str;
myPlaceHolder.Controls.Add(cb);
}

The Cause: The same ID’s are being used over and over agian in the page as the web control repeats.

The Solution: Instead of simply reinitializing the control the “new” keyword, load it manually using Page.LoadControl.  That keeps the id tags different and the error is avoided.  Your code would look something like this.

foreach (string str in strStringList)
{
CustomWebBox cb=(CustomWebBox)Page.LoadControl("~/CustomWebBox.ascx");
cb.CustomTitle=str;
myPlaceHolder.Controls.Add(cb);
}

That’s it!

This post originally appeared on the Stronico blog – with the absorption of Stronico into Digital Tool Factory this post has been moved to the Digital Tool Factory blog