hello Everybody........I did everything as directed........and succeded to get treeview shape in design view, but when i tried it on IE, it dint show the results in tree view form but display all nodes as a line. Even the Browse window of MS Visual Studio .Net failed to display the results.........any help will be highly appreciated........thanks in advance

And you have webctrl_client folder that contains IE WebControls related stuff on the root folder of your site?

You have to copy the "webctrl_client" folder to the root directory. This contains the gif files and HTC for treeview

Thanks, yes I have already done it..................but tree does not appear in browser, but the all nodes being dispalyes as a one string, while in design window it is showing everything.....

yes i have already copied that folder....but it dint do any help..........

I am having the same issue. I've been able to deploy my web app to a few different machines successfully. And on this particular machine, it was actually working at one time. Not sure if this had anything to do with it but, the server was upgraded to use IE6.0 from IE5.0. I've installed the IE WebControls again but still no luck. Any suggestions would be appreciated. Thanks!

The attached excerpt from a companion text file of the VS.NET project found in

http://download.microsoft.com/download/2/9/0/290e3bc2-a238-447f-ad45-98e590b3048b/TreeViewControl.msi

contains instructions to solve the issue.

The link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/aspnet-usingtreeviewiewebcontrol.asp
goes to the MS article where the VS.NET project is referenced (at TreeViewControl.msi link).

hope it helps - it worked for me.

Ricardo Maciel

---------------------------

From: Anand Hegde
Date Posted: 7/1/2002 7:16:00 PM

Hi Jazz,

>i've just discovered too that version was now 226
>Could someone from Microsoft describe the procedure to upgrade ?
>Desinstalling older version first ? And what about Visual Studio
>operating mode and projects ?

Basically when you have both versions of IE WebControls in the GAC, pages
using either versions of the control should work fine.
If you are using the old verion (.116) of the IE WebControls in the dev box
if the production box has the latest version, then you must change
the declaration in ASPX pages from something like

<%@ Register TagPrefix="iewc" Namespace="Microsoft.Web.UI.WebControls"
Assembly="Microsoft.Web.UI.WebControls, Version=1.0.2.116, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" %>

To

<%@ Register TagPrefix="iewc" Namespace="Microsoft.Web.UI.WebControls"
Assembly="Microsoft.Web.UI.WebControls, Version=1.0.2.226, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" %>

On the other hand, if you would like to distribute the IE WebControls
along with your application you can that as well. In this case, you won't
have to bother if the IE WebControls are installed on the target machine or
not. Follow these steps to deploy IE WebControls along with your
Application.

1) Drop the Microsoft.Web.UI.WebControls.dll to the bin folder of your
application.
2) Declare your reference to the Webcontrols from the .aspx page as follows:

<%@ Register TagPrefix="iewc" Namespace="Microsoft.Web.UI.WebControls"
Assembly="Microsoft.Web.UI.WebControls" %>

instead of the following default declaration added by VS.NET:

<%@ Register TagPrefix="iewc" Namespace="Microsoft.Web.UI.WebControls"
Assembly="Microsoft.Web.UI.WebControls,
Version=1.0.2.116, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>

3) Now copy the webctrl_client folder (which is usually located at
inetpub\wwwroot) under your application folder.
4) Add the following entry to your Web.Config file:
<configsections>
<section name="MicrosoftWebControls"
type="System.Configuration.NameValueSectionHandler, System,
Version=1.0.3300.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" />
</configsections>
<microsoftwebcontrols>
<add key="CommonFiles" value="/YourApplicationName/webctrl_client/1_0/"
/>
</microsoftwebcontrols>

Now deploy your application to any server that has .NET FW! It should work
just fine!

Thanks,
Anand Hegde (MSFT)

This posting is provided "AS IS" with no warranties, and confers no rights.