G
Guest
As a lot of us might now, the input file (aka browse button) in html does not
allow for multiple file selection or for filtering file types. The File Open
dialog used in WinForms allow these things and more.
I developed a windows user control in VB.NET with a button and File Open
Dialog, which allows multiple file selection. I registered the assembly with
regasm.exe and call the object from the html page with the object tag:
<OBJECT id="MyWinControl1" codeBase="Cab2.cab"
type="application/x-oleobject" height="280" width="480"
classid="CLSID:28766FA7-91E9-3A61-BC65-1981B6E6E840"
VIEWASTEXT></object>
When i run the page locally it works because the object is registered, but
when the page is ran from a computer that does not have the assembly
registered i get the little x icon in the browser. I thought the codeBase
will execute and prompt the user if they wanted to install the software, but
it doesn't.
Am I doing something wrong? Should the codebase reference the dll directly?
Should i use a different approach? Is this possible? If it was possible and
someone would help me make this work, would the user need to have the
framework installed in their machine?
allow for multiple file selection or for filtering file types. The File Open
dialog used in WinForms allow these things and more.
I developed a windows user control in VB.NET with a button and File Open
Dialog, which allows multiple file selection. I registered the assembly with
regasm.exe and call the object from the html page with the object tag:
<OBJECT id="MyWinControl1" codeBase="Cab2.cab"
type="application/x-oleobject" height="280" width="480"
classid="CLSID:28766FA7-91E9-3A61-BC65-1981B6E6E840"
VIEWASTEXT></object>
When i run the page locally it works because the object is registered, but
when the page is ran from a computer that does not have the assembly
registered i get the little x icon in the browser. I thought the codeBase
will execute and prompt the user if they wanted to install the software, but
it doesn't.
Am I doing something wrong? Should the codebase reference the dll directly?
Should i use a different approach? Is this possible? If it was possible and
someone would help me make this work, would the user need to have the
framework installed in their machine?