I am still trying to work through this conversion to .NET 4.5. I cannot create a sample project to recreate. All Infragistics controls will not render in the designer in VS2012 or Blend CTP2 Update2. Here are examples of the errors:

Exception: The component 'Infragistics.Windows.Design.SmartTagFramework.SmartButtonAdorner' does not have a resource identified by the URI '/InfragisticsWPF.Design.VS2012;component/smarttagframework/smartbuttonadorner.xaml'.

and

Method not found:Infragistics.Windows.Themes.ResourceSetLocator Infragistics.Windows.Themes.EditorsResourceSet'1.get_Location()

The rest of the view is rendered, but the designer cannot render any Infragistics controls.

Any suggestions you have to help me resolve these issues would be appreciated. All of the projects rendered views correctly when the projects were on .NET 4

are these messages indicating that some helper design.dll or design.VS2012.dll is missing or corrupted?

Thanks, Andrew. Attached Modules contents in zipped .xlsx file.

Just to clarify and make sure I'm giving you what you're asking for, I got this at runtime after launching the app in the debugger. The application runs properly. It's the VS and Blend designer that's throwing the exceptions and not rendering.

I'm looking for what is in the Debug->Windows->Modules of the VS instance that you attached to Blend or the instance of VS that has the designer that is demonstrating the problem so I can see what assemblies are being used at design time. Design assemblies won't be loaded at runtime and also VS uses additional information (e.g. AssemblyFolders entries in the resx) to locate assemblies that could be different than what is happening at runtime.

Thanks, Andrew. I had a feeling I wasn't giving you the right thing. This one is from the second instance of VS and has two sheets, the first is modules from attached VS and the second is from attached Blend.

Thanks for your patience on this one. From the Blend list it definitely seems like multiple copies of the assemblies are being loaded. The question is why. Could I ask you to try attaching to XDesProc.exe (the "Microsoft Visual Studio XAML UI Designer") since VS won't be loading the assemblies into its process? Thx

I've got nothing but patience now. Thanks for your help.

I have attached to XDesProc and added that Module output to the spreadsheet attached.

Definitely seeing 2-3 instances of many but not all IG assemblies. They all seem to be the version-free assemblies and the correct version 12.2.20122.2089.

It seems that where some are referenced 3 times, the VS2012.dll verison is only referenced twice. I don't know if that is a tell or not.

yes, thank you all for your help.

Hello,

If I read your last update correctly you have resolved the designer issue and this is now working correctly.

Please let us know if we can be of any further assistance.

ugh, apparently somewhere along the line some references to our own assemblies got corrupted and/or there was a custom converter throwing an exception that never appeared in any of the stack traces we were looking at and didn't happen before the switch to .NET4.5... Why IG was blowing up the designer because of these.. I will probably never know.

Thank you for YOUR patience.

Interestingly there are also multiple instances of your assemblies in memory which I'm guessing is why there are multiple instances of our assemblies. So for example I see that 2 Asset.Resources assemblies are loaded - which while they have the same version number seem to have different dates (1 from 3/15 and another from 3/18). In other cases (e.g. MVVM.Markup) I see 3 copies of your assemblies loaded. I suspect if you correct that then the designer issue will go away.