We are using the UltraGrid in a win forms application that is distributed through a UNC path.
When we publish the application, and the user tries to run it we get the error: The application requires that assembly Infragistics2.Win.Misc.v12.1 version 12.1.20.21.2071 be installed in the Global Assembly Cache (GAC) first.
Because this is a corporate application, running a seperate instal on everyones PC that might someday get this application is unreasonable. How do I get the library to install from the publish wizard.
Thank you
Andre
Hello Andre,
Could you please take a look at the following link and see if it helps:
http://help.infragistics.com/Help/NetAdvantage/WinForms/2012.2/CLR4.0/html/Win_Using_Global_Assembly_Cache_GAC_Deployment.html.
Please do not hesitate to contact me if you need any additional assistance.
Maybe I am not understanding, this is an application that has already been deployed. We are making an update to it and adding the first of the Infragistics controls (UltraGrid).
To deploy updates to the application we use the visual studio publish option to a shared UNC path. So when the user opens the application it looks for updates and auto installs the new version of the application. If at all possible I would like to continue to use this methodology to deploy the update with the new controls.
Think I figured it out, I havent had an opportunity to test it yet, however I noticed the copy local property on the infragistics dlls in my project were set to false. We will try setting these to true and see if this works.
Good Morning;
Tried the above suggestion and it still does not work...
Dont know if this makes any difference:
The user community is still on WinXp .Net version 3.5.
This is our first release of the infragistics controlls in a pre-existing application.
We inhanced one section of the application by adding the ultra grid to it for the drill down capabilities.
The app and updates are distributed to the user community as described in a previous post.
Could you please try to set the Copy Local to 'true', then build the application and try the release on a different machine? Also, depending on the version you have previously used, you might want to try to set the specific version of the assemblies to 'false'.
Please let me know if these suggestions do not work for you.
Didnt work...
I might have misunderstood you. Did you have the time to try this out?