[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.aspnet.webcontrols

Installing and running Internet Explorer WebControls

Mike Anderson

1/3/2003 9:24:00 PM

I must say I am a bit confused about the Internet Explorer
WebControls. Specifically how to get them installed in a development
environment. Visiting this group I don't see much in the way of
complaining about how these controls don't work or how difficult it
was to install. So a lot of you must be using them.

I get the impression that if my desktop box were running IIS, ASP.NET,
and the .NET Development IDE I will be able to install and develop
with them. Keep in mind that I also run Notes (stay away if you can),
Office, IE, SQL tools,...... ad infinitum. That creates a lot of
processes running on my box. It is no slouch but enough is enough.
That is why I have separate development web and SQL servers to access
from my desktop box.

At any rate my problem leaves me with two theories. The first of
which is that I am being very dim and can't see something very big
right in front of me. Or. Or all of you are running the IIS, ASP.NET
and the IDE on the same box for development and deploy later. Still I
seem to believe there is a way to do what I want within my
environment. Here are the details.

WEB Server: Windows 2000 Server running IIS, ASP.NET
Desktop: Windows XP Pro with VS.NET

Any help or comments from those in the same pickle are appreciated.

Mike
2 Answers

Jesse Ezell

1/4/2003 9:39:00 PM

0

You need to install the IE WebControls on every box that
you are using them (dev and server machines). If the
install doesn't automatically add IE WebControls toolbar
to visual studio, you can right click the toolbar and
select Add Tab, and then right click again and customize
and add a reference to the IE WebControls DLL. It will
then add the controls to the toolbar and you can drag and
drop them as needed.

The reason you can't just install on one machine is that
they are not just a DLL which you can copy into a
directory. The install also creates a directory that
contains js files and image files that are used by the
application. If your web application is in its own domain
on the server, you may also need to add a virtual
directory at the root which corresponds to the directory
that the web control client files are location (I believe
it is something like webctrl_client, but a simple
explorer browse would get you the exact name if that
isn't it).

Additionally, everyone is running IIS, ASP.NET, VS.NET on
the same box and deploying later as you assume. VS.NET
requires IIS and ASP.NET to be installed.

--Jesse

Mike Anderson

1/5/2003 1:57:00 PM

0

Thanks Jesse. It is as I figured. I was hoping I did not have to
install IIS on my development box just to support controls that should
have been shipped with the product in the first place. To date I have
been doing fine creating ASP.NET apps without having to install IIS
and ASP.NET locally using the web server instead. Looks like I may
have to bite the bullet.

Mike

On Sat, 4 Jan 2003 12:39:14 -0800, "Jesse Ezell"
<jesse@activehead.com> wrote:

>You need to install the IE WebControls on every box that
>you are using them (dev and server machines). If the
>install doesn't automatically add IE WebControls toolbar
>to visual studio, you can right click the toolbar and
>select Add Tab, and then right click again and customize
>and add a reference to the IE WebControls DLL. It will
>then add the controls to the toolbar and you can drag and
>drop them as needed.
>
>The reason you can't just install on one machine is that
>they are not just a DLL which you can copy into a
>directory. The install also creates a directory that
>contains js files and image files that are used by the
>application. If your web application is in its own domain
>on the server, you may also need to add a virtual
>directory at the root which corresponds to the directory
>that the web control client files are location (I believe
>it is something like webctrl_client, but a simple
>explorer browse would get you the exact name if that
>isn't it).
>
>Additionally, everyone is running IIS, ASP.NET, VS.NET on
>the same box and deploying later as you assume. VS.NET
>requires IIS and ASP.NET to be installed.
>
>--Jesse