this won't work too well.
first you .net windows control has to create the active/x control itself,
not the page. because it unmanaged code, the .net control will not be a
trusted control, so it will require the user to run the caspol.exe utility
to give your .net control enough permission.
-- bruce (sqlwork.com)
"Shahzad Godil" <sg****@sigmaflow.com> wrote in message
news:Oo*************@TK2MSFTNGP09.phx.gbl...
I have successfully placed a seperate .Net windows control on my aspx page
as well as one ActiveX Control (Visio control) on my aspx. But my orignal
design is that Visio activex will be placed in my windows control. And
then this windows control will be place in my aspx as "Client side" rich
user interface control.
It is giving blank page.
Thanks
Shahzad Godil