Known Issues and Important Information

The following items are either currently under investigation by the Accusoft Engineering organization or provide further information regarding the ImageGear products and samples. Should you require an updated status on any of these items, please contact the Accusoft Customer Support Department.

NOTE: For the latest release notes and other ImageGear documentation, go to http://www.accusoft.com/documentation.htm.

ImageGear for .NET - Important Information

• In ImageGear for .NET v21.0, the use of the ImGearRecPage.Dispose() method was changed. It is now required for an application to call this method to properly clean up the native resources. If this method is not explicitly called by the application, the .NET garbage collector might dispose the object after the native resources are unloaded, which might cause a General Protection Fault in the Recognition engine.

• The ASP.NET Samples require IIS to be installed and running on the PC to run the sample.

• The ImageGear.FreqIP namespace has been deprecated and will be removed from the public API in a future release.

• Support for WinGDI rendering engine has been deprecated. It will be discontinued in a future release of ImageGear for .NET.

• Auto-detection of CUT format (Dr. Halo CUT) is disabled by default. The format is not popular and has unreliable detection. An application can enable auto-detection of the format if needed, using IImGearFormat.DetectionEnabled property.

• The ImageGear for .NET documentation provides information for all platforms and .NET framework versions. However, not all features are available for all ImageGear for .NET versions. Please refer to the table on the Welcome page of these Release Notes for information about which ImageGear for .NET Namespaces are available for which versions (Windows 32-bit platforms and Windows 64-bit platforms).

• Running Visual Studio as Administrator:
  
  Microsoft recommends running Visual Studio with administrator privileges under Windows Vista, Windows 7, or Windows 8. To properly use the ImageGear Samples, please run Visual Studio with elevated permissions. To run Visual Studio with elevated administrator permissions, first confirm you are a member of the "Administrators" group on the local machine. Then right-click the Visual Studio shortcut and select the "Run as administrator" option from the context menu. Click ‘Continue’ to the UAC prompt.
  
  To ensure you have the latest updates, after running Visual Studio, choose ‘Check for Updates’ from the Help Menu.

ImageGear for .NET - Known Issues

Adobe PDF Support Issues:

• PostScript Normalizer loses an image element when converting provided EPS to PDF. Ticket # 1-6656

• PDF sample dialogs do not support Double byte characters.

• Multiple texture 3D PDFs are not fully supported. Ticket # 1-17931

• The PostScript Normalizer, created in the call ImGearPDF.CreatePSFormat(), is unable to find the ICC profiles if any subdirectory is created in the ICC PS resource directory.

Adobe PSD Format Support Issues:

• If the PSD layers structure is organized in a tree structure it will be loaded and saved in a linear array structure.

• The ImageGear PSD reader reports PackedBits compressed files as RLE.

• PSD layer mask information is not currently supported for read and write.

ASP.NET Support Issues:

• While ImageGear ASP.NET Print Pages dialog can be used to print image data, it does not support printing of annotations.

• Some pages of multiple page PDF documents may not render correctly when printed with ImageGear ASP.NET component and JavaScript controls running from Chrome.

• Some PDF and Office documents may not render correctly in ImageGear ASP.NET 64-bit component when the client-side rasterization for vector documents is enabled.

• The ASP.NET service in ImageGear for .NET may hang in situations where PDF is enabled and the Application Domain is restarted. The following actions will cause an application restart (http://msdn.microsoft.com/en-us/library/ms178473.aspx):

  • Adding, modifying, or deleting assemblies from the application's Bin folder.

  • Adding, modifying, or deleting localization resources from the App_GlobalResources or App_LocalResources folders.

  • Adding, modifying, or deleting the application's Global.asax file.

  • Adding, modifying, or deleting source code files in the App_Code directory.

  • Adding, modifying, or deleting Profile configuration.

  • Adding, modifying, or deleting Web service references in the App_WebReferences directory.

  • Adding, modifying, or deleting the application's Web.config file.

• ASP.NET ISIS scanning - A memory leak occurs during image retrieval when calling the scan method. The amount of memory that is leaked is larger for larger images, such as uncompressed color images.

• Removing pageAdded, pageRemoved and pageChanged ASP.NET JavaScript event handlers does not take effect due to the following known issue in the Microsoft AJAX JavaScript Client library: "Use the removeHandler method to remove an event handler from an event defined in anEventHandlerList object. If the event has only one handler when removeHandler is called, the event will continue to exist as a placeholder in the EventHandlerList instance."

• The ThumbnailVertical Template will generate warnings if added to a page. However, it will still perform correctly.

• The Magnifier tool in an ImageView control reacts with a bounce to the top when dragging to the end of a control's surface that is adjacent to a Thumbnail control.

• The Magnifier sometimes displays an incorrect portion of the image when hovering over another part of the page.

• The RectangleZoom and Select mouse tools will flip the rectangle in the ImageView control if dragged towards an adjacent Thumbnail control.

• Only one new ASP.NET website project per Visual Studio instance can be correctly created, as the second project does not automatically populate the web.config  <appSettings/>.  Restart Visual Studio for each new ASP.NET project to ensure that web.config <appSettings/>  populates correctly.

• If the ImageGear uninstaller complains about seemingly random non-ImageGear applications still running, this is most likely due to the Microsoft Installer incorrectly reporting the offending application. The offending application is actually the ASP.NET worker process, aspnet_wp.exe. This process will either need to be terminated or the machine rebooted in order to stop it from running and allowing ImageGear to properly uninstall. This process is what handles all ASP.NET applications on the system, including ImageGear's ASP.NET samples.

• The following error message appears when you try to debug ASP.NET 2.0 in Vista: 
  
  "Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled. Please see Help for assistance." 
  
  Note: This happens when Microsoft Visual Studio 2005 is used in Vista. 
  
  According to Microsoft:
  
  "This problem occurs because Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. When the client tries to automatically attach the debugger in an ASP.NET 2.0 application, the client sends a HTTP request that contains the DEBUG verb. This HTTP request is used to verify that the process of the application is running and to select the correct process to attach. This HTTP request must be authenticated by using Windows Authentication. However, Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. Therefore, the problem that is described in the 'Symptoms" section occurs."
  
  Note: The solution to this error is to install the hotfix from Microsoft at: 
  http://support.microsoft.com/default.aspx?scid=kb;EN-US;937523

Display Issues:

• ImGearPresentationPageDisplay did not support background drawing. Any modification of the background mode or color had no effect. Background drawing is now supported, but to avoid possible issues with the behavior change, the default background mode has been changed from ImGearBackgroundModes.BEYOND_IMAGE | ImGearBackgroundModes.UNDER_IMAGE to ImGearBackgroundModes.NONE. To enable background drawing for presentation page display, set the ImGearPresentationPageDisplay.Background.Mode property to ImGearBackgroundModes.BEYOND_IMAGE.

• Important PageView Display Dependency Properties: Deriving from System.Windows.DependencyObject does create some new requirements that may affect applications upgrading to the new version.

Installation and General Usage Issues:

• It has been reported that when installing to 2003 Server x64 or XP x64 the Installer can prompt the user that the 'Windows Imaging Component' is required and further report failure trying to install it. This can be safely ignored. The ImageGear installation will continue without issue after that and the product will function without issue.

• Due to an issue with InstallShield, after the installer installs the 2.0 .NET Framework, the MSI service is no longer available to the ImageGear installer, so it fails with the following error message: 
  
  "Error 1719. Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled." 
  
  Note: Simply re-running the installer will allow it to install properly.

• As a result of the obfuscation used in ImageGear for .NET v19.0 (or later), Managed C++ cannot currently be supported. It is hoped that Managed C++ will again be an option for ImageGear users in future releases.

• If you are using ImageGear Professional ArtX to convert binary *.art files into XML art files, legacy marks contained in the .art file are saved into an XML file without conversion to ART 3.0 marks. Although the resulting XML file can be opened in ImageGear Professional ArtX, ImageGear .NET ART will not open it. As a workaround, you can manually convert legacy marks to ART 3.0 marks before saving them to XML, or use a binary *.art format for interchange between ImageGear Professional ArtX and ImageGear .NET ART.

JPEG 2000 Format Issues:

• ImageGear for .NET rounds JPEG 2000 Resolution metadata values by truncating the decimal part when saving or updating JP2 and JPX files.

• ImageGear for .NET v20 (or later) incorrectly loads Indexed JPX files saved by previous versions of ImageGear. ImageGear for .NET loads them as grayscale instead of indexed. The issue is caused by the presence of an empty Channel Definition box in these files, which is incompliant.

• JPEG 2000 files with invalid length of SOT marker that used to load in previous versions of ImageGear will not load in version 20 (or later) and will instead report the following error: "Too many bitplanes to guarantee reversible decoding.".

• JPEG 2000 files with alpha mapping to individual channels are now displayed without transparency. JPEG 2000 files with alpha mapping to all channels are displayed with transparency.

• Invalid JPEG 2000 files that used to load in previous versions of ImageGear with a warning: "Color description (color) box found inside a compositing layer header (jplh) box, but not wrapped by a color group (cgrp) box." will not load in version 20 (or later) and will instead report the following error: "Error reading j2k stream. Found misplaced codestream in the file format wrapper. Failed loading the source file."

Microsoft Office Support Issues:

• Large shapes covering several paragraphs in a Word document (and wrapped to be in front of text) might render at the wrong position.

• Upon changing document page size using ImGearWordDocument.Repaginate method, if a page within the document contains pictures/shapes that are larger than the new page size, the following behavior is possible:

  • When using ImGearPresentationPageDisplay in WPF scale mode, the portion of the element that does not fit into the new page size will go beyond the page borders.

  • When using ImGearPresentationPageDisplay in Native scale mode, or ImGearPageDisplay, or rasterization, the page will be extended with a black area under the element.

• Microsoft Office Open XML gradients with transparency are converted as non-transparent PDF gradients.

• Microsoft Office Open XML text elements with gradient fill and stroke are converted to solid PDF text with the color of the first gradient stop.

• Microsoft Office Open XML text with patterns is converted to solid black PDF text.

Recognition Issues:

• Setting ImGearRecAsianSettings.UseFullCharacterSet to TRUE causes ImageGear to return an error during the recognition process. Ticket # IGNET-1369

• The Text preview box in the recognition samples only supports Windows code pages, Unicode (UTF-16), and UTF-8. Text in other code pages, such as DOS or WordPerfect, can still be recognized and saved to output documents, but displays incorrectly in the preview box. Ticket # 1-12203

• The recognized output of some zones can be swapped in the final output if zone location is done explicitly rather than as part of the Recognize call. Ticket # 1-12023

• Currently, the FRX Recognition module supports a maximum image resolution of 900 DPI. Ticket # 1-12074

• ImGearRecLetter.AlternativeLanguage always reports ImGearRecLanguage.NO if ImGearRecRecognitionSettings.Tradeoff is set to ImGearRecTradeoff.ACCURATE or ImGearRecTradeoff.FAST. Ticket # 1-12228

• Image metadata is lost during page import/export operations from the Recognition Component.

Vector Format Issues:

• Direct3D is not allowed to run under IIS. Use OpenGL for rendering CAD images in web applications.

• Specific CGM files with tile arrays containing raster data compressed with different compression types are not supported. Ticket # 1-14750

• Cannot render some DWG images under Windows 2003 with Direct3D. Ticket # 1-16967

Back to Top