AceGallery FAQ.

This section will be updated based on user experience and feedback.

Installation and usage.

Q: What version of ASP.NET and Visual Studio is required for AceGallery?
A: AceGallery runs on 2.0, 3.0 and 3.5. It will not work on V1.1 or lower. Visual Studio 2005 or 2008 are required to use AceGallery control.

Q: How to install the AceGallery component/control?
A: Just copy the AceComponents.AceGallery.dll file to the bin folder of the ASP.NET website and it should be ready.

Q: How to add the AceGallery to the designer.
A: After you copy the dll file to the bin directory, open the desired ASPX page in Design mode. Right click the toolbox, and select "Choose items...". Next, give the path of the AceComponents.AceGallery.dll from the bin folder. You should now see the "AceGallery" item visible on the toolbox. You may also have to add a Reference to the AceComponents.AceGallery.dll file by right clicking your project on Solution Explorer, and selecting Add Reference.

Just drag and drop that to the designer surface and you should see this.

Q: How to set properties of the control?
A: Properties can be set either from the Source view of ASPX page

or the code behind file as below.

Q: Do I have to call any methods before the control can be used?
A: No. There are no methods or server side events to handle to make it work. However there are Events that are fired when directory is changed or page is changed. These can be used to take furthur action or notification.

Q: Where can I find the help file?
A: Help file is located in the Zip file containing the AceComponents.Acegallery.dll file. Special note for Vista users: Vista doesnt show the contents of the help file by default. Please read the text file that comes with the help file on how to fix this. You can download the help file from here. Click here.

Q: How does the AceGallery work?
A: When the page containing AceGallery is loaded for the first time, the control will automatically create a "Preview" and a "Thumbnails" folder in the target directory and then generate the corresponding Preview and Thumbnail images for each original file. Therefore it is required that the Windows user account under which the ASP.NET process is running should have sufficient permissions on the target directory. After that for every page load, the control will use the saved thumbnails and preview images.

Q: What happens when I add new images to the input directory?
A: AceGallery will automatically create thumbnails and preview images for those files as long as their extension is included in the FileType property of the control.

Q: What happens when my original image files are changed?
A: AceGallery cannot know that the contents of the files are modified since the thumbnails were generated. So it will continue to show the old thumbnails and preview images until the admin deleted them or sets the "AlwaysRefreshThumbnails" property to true. Check the Help file for this property for recommended usage.

Q: What happens when my original image files are deleted?
A: AceGallery will not display the thumbnails or preview images on the gallery, but they will still be there on the disk. It is upto the site admin to delete the unwanted files.

Q: What happens when exceptions are generated inside AceGallery?
A: AceGallery will not handle any exceptions. All exceptions are supposed to be handled by the client code.

Pre / Post Sales Inquiries

Q: Is there a Free version?
A: Yes. If you do not want to pay for a license, then you can create an empty license file as below and use the licensefilepath property to supply that file name. Once you do that, users will see Google or Amazon (randomly selected) ads in the Gallery section. If in the future, you decide to purchase a valid license, just replace the below text in the license file with the License information we send you after the purchase. The ads will be removed without any code change on your part.

See a demo of AceGallery with Ads

Q: I downloaded the trial version and the control is running very slow. Why is this?
A: The control will run slower in the demo mode, if you are not displaying ads or have not bought a license yet. This is becuase in the demo mode, the thumbnails will be created everytime the page is loaded. Once you use the "ad license" or buy a actual license, the control will be much faster.

Q: What types of payment methods are accepted?
A: All payments (including credit cards) are accepted through Paypal. There is no other payment option.

Q: I recently purchased the AceGallery component and never got my license information?
A: Once the payment is completed and verified, the license information is emailed to the address which was supplied during payment. This should normally happen instantly. Sometimes there maybe problems with Paypal or our hosting servers which may cause delays. Also, your email server may be the cause of delay. Please do check your Junk mail folder to make sure the email didn't end up there. Try to avoid public email addresses like Hotmail or Yahoo during checkout. If you think its been too long, please contact us.

Q: I am interested in your product but there are some features that I want and they are not there. Can you customize the control for me?
A: If you need to customize this control, please send us an email to . While we cannot guarantee that we could customize it, we will try our best to do so. It depends on your requirements, the development costs and time constraints.

Technical Support.

Q: What kind of technical support is provided for customers?
A: Limited support is provided for customers in form of email only. A free trial version is provided so that the component is fully tested on your project. Once you are satisfied with the trial version, all you have to do is just place the text file with the license information send to you. The code would be the same. If you still have problems, please email us at and I will do my best to resolve the issue. Please note that the support is only for errors related to this component. Support is not provided for styling, formatting (CSS Related) or any other issue that can be fixed by the end user.