Hi,
I try to install NetAdvantage_WinClient_20102.exe on Windows 8 with Visual Studio 2012.
The Problem is that the License Key isn't accepted. I've checked my Account, the Key is use is the same as listed in my account.
This is a local Problem, because it works with other Computers (ok, it had worked with an older Windows patch level).
Any help would be appreciated.
Johannes
Mauve Mailorder Software
Hello Johannes,
It is not possible to use version 10.2 with Win 8 and VS 2012. Please take a look for more details on http://www.infragistics.com/help/supported-environments/
Also the product lifecycle of that version is expired. For more details: http://www.infragistics.com/help/product-lifecycle/ . My suggestion is to upgrade your product to latest supported versions.
Let me know if you have any further questions.
Regards
Hello,
excuse me if I must correct you: It is possible to use Version 10.2 with windows 8 and VS 2912. Only the automatic integration in VS 2012 doesn't works, you have to do it manually. I know that cause previous to the new installation it worked with Windows 8 and Vs 2012. And there are other computers in our company which use this configuration without any problems.
I just want to know why the installation doesn't accepts the serial number.
An update to the latest infragistics version is not easy possible, cause we than have to update all our products, which is a huge task, so it is no option in the short term.
Thank you for your help,
Best regards,
Johannes,
If you haven't already, reboot the machine and run the installer again. With the older installers, there is a issue where a bad key entry is sometimes cached and doesn't actually get cleared until the machine is rebooted. Typically this happens if you copy and paste the key from a rich text source. If you are copying an pasting the key rather than typing it in, paste it into a plain text editor like Notepad and copy it from there before pasting in the installer.
Let us know if you have any questions with this matter.
This solution above worked for me. We are in a situation where we cannot upgrade to the latest and must use 2009.1.