Web components

ASP .NET, HTML5, and Silverlight™/WPF-based products are now available on our Web site:

Separately, note that you may also use WPF components from other products in your Web applications as they can be used on the within XAML Browser Applications (XBAP), meaining that the controls could be hosted in browser that supports this type of applications (such as Internet Explorer®). Of course, in this case the end user must have .NET Framework installed on the client machine, and supplementary the client machine must trust the Web application that uses the controls in order to be able to run the components. See our Page sample application for any WPF control for an example of how to create a XAML Browser application with our control, and look at the Questions and Answers page in Documentation of the product for more details about how you could set a trust to your Web application on the client machine(s) in order to be able to run WPF controls there.

Our Windows® Forms controls can also be hosted in Internet Explorer® browser (and presented within HTML pages). For instructions on how to do so, please read this article. For licensing issues regarding Windows® Forms controls hosted in browser, we recommend you to read this article too. When hosting our Windows® Forms control in Internet Explorer® they will NOT run on the Web server, they will be downloaded and run in the context of the end user. This has several implications: if you need to populate controls with data from a server side database (and optionally send back changes), you will need to design and develop a Web service hosted within your Web site, and design a wrapper client component to provide the client communication services; end users may need to add your Web server as a trusted resource in their browser in order for the controls to be able to run with full trust on the client machine, or otherwise some of their functionality may be disabled; end user must use Internet Explorer® (or a browser that supports including Windows® client components within HTML pages), on a machine running a Windows® operating system; licensing DlhSoft controls needs to be done through .licenses (compiled licenses) files hosted on the Web server, after being manually compiled from our provided .lic (license) files, using LC.exe tool (available within the .NET Framework SDK). For a simple example showing some of the discussed steps, please check out our Web sample application from Gantt Chart Library for Windows® Forms.