-
You need these older versions from the bottom of the download page : ASP.NET Menu - Developer License -> Web.UI version 1.5 for ASP.NET Menu 2.x for ASP.NET - Developer -> Web.UI version 2.0 for ASP.NET
-
The ComponentArt.UIFramework.lic and the ComponentArt.Web.UI.dll files need to be in the /bin folder for licensing to function. If this is the case, there is likely some other issue with your environment. You should open a support request to further diagnose this. Regards,
-
System.Security.Cryptography.RijndaelManaged is used by the licensing functions and, as you have noticed, is not FIPS compliant. Unfortunately, the licensing code is not distributed, so you cannot fix this yourself with the product source. Depending on which products you are using, there may be a workaround for you. Please open a support request and we can persue it there.
-
[quote user="JGarlandX"]What license key can we use for the Beta?[/quote] If you have an active subscription, you can find your 2010.1 license key on the My Licenses page. We are planning to release the RTM within 30 days of the beta. Hope this helps.
-
Any major version of the control suite requires the corresponding version of the license file: UI Framework 2009.1 requires a 2009.1 UIF license file UI Framework 2009.2 requires a 2009.2 UIF license file etc... If you are seeing unlicensed warnings when the correct corresponding version of the license file is present, you should open a support incident and our support team can assist. Hope this helps.
-
I've looked further into the issue. It seems that things have changed in Windows 7 x64 with regards to registry reflection. This will affect licensing on Windows 7 x64 systems where the application is not using a .lic file in the bin folder. So, until the License Manager is fixed, you have these options: deploy a .lic file in the bin folder of your application set Enable 32-Bit application = true for the IIS7 application pool under which your app is running export the registry key HKEY_LOCAL_MACHINE...
-
I have not been able to reproduce this with the following configuration: Windows 7 Professional x64 Visual Studio 2008 SP1 Web.UI 2009.3 SP1 I have added several AJAX controls to the web form. They are licensed correctly in debug mode. To pursue this matter, I suggest you open a support request . Our Support Team can look into things in more depth with regards to your specific scenario.
-
[quote user="support@genilogix.com"]I had ComponentArt WebUI 2008.2 (fully licensed) on this machine and wanted to try UIFramework 2009.3 out before buying. I uninstalled WebUI 2008.2 and then tried to install UIFramework 2009.3. I selected "I would like to continue evaluating this product for 30 days." and hit Next >. At that point, I get a dialog stating "ComponentArt.License.Manager has stopped working".[/quote] It appears there is a bug in the 2009.3 license manager...
-
I am doing all my work on a dev server. I installed the controls on the server using the install file I downloaded from CA. Do I have to install the controls on my stage and production server or can I just push up the dependant files from my dev. I think the dependant files are: website root\licenses.licx bin\ComponentArt.Web.UI.dll bin\ComponentArt.Web.UI.dll.refresh bin\App_licenses.dll Is this correct? I don't see any references in the web.config file for the components so it looks to me all...
-
Hey Stephen, Following were my steps: Enter License Key, Develop, move to production, Found out I had HTTP/HTTPS problem Changed Util code to accomadate Move to production, Get License key error on Production Do I have to re-enter the license key with the new dll? Thanks and please let me know, Dhaval