Version: 1.0.5.5
Ajax-enabled interactive image viewer provides in-place pan, zoom, and dynamic loading of high resolution images. Display large images on demand without writing JavaScript or using plugins! 
Q: Can I use PowerWEB Zoom with other PowerWEB products such as LiveControls?
A:

Yes, PowerWEB Zoom is fully compatible with PowerWEB LiveControls and TextBox. By combining other PowerWEB controls in your application, extremely rich applications can be developed. For example, using LiveControls, you can change properties and images within Zoom without using a PostBack.


Back to Top
Q: How is PowerWEB Zoom different than Google Maps?
A:

Google Maps is an excellent application for generating maps, point-to-point driving directions and satellite photographs. PowerWEB Zoom shares some of the pan and zoom functionality, but is a general purpose image viewer, not limited to maps. Also, Zoom is used as an ASP.NET server control and does not require any javascript coding or external APIs to function.


Back to Top
Q: Does Zoom work with ASP.NET 2.0?
A:

Yes, PowerWEB Zoom functions under ASP.NET 1.0, 1.1, and 2.0 and is compatible with Visual Studio versions 2002, 2003 and 2005 as well as Visual Web Developer 2005.


Back to Top
Q: What is the largest image I can use with PowerWEB Zoom?
A:

While there are no hard-coded limits to the size of an image that may be used with Zoom, there are some server resource limitations that must be taken into consideration. Zoom renders resized images and tiles on the fly and stores them on disk. If using particularly high Quality and InterpolationMode settings, these images may take up a significant amount of disk space. Also, for optimized performance these rendered images and tiles are cached in memory on the server for a configurable amount of time. A good rule of thumb is to keep source images under 5MB in size and to test your application for resource consumption before deployment.


Back to Top
Q: Where can I find sample applications or code?
A:

PowerWEB products all ship with several samples that are designed to demonstrate the core product functionality within many environments and programming languages. If there is a particular sample that you would like to see, please contact support@dart.com or post your suggestions on the product support forum.


Back to Top
Q: Under Visual Studio 2005, I do not see any help pages when I hit F1. How do I correct this?
A: To see the help topics within Visual Studio 2005 and Visual Web Developer 2005, go to Tools > Options. Under Environment > Help > Online (make sure "Show all settings" is checked), ensure that "Try local first" is selected. This will find the installed help files before attempting to look online.
Back to Top
Q: What are the Ajax features of PowerWEB Zoom?
A:

Ajax has become a buzzword that is sometimes misused when meant to describe simple client-side functionality. In reality, Ajax is browser to server communication for updating or retrieving data, ultimately driving interface changes. These changes do not require full page PostBacks or refreshes. In this way, Zoom is fully Ajax-enabled. As you pan around an image, sections of the full image are rendered on the server and loaded into the browser view area. When a zoom is performed, the source image is resized on the server and delivered to the client on-demand.


Back to Top
Q: Why do I see an 'Attempting to deserialize an empty stream' exception when I build my VS.NET 2008 Website?
A: Websites create an App_Licenses.dll for component licensing which must be distributed with the application.  Due to an apparent VS.NET 2008 bug, this dll is faulty when created during compilation on a 64 bit Operating System.  To work-around the problem, the App_Licenses dll in the 2008 Website can be replaced. 

Options include:
a) Compile a 2005 WebSite on the same (licensed) machine using the same controls/components
b) Compile a 2005 or 2008 WebSite on a 32 bit OS machine, provided this machine is also licensed (Dart Developer licenses allow installation on up to two machines)

Replace the faulty App_Licenses.dll with the resulting dll from one of the options above, and the Website should build and deploy without issue.  Do not delete the new dll, or VS.NET will again create a new faulty one in its place.


Back to Top