Tilmann,

Do they work on your XP VM?  If so is it an option to use your XP VM for development of the project using these controls.  Maybe the registry entries are in the wrong location and need to be in the WOW6432Node or outside of it on the 64 bit Windows 10 machine.  You could try duplicating the entries in the other location to see if that makes a difference.

Are you only testing this in your existing application or have you also tested the controls in a new VB6 project to see if they work there?  If the work in the new project maybe the version installed is different from what your project references.

Please note that these controls have been retired for over 10 years and were not tested on any newer operating system than Windows XP (and I am not even sure they were tested on XP).  Retired products are provided as is without support.  If you would like help accomplishing the same functionality with one of our current control sets, we will be happy to assist you.

Let me know if you have any questions with this matter.

For the last two questions, I am not sure what needs to be copied over from the old machine.  If you run the installer on a new VM for XP, you could also watch for file system changes to see what files are present and if there is a file that might provide the licensing information. 

As far as if those assemblies are needed or not, I don't know and it may depend on what you are using. 

Regarding skipping the license check, this would require recompiling the controls from source code so no that isn't possible unless you obtain the source code.  If the controls you are using are part of UltraSuite 3.02 then you may be able to get access to the source code by purchasing it and you can reach out to sales@infragistics.com for more information on purchasing the source code.

Tilmann,

These products have been retired for over ten years and there is no support for them anymore.  We don't have these registry settings listed anywhere and the best way to find what changes would be to watch the registry for changes when installing on an XP VM so that you can see exactly what has changed.

As far as the assemblies that you need to register manually, you would need to register the ones that you use.  If you aren't using an assembly, then not registering it will not impact you.  As far as where these assemblies are, I assume they are in an install folder though I am not certain.

The installers were never tested on a 64 bit operating system as that was first done in 2006 and the installer is older.  It is possible that the the registry keys are written in the wrong location and not found because of the Wow6432Node.  If you run the installer on a 32 bit XP VM and copy over the relevant registry entries as well as the assemblies and manually register the assemblies with regsvr32 it is likely that it will resolve the licensing issue.

If you are using a 64 bit operating system, it is likely that the following thread will help you:

0

Alan Halama answered on Jul 27, 2016 5:03 PM

Yellaiah,

The application that you are trying to compile is using NetAdvantage for ASP.NET 2010 Volume 3 and you need to have this installed on your machine.  You can download this from the My Keys and Downloads page as long as you have your product key registered for that volume.

Let me know if you have any questions with this matter.

Yellaiah,

The application that you are trying to compile is using NetAdvantage for ASP.NET 2010 Volume 3 and you need to have this installed on your machine.  You can download this from the My Keys and Downloads page as long as you have your product key registered for that volume.

Let me know if you have any questions with this matter.

Hello,

The Development issue that was logged for the exception thrown with the Rank.EQ function has an ID of 211312.  This is now resolved and is available in the latest service release which can be downloaded from the My Keys and Downloads page.