if the user has allowed active/x controls you can use the object tag
instead, then in javascript check the readyState. as .net assemblies can
take a long time to load in IE, you will need to use a timer to check the
readyState. aslo you clients must have framework 1.1 already installed.
note: even though your assembly is installed, it permissions will still be
restricted to internet mode (no disk access, etc)
> Hey
> I need to assert from within a web page that an assembly was previously
[quoted text clipped - 13 lines]
> TIA
> Rea
Rea Peleg - 22 Jan 2004 17:18 GMT
Thanks Bruce
I do not need to load this assembley to ie, just check that it exists
on the web page's hosting machine.
Can I use the <object> tag to refer to this kind of an assembly ?
Also I do not know where it had been installed on that computer.
I need to get the path to it from the registry.
Thanks again
Rea
> if the user has allowed active/x controls you can use the object tag
> instead, then in javascript check the readyState. as .net assemblies can
[quoted text clipped - 22 lines]
> > TIA
> > Rea
bruce barker - 22 Jan 2004 20:59 GMT
with IE you can only load an assembly, you have no access to the registry or
disk. when you install your assembly, you can also install a simple active/x
control (marked safe for scripting), and use this as a flag the assembly has
been loaded.
otherwise you will have to write an unmanaged active/x control that the page
downloads which checks for the assembly (like when you go tot the microsoft
update page).
neither will work if the user turns off active/x support in IE.
-- bruce (sqlwork.com)
> Thanks Bruce
> I do not need to load this assembley to ie, just check that it exists
[quoted text clipped - 32 lines]
> > > TIA
> > > Rea