Re: P

[Tony Capone]

Paul:

Yes. I had to modify the security policy on the client machine to get it to
work.

I started by creating a virtual directory named Temp on a server that had
.NET 2.0 on it, then created a Web page in the directory with the following
object tag:

<object id="oTreemapControl"
classid="http://localhost/Temp/TreemapControl.dll#Microsoft.Research.CommunityTechnologies.Treemap.TreemapControl"
height="300"
width="300">
</object>

If I tried to access this page from Internet Explorer on a client machine
that had .NET 2.0 on it, all I saw was the empty box that IE uses to
indicate "can't display control." (The client and server machines were one
and the same in my experiment, but I don't think that's relevant.)

I then followed these instructions for modifying the .NET 2.0 security
policy on the client machine, which I found at
http://www.dotnetbips.com/articles/displayarticle.aspx?id=118 :

"...You need to adjust .NET security policy on the client machine to trust
the web site sending the control. This can be done using Control Panel >
Administrative Tools > Microsoft .NET Framework Configuration option. Right
click on the Runtime Security Policy and the select Adjust security from the
shortcut menu. The adjust security wizard will start. Using the wizard
increase trust level for trusted sites zones to Full Trust. You also need to
go to Tools > Options menu of IE and add the site url under trusted web
sites zone."

After increasing the trust level for trusted sites to Full Trust in the
Configuration tool and adding the virtual directory to the list of trusted
sites in IE, the TreemapControl appeared in IE.

The need for full trust appears to be related to the fact that
TreemapControl.dll has a dependent assembly, namely TreemapGenerator.dll.
When I tried the same experiment with a control that had no dependent
assembly, full trust wasn't needed to get the control to appear.

So follow the instructions I've quoted above and see if that fixes your
problem. Be aware, though, that asking users of your site to make such
security policy changes is problematic, to say the least. If you find a way
to get the control to work without having to change the .NET 2.0 security
policy for trusted sites, let me know.

-- Tony Capone

"a" <a...@discussions.microsoft.com> wrote in message
news:CB64CA0B-103F-4DE7...@microsoft.com...
> Tony:
>
> Did you ever get the treemap control to work in an html object tag?
>
> Sure would be nice if I could get some help on this one.
>
> Paul

[a]

Tony:

Thanks for the info. I believe that I have the same set-up as you,
concerning security and permissions, but I'm in the process of reorganizing
my network, so I'll try again and see if I can get it to work since you have
verified that this set-up works for you.

If I find another way of making this work, you'll be the first to know...;-)

Paul
==============================================

"Tony Capone" wrote:

> Paul:
>
> Yes. I had to modify the security policy on the client machine to get it to
> work.
>
> I started by creating a virtual directory named Temp on a server that had

> ..NET 2.0 on it, then created a Web page in the directory with the following