Vince,

Thanks for the suggestion.

I looked and we do have Copy Local set to true. It has been true for months and across multiple versions of NetAdvantage.

After I set it to false and removed the UltraWinGrid assembly from my output directory I still get the WinGrid in the component tray. That is true even after a rebuild and a restart of VS.

I am confused by your mention of a design-time assembly. I only see one version of the UltraWinGrid assembly. There are 2 instances of it. One where the Reference copies it from and one where it copies it to. Where does the UltraWinGrid design-time assembly come from?

Also, other developers on my team can see the custom designer using the same project with Copy Local set to true.

Is there anything else I can check.

Thanks.

I've just found out that some of the information I've provided on design assemblies is a bit dated.  We removed some (though not all) of these separate design-time assemblies some time ago.  For WinGrid in particular, its separate design-time assembly was removed back in 2007 Volume 1.

So, while what I've written would still be applicable to the general scenario when there's a design-time assembly invvolved, that's probably not the cause of your particular situation.

Thanks for clarify the design-time assemblies issue. 

I tried your suggestion to repair Visual Studio and it did not make any difference. I will try to figure out what is different on my coworkers' systems from mine.

Any time the grid shows up in the system tray, it's because Visual Studio is unable to find the grid designer.Setting CopyLocal to try on the assemblies can cause this kind of issue because if you set CopyLocal to try on an assembly that also exists in the GAC, VS gets confused about which one to use - and it ends up using both and loading two versions of the same assembly into memory. 

Another potential reason this might happen is if your project is referencing the design assembly. Make sure there are no references in any of the projects in your solution to the Infragistics2.Win.Design or Infragistics2.Win.UltraWinGrid.Design assemblies. Be sure to check all of the projects in the solution. You might also want to check in the bin folders of each project and make sure there are not local copies of either of these assemblies in those folders.

I would also try clearing out the contents of the licx file in your projects in case that is referencing the design assemblies. 

Mike,

Sorry for the long delay. I had a release deadline looming and had shelve this problem. I have been limping along without being able to use Infragistics controls in the VS designer.

The projects that set CopyLocal are used by everyone else on my team without problems.

I checked for multiple copies of the "Design" assemblies as you mentioned and have not found any.

I searched all of the project files for references to the "Design" assemblies and found no use of them. The same is true for the licx files.

I have uninstalled and reinstalled Infragistics.

Any other suggestions?

Turn off CopyLocal and see if that helps. Perhaps the others are just getting lucky.

You cannot have an assembly in a project set to CopyLocal and also have it in the GAC. Since all of the Infragistics assemblies are installed into the GAC by the installer, this will always be the case for the Infragistics components. When you do this, Visual Studio loads two copies of the same assembly into memory and gets confused.

Hi,

If it helps, I've just gone through some pain with this:

I had this same issue in VS 2010. Checked all the suggestions here with no joy.

'Repaired' VS2010. No joy (half a day gone)

Installed VS 2012 . (another half day).  Still no joy.

Noticed that in the last response, there was mention of putting the *Design dlls into the same folder as the main folder. In my installation (Infragistics35 v10.3) I saw that there was a subdirectory "Design". ( C:\Program Files (x86)\Infragistics\NetAdvantage 2010.3\ASP.NET\CLR3.5\Bin\Design).

I copied all these dlls to the parent

It all worked.

Can't say I'm too happy with Infragistics with regard to what appears to be a fundamental referencing error... something in the registry???

Thanks for the forum support.

regards,
Duncan.

Had the same problem with NetAdvantage 11.2 and VS 2010.

None of the above sugestions helped at all.

So from another Development computer; I copied the Infragistics2.Win.v11.2.Design.dll and Infragistics2.Win.v11.2.Design.xml files into the C:\Program Files\Infragistics\NetAdvantage 2011.2\Windows Forms\CLR2.0\Bin folder on the computer that was exhibiting the problem.

And that solved the problem.

Thanks for posting what you've found, as this may help someone else encountering a similar situation in the future.

OK, I found it.

I forgot to install the Infragistics patch we are building with. My installed assemblies were not the same version as what was in the third party folder. So that accounts for the 2 conflicting versions.

Thanks.

I turned off CopyLocal and also removed the Infragistics assemblies from the build's output folder. But I still see the same behavior. So perhaps it is more than bad luck tripping me up.

We do have a folder under our source tree for third party libraries. There are copies of the Infragistics assemblies in that folder. When we add a reference to an Infragistics assembly, we use the version in the third party folder. The Infragistics designer assemblies are not in that folder.

When I used ProcMon, a process monitor tool from SysInternals, I found that adding an UltraGrid causes a large number of accesses to both the Infragistics install folder and to our third party folder.

Is that the double loading you are talking about?