Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
250
Cannot resolve dependency to assembly 'InfragisticsWPF4.v11.1
posted

Hi,

I have a WPF application that is using infragistics.

It works fine on the developers machine since it has infragistics installed on our machines.

However, while trying to build the application on a machine that does not have infragistics installed on it. The build fails with the below error.

Unknown build error, 'Cannot resolve dependency to assembly 'InfragisticsWPF4.v11.1, Version=11.1.20111.1002, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event. 

The application just uses XamComboEditor in its WPF form and has infragistics referenced in the page as follows:

 xmlns:igEditors="clr-namespace:Infragistics.Windows.Editors;assembly=InfragisticsWPF4.Editors.v11.1"

The project containing the form has reference to "InfragisticsWPF4.v11.1.dll" added from a commonlib folder not GAC.

The common lib folder also has reference to the below files:

Infragistics.Windows.Extensions.dll

InfragisticsWPF4.Controls.Editors.XamCalendar.v11.1.dll

InfragisticsWPF4.Controls.Schedules.v11.1.dll

InfragisticsWPF4.DataManager.v11.1.dll

InfragisticsWPF4.DataPresenter.ExcelExporter.v11.1.dll

InfragisticsWPF4.DataPresenter.v11.1.dll

InfragisticsWPF4.DockManager.v11.1.dll

InfragisticsWPF4.Editors.v11.1.dll

InfragisticsWPF4.Ribbon.v11.1.dll

InfragisticsWPF4.v11.1.dll

Not sure why the project does not build and also not able . Please help....
           

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

Unknown build error, 'Cannot resolve dependency to assembly 'InfragisticsWPF4.v11.1, Version=11.1.20111.1002, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event.