User (Old forums)MemberFebruary 2, 2010 at 1:55 pmPost count: 23064
The general Xceed components package always defaults to installing the samples under “C:\Xceed Component Samples\“, whereas the other packages use “C:\Xceed Samples\“. This is quite annoying, especially as the installer for the general package can take up to 60 seconds to change the path, and the other installers don’t offer an option. If there’s no way for the installer to remember the sample path used in the previous installation, could it at least default to using the same path as the other packages?
On a related note, could we please have some consistency with launching the “Resource Center” after the install? The general package opens the application before you click the “Finish” button; one of the Silverlight packages offer an option to launch it after you click the button; the other packages have no option, and always launch after you click the button. When I’m trying to install five sets of updates, it’s quite annoying to have these windows popping up in the background.
Imported from legacy forums. Posted by Richard (had 2302 views)User (Old forums)MemberMay 5, 2010 at 4:05 pmPost count: 23064
OK, the new installers for the .NET 3.5 components seem to have addressed this, and the installer for the .NET 4.0 components is much better.
The downloads page is getting a bit confusing – for example, it’s not entirely clear that the Ultimate Suite installer includes all of the .NET 4.0 components (and the ActiveX components?) so the other .NET 4.0 downloads aren’t needed. For .NET 3.5, all of the individual downloads are required.
Also, the Component Licenser tool no longer recognizes my keys for the ActiveX components – “You have entered a key for a product which is not installed”.
Imported from legacy forums. Posted by Richard (had 419 views)Diane [Xceed]ModeratorMay 7, 2010 at 5:13 pmPost count: 1353
Thank you for your feedback. I submitted a request to the development team to have this looked into to see if we can improve the download page, and also fix this issue with the Component Licenser.
Imported from legacy forums. Posted by Diane [Xceed] (had 308 views)Diane [Xceed]ModeratorMay 10, 2010 at 5:18 pmPost count: 1353
In order to continue investigating the issue with the Component Licenser, we would need to know the license key that you are trying to add to it. You can send the answer by email to firstname.lastname@example.org (please include “case 133443” in the email title so that it gets automatically sent to the fix request already in progress). Thank you.
Imported from legacy forums. Posted by Diane [Xceed] (had 2499 views)
- You must be logged in to reply to this topic.