As detailed in\u00a0Configuring Visual Studio to use ConfigMgr Assemblies<\/a>\u00a0is it not permitted to take the assemblies from the Microsoft Configuration Manager console and bundle them with your application if distributing outside your company. One possible solution is to configure your application so that it will automatically load the required assemblies from a local installation of the ConfigMgr console. This also has some advantages over bundling the assemblies with your application:<\/p>\n\n\n\n MSDN description of AppDomain.AssemblyResolve<\/a>.<\/p>\n\n\n\n When you run your ConfigMgr SDK based application without copying the relevant assemblies into the same folder as your executable you will get an exception when the missing assemblies attempt to load. The\u00a0AssemblyResolve<\/strong> event is triggered whenever an assembly load is attempted and cannot be found. The event also provides the opportunity to load the requested assemblies from another location instead of just failing. The example code below shows how to use AssemblyResolve to allow an application to load the ConfigMgr SDK assemblies directly from wherever it is installed. The way it works is:<\/p>\n\n\n\n The examples on this page can be downloaded from the GitHub repo<\/a>:<\/p>\n\n\n\n\n
AssemblyResolve Event<\/h2>\n\n\n\n
\n
\n
Examples and Downloads<\/h2>\n\n\n\n