Last post Feb 21, 2007 04:03 PM by James Gao
Jan 27, 2006 07:08 PM|aircargo|LINK
Has anyone gotten the IEWebControls, particularly the TabStrip and MultiPage, to work in ASP.NET 2?
I can run them on my machine without a problem using a website in .NET 1.1 but on a newer .NET 2 site, the tab strip doesn't work at all.
Jan 31, 2006 08:44 AM|ranganh|LINK
You need to do some ground work for setting up IE Webcontrols to work in ASP.NET 2.0.
First of all you need to copy the webctrl_client folder into your application's folder. This will be available in the IIS root directory when you were working with 1.1 version.
First of all, in the web.config you need to specify the following within the <configuration> </configuration> section
<section name="MicrosoftWebControls" type="System.Configuration.NameValueSectionHandler,System,Version=126.96.36.199, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add key="CommonFiles" value="/yourwebsitename/webctrl_client/1_0/"/>
Then, you can normally reference the control in the Page directive and use the same.
Hope this helps.
Feb 01, 2006 02:55 PM|tmrhymer|LINK
Im relatively new to asp.net, and im not using iis, im just using the built in function of VS 2005 to view server pages. Any idea of where i should even start to get this to work?
All i get is this error:
Parser Error Message: Could not load file or assembly 'Microsoft.Web.UI.WebControls' or one of its dependencies. The system cannot find the file specified.
Then i get a bunch of log entries. Thanks
Feb 02, 2006 12:30 AM|ranganh|LINK
You need to download the Microsoft IE Webcontrols from here
Then you need to follow the instructions that come along with the download and create the 'Microsoft.Web.UI.WebControls' and also create the webctrl_client by following the instructions.
Finally, you need to copy the webctrl_client folder into your application's root folder and also add reference to the 'Microsoft.Web.UI.WebControls' DLL for your application.
This should solve your issue.
Write back if this doesnt help.
Feb 10, 2006 07:23 AM|Srikkanthan|LINK
Your post was very much useful. I was trying to use TabStrip. Wierdly for me after doing all the steps you had mentioned I didn't got the tabs at all. The controls in all tab pages were just appearing
in the same page without tabs. However my design window was showing tabs.
Then I tried differently. I downloaded IE Webcontrol once again and ran the build.bat with .NET 2.0 compiler. Then I copied the newly built Microsoft.Web.UI.WebControls dll to the bin folder. Even
now the tabs were not appearing.
Finally got bored of everything and tried to remove the web.config setting you had mentioned from my web.config. Voila! everything works - I got tabs. IE Webcontrol is Working !!! in ASP.NET 2.0.
Then I tried one more sample application. Strangely for me, if I give the web.config setting you have mentioned (MicrosoftWebControls) it is not working. If I don't
give it everthing seems to be fine. Probably the path must be the problem for me I guess.
Feb 13, 2006 04:08 PM|MarkP|LINK
How did you compile with .net 2.0? I'm using a dll compiled in 1.x. I don't know if there are differences in execution...
Can you give me further information?
Feb 14, 2006 09:36 AM|ranganh|LINK
You dont need to necessarily compile with ASP.NET 2.0. You can just use the old Microsoft.Web.UI.Webcontrols.DLL and specify the settings as mentioned in my original post.
They have been working fine for me (even intellisense pops up for them). The only issue is that PageView would be highlighted as an error. But you can just ignore it.
Feb 14, 2006 09:42 AM|ranganh|LINK
I havent had any issues in terms of using the Microsoft.Web.UI.Webcontrols.DLL build using .NET 1.x versions. Probably, you missed out the step that the webctrl_client also needs to be a part of the root directory
or you forgot to enter the Control declaration in the page directive as you would do with usercontrols.
BTW, if you are looking at a scenario where you would have postbacks when you switch between tabs, consider usign the MultiView - View controls. They simplify the way you work with Tabstrip and you dont have
to do FindControl, Explicit Event Declaration etc., which were some of the mundane tasks when using Tabstrip in 1.x versions.
I have a couple of articles which examine these and IE Webcontrols extensively. May be you want to check them.
ASP.NET 2.0 MultiView Control - No more TabStrip / Panel Show-Hide
A better way of working with IE Webcontrol - Part I
A better way of workign with IE Webcontrol - Part II
Feb 14, 2006 05:54 PM|tmrhymer|LINK
I've done all the installing of the webcontrols, and done the build.bat process and made 2 folders in the root of my applications (bin and webctrl_client) the application will come up in vs 2005 when i click view in browser (and when i test it on other servers
with the 2.0 framework) but whats weird is theyre not working right...i have tried this with the treeview and the tabstrip with the multipage and with the treeview all i get is the names of the treenodes that i made but they dont show up in an expandable form
its just the text in a flowlayout one after the other...any idea what im doing wrong?
Feb 15, 2006 12:42 AM|ranganh|LINK
Did you do the web.config setting I had mentioned in the original post?
Feb 15, 2006 03:47 AM|tmrhymer|LINK
im not even using a web.config file...its an introduction assignment web controls and we havent even covered the web.config file
Feb 15, 2006 06:55 AM|ranganh|LINK
Also, make sure the webctrl_client folder is there in your virtual directory root c:\inetpub\wwwroot.
Write back if none of the options mentioned in this post help.
Feb 15, 2006 02:18 PM|tmrhymer|LINK
yeah theyre still not functioning right - heres the actual code - Could it be a browser problem? Im using I.E. 6 - and i have a bin folder with the .dll file i need, and all the files im supposed to have for the webctrl_client folder are in place as well.
Feb 15, 2006 03:29 PM|joteke|LINK
what comes to TreeView, I believe that using ASP.NET 2.0's built-in TreeView overcomes IE WebControl TreeView in almost all possible ways (no external script files or behaviours, supports cross-browsers, also client-side populating, etc)
Here's a few resources related to v2 TreeView
Display Hierarchical data With TreeView in ASP.NET 2.0
Customizing TreeNodes with RenderPreText and RenderPostText
Context menus in ASP.NET v2 TreeView
Feb 16, 2006 12:32 AM|ranganh|LINK
If it is a TreeView requirement, if you are using ASP.NET 2.0, use the built-in TreeView control that is shipped.
I was guiding the original poster for implementing Tabstrip control. For treeview, you can use
<asp:TreeView id="TreeView1" runat="server"> which has a huge set of advantages over IE Webcontrols TreeView.
Feb 16, 2006 10:22 AM|cmm|LINK
I downloaded the set of controls and ran the "build.bat" file...which contains the following commands:
@if "%_echo%"=="" echo off
if not exist build mkdir build
csc.exe /out:build\Microsoft.Web.UI.WebControls.dll @IEWebControls.rsp
xcopy src\Runtime build\Runtime /E /Y /I /Q
Apparently the output directory was changed for some reason, as there is no longer a "webctrl_client" directory created at this point as part of the build process. If you follow the instructions other people provided but copy the "build\Runtime" contents
to a location under your project directory, and update the web.config appropriately so that the MicrosoftWebControls CommonFiles key points to that directory, the controls will display (at least it did for me).
Hope that helps,
Feb 16, 2006 12:08 PM|tmrhymer|LINK
Mar 06, 2006 03:27 AM|macsa|LINK
your post was very useful.
When I made the steps, my VS2005 made the following errors in the error list:
"Element 'PageView' is not a known element. This can occur if there is a compilation error in the Web site. "
The multipage element is ok, but the PageView is not.
What is the solution?
Mar 06, 2006 06:10 AM|ranganh|LINK
The PageView element shows error when building in Visual Studio, but it can actually be ignored.
Just ensure that there are no other build errors. When there are other build errors, I have found that this lists out also as an error.
But as such, this error can be ignored and I have found that it works fine, though it puts that squiggle red to show its an error in the IDE.
Dec 27, 2006 09:26 AM|Tristang|LINK
This is still not working for me. In my page, I have:
<%@ Register TagPrefix="hstab" Namespace="Microsoft.Web.UI.WebControls"
Assembly="Microsoft.Web.UI.WebControls, Version=188.8.131.52, Culture=neutral,
In my web.config file, I have:
Now, my error is still:
Could not load file or assembly 'Microsoft.Web.UI.WebControls, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The located assembly's manifest definition
does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I have the webctrl folder in both my web directory and root directory, and the dll taken care of. Also, I get the same error regardless of if I have the web.config code in there or not.
Jan 11, 2007 09:39 AM|ranganh|LINK
Can you list the steps you did before using the IE Webcontrols?
Secondly, are you trying to use IE Webcontrols for a Treeview?
Feb 21, 2007 04:03 PM|James Gao|LINK
I am working on the IEWebControls with ASP.NET 1.1. I copied the WebControls.dll in the Bin and added reference to the webpage. When the page is browsed, there is a parser error:" The located assembly's manifest definition with name 'Microsoft.Web.UI.WebControls'
does not match the assembly reference." The 'Microsoft.Web.UI.WebControls.DLL' is version220.127.116.11. The local reference is the same version. Do you have any suggension to fix this problam. Thanks!
Here is the simple code:
<form id=Form1 method=post runat="server"></form>
<%@ import namespace="Microsoft.Web.UI.WebControls" %>
<%@ Register TagPrefix="mymultipage" Namespace="Microsoft.Web.UI.WebControls" Assembly="Microsoft.Web.UI.WebControls, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <form id=Form1 method=post runat="server">
<body MS_POSITIONING="GridLayout"> </form> <form id=Form1 method=post runat="server"></form> <form id=Form1 method=post runat="server">
<form id="Form1" method="post" runat="server"> </form>
</form> <form id=Form1 method=post runat="server"></form> <form id=Form1 method=post runat="server">
<form id=Form1 runat="server" method="post"></form>