AjaxControlToolkit DropDownExtender flicker

by neo_savvy 6/4/2009 8:51:00 AM

To prevent flickering on client load, set the "display: none" on the panel set as the DropDownControlID on the DropDownExtender.

<ajaxToolkit:DropDownExtender runat="server" ID="dropDownExtender" TargetControlID="dropDownLabel" DropDownControlID="dropDownPanel" />
<asp:Label ID="dropDownLabel" runat="server" Text="Label" Width="109"><a>{Drop Down Label goes here}</a></asp:Label>
<asp:Panel ID="dropDownPanel" runat="server" CssClass="modalDropdown" style="display: none">
   <ul>
       <li>DropDownListItem #1</li>
       <li>DropDownListItem #2</li>
   </ul>
</asp:Panel>

Be the first to rate this post

Currently 0/5 Stars.
1
2
3
4
5

Tags:

HTML | ASP.net

HttpException in page with ScriptManager using Virtual Path Provider

by neo_savvy 5/29/2009 4:21:00 PM

This bug is related to System.Web.Extensions.dll.

Sharepoint uses a Virtual Provider to retrieve content from the database or the file system depending on the type of page (customized or common) and forwards the retrieved page to the asp.net runtime. When using a ScriptManager (with page methods enabled) on a page that runs in Sharepoint, the ScriptManager maps virtual directories to the file system - and tries to establish a CacheDependency (which uses a FileChangesMonitor to monitor) that specific path/directory. This is what causes the HttpException reported below:

Exception error message when you use a virtual path provider to serve a Web page that has a ScriptManager control: "Directory '<file directory>' does not exist. Failed to start monitoring file changes."

You may refer to the Microsoft Knowledge Base article KB957661 for more details.

There's a hotfix available to resolve this issue. You can obtain it here.

Be the first to rate this post

Currently 0/5 Stars.
1
2
3
4
5

Tags:

ASP.net

Membership.CreateUser: "The E-mail supplied is invalid"

by neo_savvy 4/5/2008 5:55:00 PM

Are you getting this exception with this code?

MembershipUser user = Membership.CreateUser([username], [password]);

That exception message is a very poor description of the actual problem. You definitely have set requiresUniqueEmail = "true" in your web.config. The issue at hand is the method you have chosen. If you have requiresUniqueEmail set to true, then you must supply a unique email when you create a user. So you should use the appropriate overloaded method:

MembershipUser user = Membership.CreateUser([username], [password], [email]);

That should solve the problem, hopefully .