Thanks Bruce, but from what I've read the codebase attribute isn't used when
referencing a .NET assembly. I've tried modifying the object tag to point to
the dll as follows with no success:
<object id="objTest" classid="dlltest.dll#dlltest.dllTest"
codebase="c:\inetpub\wwwroot\dlltest\dlltest.dll" width="100" height="100"
viewastext></object>
I haven't gone so far as to put the dll into a cab yet... Do you think that
would make the difference?
"Bruce Barker" wrote:
codebase is used to specifiy the path. IE requires the code path match the
domain the same came from though. to host the object locally you can:
1) have the user run the page from the local disk.
2) build a cab file, mark as safe, and install the component locally.
-- bruce (sqlwork.com)
"Andrew Bagby" <An*********@discussions.microsoft.com> wrote in message
news:02**********************************@microsof t.com... Hi,
I have created a c# assembly that I want to use from IE. There is no UI,
just some methods that I want to call from client-side script.
I've referenced the assembly as follows:
<object id="objTest" classid="dlltest.dll#dlltest.dllTest" width="100"
height="100" viewastext></object>
and everything works fine as long as I open the web page from a web
server.
What I would *really* like to do, however, is open the page directly from
the file system - it's just a .htm page - with the ultimate goal of
enabling
the user to work with this page when not connected to the network.
I've tried hard-coding the local path to the dll in the classid attribute
with no success. Does anyone know if / how this can be done?
Thanks!