Hi There;
I have just upgraded from 20103.1000 to 20103.2056 and am now having huge problems in the VS2008 IDE, especially in relation to dropping data source objects on a form. The problem is not restricted to the grid, but rather to all IG controls that are bound to datasource members in the IDE.
It is the case that I have customized my data source members to utilize infragistics controls by default. After the upgrade, whenever I now drop a control on a form, the control appears both on the form itself and in the form's tray (i.e. where components are normally placed). If you delete the component from the tray, then the component is removed from the form as well. I refer you to this post which describes a similar problem:
http://forums.infragistics.com/forums/p/42616/235057.aspx#235057
The differences for me from the above post are:
In addition, I reffer you to an earlier post of today regarding a similar situation when you attempt to drag ANY databound control onto an UltraPanel control. My post is at:
http://forums.infragistics.com/forums/t/52216.aspx
It appears that there are some major issues regarding databound controls in the IDE. This is a serious problem and I would appreciate any help that you can provide.
Heeeeeeeelp
Kind Regards
Dave Ballantyne
Hi Dave,
If a control shows up in the component tray, it means that Visual Studio is unable to find the designer for that control.
Check the Assembly folder on your machine and make sure it has a reference to Infragistics.Win.v10.3.Design and that it's the same version as the other v10.3 references. If it is not there, or the wrong version is there, see if you can find the correct version on your hard drive (it should be in the same place the other assemblies are installed to) and copy it to the Assembly folder and remove any incorrect versions of that assembly.
Also make sure that this dll is not referenced directly by any projects in your solutions.
Hi Mike;
Please refer to this post which i believe is related:
http://forums.infragistics.com/forums/p/52216/272364.aspx#272364
I think that this may have something to the legacy 2.1 version that was previously installed. Although this product is no longer supported, I should still be able to manually upgrade to the current version (which is what I have been trying to do since installing the new version last week).
Note that 2.1 has been uninstalled and there are no 2.1 dlls in the assembly cache. A couple of 2.1 dlls still exist for legacy projects that have not yet been upgraded.
Interestingly, I tried to delete the 20103.1000 dlls from the cache, yet i am denied being told they are still in use. The solution I am referring to is the only solution I have worked on since I installed 20103 so no other solution could possibly refernce 20103.
Im in a real mess and dont quite know where to begin to attempt to correct the problem.
I feel I have a case of severe .net dll hell (which suposedly shouldn't occur).
I greatly appreciate you looking at this probem.
Dave
Hello Dave,
Since this was a legacy project, could you please check what is the content of "license.licx" file in your applicaiton? If there are any older references please clear the content and clean and rebuild your solution again.
Please let me know if this helps.
Hi Danko / Mike;
Cleaning the licenses.licx files did not help.
However, I fianlly have figured out what has gone wrong, and I think I may have uncovered a relatively serious issue.
When I upgraded, it appears that the references to to the Windows Form Designer\Data UI Customization objects were not upgraded as they were all showing as 20103.1000.
Therefore, whenever I dragged a bound control onto a form:
It all seems perfectly logical now that I have figured it out with all of your help. Once I reassigned all the Data UI controls to the correct version, fixed the referenced assemblies, then rebuilt my solution, everything now seems to work correctly.
I have a separate thread going with Hristo at the following link, which now appears to be the same problem. Consequently I have asked Hristo to open a case to look at what may appear to be an installation based issue.
I thank you all for the expert and timely assistance at Infragistics.
It all makes perfect sense now. We have no control over the references that Visual Studio stores for linking up UI components with the data sources.
The same issue happens with the toolbox. The Visual Studio toolbox keeps a reference to the specific version of a control at the time you add the toolbox item. If you later update to a service release or a new version, you have to update the toolbox, as well.
We help you out there by providing the Infragistics Toolbox Utility which automatically creates a tab with al of the Infragistics controls on it. But since the data source link-ups are not standardized (you set it up yourself), we don't have any way to handle that.
Thanks for posting the solution here, though. It never occurred to me that the data object link would cause a problem like this. It's something I will have to try to keep in mind for future reference.