| 
|
| |
From: "Rick Bullotta"
Subject: Scripting Limitation with .Net Windows Form Control/IE?
Date: Wed, 5 Jun 2002 11:38:39 -0400
| |
It seems that the scripting engine is only capable of recognizing "top
level" methods and properties when a control written in .NET is embedded in
a web page using the OBJECT tag!!! Or, stated another way, it does not
appear possible to return references to objects from a .NET control to the
scripting environment. Applets were always capable of returning object
references to the scripting language, with no limits on the depth/hierarchy
of containment and such. This is a real showstopper/limitation with .NET
controls in terms of delivering a web-page scriptable rich UI. For our
needs, server-side generated HTML or DHTML won't do - we need a rich UI
component embedded in the page.
Is this a known limitation? Any workaround? Any plans to lift this in the
future? Beyond this and a few other idiosyncracies, .NET rocks!
Thx.
- Rick Bullotta
CTO
Lighthammer Software (www.lighthammer.com)
| | Post a follow up to this message... |
From: "Peter Torr \(MS\)"
Subject: Re: Scripting Limitation with .Net Windows Form Control/IE?
Date: Thu, 27 Jun 2002 10:45:32 -0700
| |
"Rick Bullotta" <NOSPAMRick.Bullotta> wrote in message
news:ejnzhiIGCHA.2096
> If I create my own class wrapping the Timer, similar to what you
> demonstrated in your attachment (another user class), it works fine.
>
> Is this related to the fact that the scripting environment doesn't
> inherently know any typelib information for the System.Windows.Forms.Timer
> class?
Hi,
Type libraries actually have nothing to do with a script's ability to call a
method. This is a common misconception ;-). The type library is like the
owner's manual on a toaster. Sure it's there if you want to read it, but
most people can work a toaster without looking at the manual.
Type libraries are for compilers, not engines.
Anyway, I would guess that the problem is probably that the Timer's members
have not been marked as "COM Visible", so they don't come across. Creating a
wrapper is probably your best bet.
Peter
--
Peter Torr -- ptorr
This must be the disclaimer I waited years to read:
http://www.microsoft.com/info/cpyright.htm
| | Post a follow up to this message... |
| |
|
