Active Directory and changing passwords through ASP.NET

When using an ASP.NET-application to change have a user change his/her password, Password Complexity can act up.
Or better said… ASP.NET apparently doesn’t look at the settings set in Active Directory :-/

While looking for a solution, I ran into this (series of) article(s)….

My solution: write a custom MembershipProvider, derived from the ActiveDirectoryMembershipProvider.
That way I don’t have to actually plug things in the standard-controls, just provide a custom membership-provider…

UpdatePanel-updates and losing focus

I’m currently fiddling around a bit with UpdatePanels (again), and noticed that focus is lost when the UpdatePanel is updated.
Luckily, I found the following site that solved my problem.

Visual Studio 2010 and SharePoint 2010

While attempting to find a fix for the migration-thing, I ran into a problem while connecting to the SharePoint site.

First I got an IOFileNotFoundException, stating that the Web application was not found…
So.. Visual Studio 2010 is set to x86 by default… and SharePoint 2010 is a x64-application. Got that one fixed thanks to this webpage.

Next, I got an error saying .NET 4 cannot be used for SharePoint…
So I had to change the target framework to .NET 3.5…
Thanks to this page for kicking my brain back into gear…

Oh.. and VS2010 needs to be run as an administrator…

SharePoint 2010, migrating from SharePoint 2007 and Language Packs

So… apparently SharePoint 2010 has a new ‘feature’… Instead of the English names in URLs, localized names are used.

For example, the default-page in 2007 for a Dutch-site has as URL: /Pages/default.aspx

For 2010, the URL will be: /Paginas/default.aspx

Where the fun comes in? Migrating from a Dutch 2007-site to 2010… And getting navigation-errors… and not having all your pages and such…

What got me on track of this was this post from Appie, developer at TamTam.

Now all I have to do.. is find a better solution…

RunWithElevatedPrivileges and security-validation errors

I’ve been looking at some code that was written for us which works on one server, but fails on another.

Has to do with the page not running in the proper context at the time some actions are done.

Luckily, I found a very good solution right here.

LINQ is really REALLY nice :)

Ran into a little problem having to do with setting some things on a SPGridView-column after databind.

Luckily I ran into this post, which helped me get a shorter version for the same purpose:

DataControlFieldCell dcfcDescription = e.Row.Cells.OfType<DataControlFieldCell>().Where(c => c.ContainingField.SortExpression == "Description").Select(c => c).SingleOrDefault();
if (dcfcDescription != null)
{
    Label desc = (Label)dcfcDescription.Controls[0];
    dcfcDescription.ToolTip = desc.Text;

    if (desc != null && desc.Text.Length > 100)
    { desc.Text = desc.Text.Substring(0, 50) + " ..."; }
}

I love being able to use LINQ on objects that were not originally designed for that

Weeknumbers and SQL Server

I was investigating a problem today, where the first week of the year in The Netherlands was show by one of our applications as week 2.

Fortunately, I came across this link, which gave me a solution, and the knowledge that SQL Server 2008 has a native function for this.