if u make a windows form control in a (
.NET)control library, you can reference the control from a web page. theres a special syntax to do it with the
<object> tag.
you will however have to configure
.NET code access security on any machine thats supposed to access it, including adding your domain to the trusted sites zone on the client machine.
Code:
<object id="ControlID"
classid="http://localhost/Site/TestControl.dll#Namespace.ControlName"
height="50" width="100" VIEWASTEXT>
</object>
i have done it before. what we did was just convert the output type of the application project to dll, add a custom control that has a button to start the main form, recompile, and voila... a zero deployment solution.
at least that what microsoft says, but it never really reach deployment... because configuring the
.NET security ended up being no simpler than installing the app on the client machine.
the advantage with your case is that you are on a domain, and your admin can deploy the security policy, and add the domain to the trusted sites form his admin console to all machines