This project is read-only.


MultiHandleSliderExtender - Breaks Design View


First time submitting an error report here so be gentle ;)

I've been using an old version of the ajaxcontroltoolkit with Visual Studio 12 over several years for a project at work and now have a need to use the multihandlesliderextender for a new part of the project. I dropped one into the page and set it up and eventually got it working in the but it gave the "could not be set on property" error which has been reported several times in the past and supposedly fixed in the new versions.

Due to this i decided to bite the bullet and upgrade, so have spent the whole day installing Visual Studio 2015 (alongside 2012) then creating a clean new website for testing, then installed the newest version of the ajaxcontroltoolkit into the new site via nuget.

Dropped the control into a page and it's still producing the same error (!) - have attached a screen shot of the error in the designer and the control working in the page, code is as follows :

<%@ Page Language="VB" AutoEventWireup="false" CodeFile="testpage2.aspx.vb" Inherits="testpage2" %>
<!DOCTYPE html>

<html xmlns="">
<head runat="server"> <title></title> </head> <body>
<form id="form1" runat="server"> <div> <asp:ScriptManager ID="ScriptManager1" runat="server"> </asp:ScriptManager> <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox><br /> <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox><br /> <asp:TextBox ID="TextBox3" runat="server"></asp:TextBox><br /> <ajaxToolkit:MultiHandleSliderExtender ID="TextBox1_MultiHandleSliderExtender" runat="server" Enabled="True" HandleAnimationDuration="0.1" Maximum="100" Minimum="0" TargetControlID="TextBox1"> <MultiHandleSliderTargets> <ajaxToolkit:MultiHandleSliderTarget ControlID="TextBox2" /> <ajaxToolkit:MultiHandleSliderTarget ControlID="TextBox3" /> </MultiHandleSliderTargets> </ajaxToolkit:MultiHandleSliderExtender> </div> </form> </body>

Cheers, Lee

file attachments

Closed Mar 10, 2016 at 5:11 PM by MikhailTymchukDX
This issue was moved to GitHub as a part of the AJAX Control Toolkit migration process.
Please follow this link to continue working on the issue:


MikhailTymchukDX wrote Feb 19, 2016 at 10:36 AM

The issue is fixed and the fix will be included in one of our future releases.