Software Blog

In case you are using some of the Custom Index Providers I blogged about previously, you may encounter some errors when upgrading to the new Sitefinity 3.6 SP1 that was released this week.

The problem is that the IIndexerInfo interface how requires a new method, ResolveIndexPath(). Since the Sitefinity team is still catching up on documentation, I didn't know what exactly this is used for. Fortunately, with the use of Reflector, it turns out that this simply returns the Path property.

public string  ResolveIndexPath()
{
     return  Path;
}

Actually, this method is also supposed to take into account culture information, modifying ...

This post is for anyone who is encountering the following errors in their asp.net applications:

• The server tag 'asp:ScriptManager' is ambiguous. Please modify the associated registration that is causing ambiguity and pick a new tag prefix.
• The base class includes the field 'ScriptManager1', but its type (System.Web.UI.ScriptManager) is not compatible with the type of control (System.Web.UI.ScriptManager).

There are many instances where you might exprience this problem. For me, the situation was that we had a virtual directory running asp.net 2.0 with AJAX extensions, while the root site is running asp.net 3.5. The subdirectory was attempting to reference the old 1.0.61025.0 ...

While developing an online form, I came upon the need to insert two copies the results to a database, one for each of two options selected on the form. The only thing different between these entries would be this option, and of course, the autogenerated ID for the row's primary key.

While I could simply call the Insert function of the TableAdapter twice, this method requires that each field be explicitly submitted as a parameter, and since the data is coming from textboxes, and there are about a dozen boxes on the page, that's a whole lot of textbox.Text.Trim() arguments!...