| |
Having a problem? Wish there was a feature for what you want to do? Check here first.
What are the system requirements to run EasyListBox?
I don't have my registered download link anymore, but I want the new version! What do I do?
I've installed EasyListBox 4.0 on ASP.NET 1.x and the system says it's not a valid DLL or assembly. What's wrong?
I've installed EasyListBox 4.0 and I'm getting the following error:
Error in OnPreRender:
System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
When I put EasyListBox in a page and click on it, I just get a Javascript error. What's wrong?
What if I don't want to keep the ELB script files in my website root?
Can I use EasyListBox in a WinForms application?
How do I get the selected value of an EasyListBox instance if I'm not using ViewState?
I'm using EasyListBox for swapper lists; why can't I find the Items collection on postback?
I have some related lists in a User Control/Master Page/other naming container, and they're throwing errors. What's going on?
What are the system requirements to run EasyListBox?
You must have a web server with ASP.NET installed. If you do not have ASP.NET, you can
download it here.
Back to top
I don't have my registered download link anymore, but I want the new version! What do I do?
You can request your download link with
this form
and it will be mailed to you right away.
Back to top
I've installed EasyListBox 4.0 on ASP.NET 1.x and the system says it's not a valid DLL or assembly. What's wrong?
EasyListBox 4 is compiled against ASP.NET 2.0, and will not be recognized by earlier versions. You must either (a) install ASP.NET 2.0 (and the AJAX Extensions), or (b) use EasyListBox 3.5, which is
available for trial on the Download page and is still supported through JavaScript file updates. Be sure to specify version 3.5 in your comments at purchase time, or notify ELB support after purchase to obtain the correct version.
Back to top
I've installed EasyListBox 4.0 and I'm getting the following error:
Error in OnPreRender:
System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
EasyListBox 4 requires that you install the ASP.NET AJAX Extensions. You can install the 1.0 version of the extensions, or simply install ASP.NET 3.5 (on top of the 2.0 framework).
If you still receive this error after installing 3.5, make sure that your web.config contains the proper assembly redirects. They should be located in the "runtime" section of the web.config file, and should look like this:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
Feel free to download this sample web.config file for ASP.NET 3.5 if you still have trouble.
If you are not able (or allowed) to install new framework components for some reason, you can either (a) add the DLLs and customize the web.config yourself, or (b)
try the previous version of EasyListBox (3.5), which does not require ASP.NET AJAX (or 2.0) and is still supported through JavaScript file updates.
Back to top
When I put EasyListBox in a page and click on it, I just get a Javascript error. What's wrong?
Did you forget to put EasyListBox between a <form runat="server"> and </form> tag? ASP.NET server controls must be
contained within a server-side form like this in order to operate.
Another possibility is that the ELBScript.js file is not where ELB expects it to be. Check the script tag in View Source to see if the src attribute is pointing where you expect.
Back to top
What if I don't want to keep the ELB script files in my website root?
Versions 2.4 and up allow you to set a key called "ELBScriptPath" in the web.config file. The path you specify here is relative to
the website root (i.e. "/scripts/EasyListBox") so all sub-applications can use the same script path.
Back to top
Can I use EasyListBox in a WinForms application?
Unfortunately, no. EasyListBox is an ASP.NET server control, which means it is executed on the web server and rendered to the
browser as HTML.
Back to top
How do I get the (server-side) selected value of an EasyListBox instance if I'm not using ViewState?
As you might expect, it's easy. Just like any other form control, you can call
Request.Form("myListBox")
and you'll have the selected value, just as you would for an old-style listbox.
However, assuming you haven't set the MaintainState property to False, you can also call myListBox.SelectedValue
-- even without ViewState!
Back to top
I'm using EasyListBox for swapper lists; why can't I find the Items collection on postback?
Swapper lists are very different from other kinds of listboxes. When working with these lists, the
entire set of values -- as well as their order -- usually needs to be retrieved. With this in mind, EasyListBox provides the
AllValues() method, which returns an array of all values present in the list (in the user-defined order) on postback.
Back to top
I have some related lists in a User Control/Master Page/other naming container, and they're throwing errors. What's going on?
If you've specified the ChildList or ParentList with hard-coded value, chances are it's not the right one. When rendering control IDs in the browser, ASP.NET appends the ID of any significant parent controls... so instead
of "myDropDown", the ID is rendered as "myUserControl_myDropDown", and so on; this can be mitigated by using the list's ClientID property, like this:
myParentList.ChildList = myChildList.ClientID
myChildList.ParentList = myParentList.ClientID
Back to top
|
