Welcome Guest! To enable all features, please Login or Register.

Notification

Icon
Error

Options
View
Last Go to last post Unread Go to first unread post
#1 Posted : Friday, October 24, 2008 5:31:07 AM(UTC)

GregR  
GregR

Groups: Registered, Tech Support, Administrators
Posts: 769


This ASP.NET C# 2.0 demo uses the LEADTOOLS v16.5 .NET interface to print images stored on the server to a printer installed on the client's local machine.  This process involves making a .NET UserControl that gets downloaded to the client which downloads an image from a URL to a temporary location, prints the image locally, and then cleans up the temporary file(s).  Included in the ZIP file is a Word document explaining how to set up the project.
File Attachment(s):
 

Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads

Wanna join the discussion? Login to your LEADTOOLS Support accountor Register a new forum account.

#2 Posted : Monday, August 2, 2010 8:10:05 AM(UTC)

Travis  
Travis

Groups: Registered, Tech Support
Posts: 215

Was thanked: 3 time(s) in 3 post(s)

Attached is this project updated to version 17 using Visual Studio 2008.

Note: As of .NET 4.0 Framework the IEHost.dll will no longer be supported.  What does this mean?
The samples from this forum post will only work in the Framework 3.5 SP1 and earlier.

So far the only documentation we have found from Microsoft on this can found at this link:
http://social.msdn.microsoft.com/Forums/en-US/clr/thread/e293ed8e-be48-4c4a-838b-dcf3c2cec5b7

Below is an excerpt from this post:

IEHost.dll is the runtime host that provides the ability to host Windows Forms controls and run executables in IE. IEHost is a .Net 1.1 technology that provided a better model than ActiveX to host controls within the browser since they were lightweight and the controls operated under the .NET security model, where they operated inside a sandbox.

For Dev10, the proposal is to remove IEHost.dll for the following reasons
1)    IEHost/HREF-EXEs are surface area exposed to the Internet. This poses a high security risk (we already have bugs filed related to this), and most customers (by far) who install the Framework are getting very little value for this security risk. If IEHost and IEExec is left as-is, a new model needs to be designed where either (a) using this technology is safe and is always on, or (b) is as secure as today and can be configured to be turned off. The cost of doing this is very high.
2)    Customers who want IEHost/HREF-EXE-sytle controls or apps have numerous other technologies they can use, like ClickOnce, XBAP, Silverlight.
3)    Customers who want the exact same functionality as 3.5 SP1 for this feature can continue to use 3.5 SP1. This change, of removing IEHost takes effect only in .Net Framework 4.0.
4)    The opportunity cost and risk of continuing to support this feature for the CLR team is high. Going forward, we will be able to deliver more features and bug fixes that benefit more of our customers if we can remove this from NetFx4.    
File Attachment(s):
Travis Montgomery
Senior Sales Engineer
LEAD Logo
 
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2017, Yet Another Forum.NET
This page was generated in 0.215 seconds.