Afternoon,
I am having issues getting the Infragistics controls installed on my machine to be correctly recognised. They were installed by adding the OE Ultra Controls to an existing OE11.3.1 installation, installed under the same user as the original installation. They appear correctly under the Referenced Assemblies in the existing Eclipse project which uses them, and can be opened up in the Class Browser. All of the dlls appear to be present and registered to the correct locations as compared to a working installation on another machine. However, nothing will recognise them as being present. Within Eclipse the project shows errors saying that it cannot find the interface or class wherever an Infragistics control is referenced. Attempting to compile outside of Eclipse using the command line also fails for the same reasons, so we are confident it is not a configuration issue within Eclipse itself.
If anyone has encountered this or similar, any help you could provide would be much appreciated
Brian, they are installed locally.
Brian, I can answer this... (I've been trying to help Robin with this & he's not at his desk at the moment).
The symptoms are as if the controls can't be found/used by progress...
The same compile errors happen when compiling the project inside Eclipse (project build) & outside of Eclipse (using the Ant/PCT build script that works on other PCs.
No network source is used anywhere. The same project setup works on other developer PCs.
The only differences that I can think of between Robin's PC & the other Dev PCs are:
We've compared where the dll's have been installed on various Dev PCs & they're all in identical locations to Robin's installation.
e.g. "Infragistics4.Win.v13.1.dll" is in:
The most puzzling aspect for me is that if I go to the projects Referenced Assemblies, I can see the Infragistics DLLs there. I can also open the infragistics controls in the class browser & browse the individual Infragistics classes .
My suspicion is that the OE installer has done something different when adding a component to an existing installation.
Afternoon,
I am having issues getting the Infragistics controls installed on my machine to be correctly recognised. They were installed by adding the OE Ultra Controls to an existing OE11.3.1 installation, installed under the same user as the original installation. They appear correctly under the Referenced Assemblies in the existing Eclipse project which uses them, and can be opened up in the Class Browser. All of the dlls appear to be present and registered to the correct locations as compared to a working installation on another machine. However, nothing will recognise them as being present. Within Eclipse the project shows errors saying that it cannot find the interface or class wherever an Infragistics control is referenced. Attempting to compile outside of Eclipse using the command line also fails for the same reasons, so we are confident it is not a configuration issue within Eclipse itself.
If anyone has encountered this or similar, any help you could provide would be much appreciated
Flag this post as spam/abuse.
.NET framework versions are identical on the PCs that work & the one that doesn't. (I've checked using the registry & we have 4.0 + 4.5)
The same problems occur in a fresh workspace.
- Note that the problem still occurs when compiling the project outside of Eclipse (running Ant from command line) - this strongly implies that the problem is not within Eclipse, but is to do with the installation of the controls.
When creating a fresh project in a fresh workspace on Robin's PC (the one with the problem), with a project type of "GUI for .NET", he cannot add Ultra controls to the auto-created "Form1.cls" (because the controls are disabled in the toolbox).
To test, I created a project on my (working) installation & then dropped an UltraTextEditor on it.
I then copied the project to Robin's PC & imported it into his fresh workspace.
When opening "Form1.cls", the following Visual Editor error is shown:
"unable to resolve type information for type Infragistics.Win.UtlraWinEditors.UltraTextEditor for field ultraTextEditor"
The 11.3 vs 11.3.1 question might be the gotcha I've been looking for.
The existing OE11.3 installation was already on SP1.
The 11.3 (SP0) installer was run to add the component.
Is this likely to have caused a problem?
(& if so... how do we fix?)
Brian, 11.3.1 has been installed for some time. The 11.3 installer was used to add the Infragistics controls, the 11.3.1 installer didn't give the option to add new components.
I'm sure that this is the issue.
I misspoke earlier when I said that we had the same dll files installed.
I've just spotted that Robin has 13.1.20131.2015 of the controls & I have 13.1.20131.2048
So, we need to install the SP1 controls on Robin's PC.
Can we just re-run the SP1 installer?
... or just run the "NetAdvantage_WinForms_20131.2048_SR.msp" from SP1 installer's "3party/uictrls/" directory?
Ran the 11.3.1 installer again, and it has cleared all of the errors.
Thanks for the help everyone.
Robin
The 11.3 vs 11.3.1 question might be the gotcha I've been looking for.
The existing OE11.3 installation was already on SP1.
The 11.3 (SP0) installer was run to add the component.
Is this likely to have caused a problem?
Flag this post as spam/abuse.
Re-running SP1 solved Robin's problem.
We hit a nasty gotcha on a colleague's machine though, which meant that SP1 silently corrupted his PDSOE installation...
He had at some point in the past (accidentally) updated his PDSOE Eclipse installation to 3.7.2 (probably while installing a v3.7.2 compatible version of the JDT plugin). This (unsupported) configuration generally works & so no alarms were raised at the time.
The problem was that the OE11.3 SP1 installer successfully removed the OE11.3 Eclipse plugins, but silently failed to install the OE11.3.1 version of the OE Eclipse plugins. (I'm guessing that this is because IntegrateArchitect.bat refuses to install into 3.7.2 Eclipse installations).
This had the net effect of making Eclipse refuse to startup, with a log file entry reading "java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini)."
We're now uninstalling & reinstalling 11.3 + 11.3.1 to correct the issue.
Re-running SP1 solved Robin's problem.
We hit a nasty gotcha on a colleagues machine though, which meant that SP1 silently corrupted his PDSOE installation...
He had at some point in the past (accidentally) updated his PDSOE Eclipse installation to 3.7.2 (probably while installing a v3.7.2 compatible version of the JDT plugin). This (unsupported) configuration generally works & so no alarms were raised at the time.
The problem was that the OE11.3 SP1 installer successfully removed the OE11.3 Eclipse plugins, but silently failed to install the OE11.3.1 version of the OE Eclipse plugins. (I'm guessing that this is because IntegrateArchitect.bat refuses to install into 3.7.2 Eclipse installations).
This had the net effect of making Eclipse refuse to startup, with a log file entry reading "java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini)."
We're now uninstalling & reinstalling 11.3 + 11.3.1 to correct the issue.
Flag this post as spam/abuse.
Brian,
When I noticed that my colleague was missing a load of OE Eclipse plugins, I tried running IntegrateArchitect.bat on the
%DLC%\oeide\eclipse installation (although I tried "-install", not -"update").
That then gave me the error message that it couldn't install into Eclipse 3.7.2 which is when I found out that my colleague had accidentally updated Eclipse to 3.7.2.
He's just finished uninstalling/reinstalling 11.3+11.3.1 - I'm very hopeful that this will work!
thanks for all your help