On three of our development machines, all IG controls are in the foreground and the developers can work with them. On my machine, all controls are in the background with no way to bring them to the foreground. I can see them, but I can't click on them at all to work with them. Any idea why?
Hi Mark,
This sounds like a license issue. Please try the following:
1) Ensure that your project is referencing the correct DLLs. The minor version number of the DLLs should match the version of the DLLs installed in your GAC.2) If there is a licenses.licx file, open it and clear out the contents. Sometimes old version information is retained in this file.3) Clean and rebuild your project.
Please let me know if the issue persists after performing these actions.
Thank you. No luck with any of that. All Infragistics controls are still inaccessible on my machine. Any chance support can log in and check it remotely?
Mark,
Please provide a screen shot of what you are seeing on your machine.
Attached. I hope (not sure how to post an image here). This is two different screen. I can't click on the tabs in the top image, and that combo box can't be clicked on. Selecting it in the properties window has no effect either. If you'll notice, that is the UltraGrid in the top image... the blue bar at the bottom of it should have a start button and wording next to it. All of the ultragrids in the project have the blue bar, but none have the start button or the wording. Hope this helps.
http://s1155.photobucket.com/user/BCM12345/media/ig_zpsenyli5gn.jpg.html
The behavior that you are seeing is what you would see if the designer for the control isn't available. Is the version of the Infragistics controls that you are using installed on your machine? If not, installing it is likely to resolve the issue.
There are more details on a similar issue in the thread here: http://ko.infragistics.com/community/forums/t/50748.aspx
For the image, it is likely failing if you are trying to add the link to photo bucket as it is an html page and not an actual image. if you right click on the image from bit bucket and get the image location and use that it appears to work.
Let me know if you have any questions with this matter.
Compared my installed version to that of my team. They had 16.1.1000. I had 16.1.2033. My installation included the service release update, while theirs didn't. I uninstalled my version and installed 16.1 without the service release so I am at 16.1.1000 now also and everything seems to be working fine. Is the version mismatch the cause, or is the latest service release the cause? I would like to update the team to the latest, but am concerned it will destroy the project.
Thank you for the prompt, clear responses. It is truly appreciated.
The version mismatch is the most likely cause of the issue. For example this would happen if the assemblies for version 16.1.20161.1000 are included locally in your project when you had the service release installed.
In that case changing the references locally on your machine to the service release version would have resolved the issue with the designer for your machine. You could test this by installing the service release again and making sure that the version from the GAC is referenced rather than the 16.1.20161.1000 version is referenced.
Let me know if I may be of further assistance.
When you install the service release version 16.1.20161.2033 would have been in your GAC and that would have been the version for the design assemblies on your machine. It is possible that the references for your project would have still been pulled from somewhere such as a libraries folder within your project and could have been using version 16.1.20161.1000. You can see where your references are coming from by looking at the properties of the references in Visual Studio.
As far as changing the reference to point to another location, this could be done with reference paths, removing and re-adding the reference, deleting/moving the file form the location it was in on the filesystem if a hint path was set. Typically we would recommend using our version utility to upgrade the references of your project when you install the service release as that would set the version to be the installed service release.
As far as the designers working, they must match the exact version so the design assemblies for the service release will not actually work with the volume release.
For your last question, after installing the service release run our version utility to upgrade your project and you will want to clean and rebuild your application including any dependencies that reference the Infragistics controls.
Let me know if you have any questions.
Trying to make sense out of what you wrote... Few questions:
Are you saying I would have had two versions of Infragistics4.Win.UltraWinGrid.v16.1... one with 1000 and one with 2033? Not sure how we would change the reference.
Shouldn't any version work, especially a later version?
Once we re-run the installer and get the service release, and do that on all machines, we should be good?