GP Add in raised exception
After applying GP2010 SP3 my GP add in started raising an exception on windows forms that used Entity Framework (EF). The error reported was
System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.Lync.Utilities, Version=220.127.116.11…"
…but I don’t use Lync…
But I know Dynamics GP does have integration with Lync. It had me puzzled for a while as I wondered why my form was causing this assembly to be required and attempting to load it. Eventually the penny dropped after studying the stack trace. The stack trace was mentioning about System.Reflection and System.Data.Metadata.Edm.DefaultAssemblyResolver.GetAllDiscoverableAssemblies(). I guessed there was some dynamic loading going on and got mislead reading up on MEF, thinking perhaps GP implemented it under the covers. I then hit lucky on Google with Craig Suntz’s blog that explained my issue. It is down to Entity Framework connection strings.
Entity Framework Connection Strings
In my EF connection string I was building my connection string like this from the SQL connection string.
Dim entityBuilder As New EntityClient.EntityConnectionStringBuilder() entityBuilder.Provider = "System.Data.SqlClient" entityBuilder.ProviderConnectionString = sqlBuilder.ToString entityBuilder.Metadata = _ "res://*/Inventory.DAL.InventoryModel.csdl|res://*/Inventory.DAL.InventoryModel.ssdl|res://*/Inventory.DAL.InventoryModel.msl" Return entityBuilder.ToString()
Notice the “res://*” bit, the Metadata reference. The files are embedded into the assembly as resources and this Metadata property is the pointer to them. Specifying * instructs a reflective search through all assemblies (even if not yet loaded) that are referenced by the application, looking for the resources.
I guess that as Lync SDK was referenced by GP 2010 my attempt to create the connection was causing the Lync assembly to be loaded in order to check it for the meta file resource. The consequence of this is that we got an application exception as that assembly does not exist on the machines in our organisation.
The solution is to explicitly specify the assembly name that holds the resource as shown in the next code snippet. Making this exact reference is more efficient by it preventing unnecessary loading of assemblies and thus preventing the error . This is interesting as I’d experienced a performance hit on these windows vs ones not using EF. I assume some of that was down to this attempt to load all the assemblies.
Dim entityBuilder As New EntityClient.EntityConnectionStringBuilder() entityBuilder.Provider = "System.Data.SqlClient" entityBuilder.ProviderConnectionString = sqlBuilder.ToString entityBuilder.Metadata = "res://GP AddIn GUI Library/Inventory.DAL.InventoryModel.csdl|res://GP AddIn GUI Library/Inventory.DAL.InventoryModel.ssdl|res://GP AddIn GUI Library/Inventory.DAL.InventoryModel.msl" Return entityBuilder.ToString()
After recompiling and then deploying to the GP add in folder, my problem went away. I suspect if I spent some more time on this that the Lync assemblies are stuffed into the Global Assembly Cache by the SP3 installer, as we do copy deployments to the client machines we will be missing those assemblies. Hence not everyone may suffer this issue when using add ins if you run the full installer. However this guesswork needs researching and I’ve not got time right now to investigate.
About MEF (Microsoft Extensibility Framework)
In my Google search of the issue, it looks like you can get issues around MEF with dynamically loading assemblies, so for those of you finding this post through Google and not using Dynamics GP, then that might be a term to try on Google for a solution in your scenario.
Below is the original error
Raised by by Add-in for those still with an interest…