This is a follow up on my earlier project CRM Customization Manager, CRM Configuration Manager is a Windows application to create an Export / Import selection that can later be exported as a command prompt string for later use, or execute directly inside the application. The main features of CRM Configuration Manager are,

• Easy access to the features of CRM Customization Manager
• Possible to select a CRM server as destination, allowing one click export and import.
• Create advance export/import selections for later use inside scripts / installations

This release includes CRM Customization Manager v2.0 that contains fixes and few new features,

• JavaScript Export/Import, This allows you to extract JavaScript to a local folder, where you can work in a proper script editor, and later import them back. You can also create new javascripts in the same folder, just follow the name convention and they will also be imported to the correct entity / event.
• Zip support, Now all features works with zipped customizations
• Include Related Entities, This features will automatically include related entities to the selected entities, so their relationships are exported and can be reviewed for conflicts. This is recommended during the development process when relationships may change.
• Publish Workflows, Publish operation now also publishes workflows

Previous key features...

I’m wondering, is there any interest in creating your own operations? That is, using a Plug-in model to add custom arguments to the application that will call your code before/after execution. If you find the application useful, please donate to keep the development alive :)   CcmSetup1.01.exe (907,26 kb) Update: v1.01 Import filename fix   Happy Customizing!

During my time with Microsoft CRM 4 I’ve found some limitations of the import & export process of customizations, which led to the curiosity if one could fix those with a custom application. Thanks to the open architecture of Microsoft CRM with Web Services and Xml for customization management it was pretty easy to create a small application to improve the import and export process of customizations.

Here follows the main features of CrmCustomizeManager.

• Console Application, Making it possible to import and export inside nant, msbuild or bat scripts, for example to export the customization each night and “check in” to a source code repository, enabling version control of the customizations. Also to import customizations directly from a MSI installation.
• Export Only Modifications, You can export a “clean” customization xml in the beginning of a project and save it in the application folder as “CleanCustomization.xml”, the application will compare the current state and only export the entities that are modified or added.
• Remove Deleted Attributes, This feature only applies when importing a customization. When this operation is selected one will be prompted with all attributes that has been removed in the new customization, given the possibility to remove them from the CRM instance.
• Changes Attribute data type, When changing an attributes data type and then trying to import it to a CRM instance that still contains the old attribute would normally generate an error. This is now handled and the data inside the old attribute will be converted to the new data type (when possible and logical)
• Publish, You can publish the customizations, can also be used at it’s own, for example assigning it to a system wide hotkey for fast access.
• Node & Entity Selection, you can select what nodes and entities to import and export. For example only export ISV Config or the Site Map. Possible items to select,
  
  

  Entities	Workflows	Roles	ISV Config
  Sitemap	Templates	Calendar Settings	General Settings
  Email Settings	Marketing Settings	Outlook Synchronization	AutoNumbering Settings
  And more…

Get Latest version.

As WM-data just became Logica here in Sweden we have changed our laptops and entered a new domain, with that there came new policies and rules. One of them is the enforcement of using the User Account Control (UAC) on all Vista machines, which is pumped out each time logging into the Logica domain.

This presented a problem that needed to be solved, how to be able to work inside the domain and still be effective? Solution: A NT Service that continuously turns off the UAC.

Here is an install for the small service that just checks so the UAC is not turned on when the computer is shutting down.

DisUacSetup.msi (392,00 kb)

There is often that one need to get an assembly’s full name, while one can do it quite simply in C# by instancing the assembly and calling GetName(), but when setting up applications outside the development environment, You can use SN.exe to retrieve the PublicKeyToken using the -T parameter, but still it would be nice to get the whole Assembly Name, so here is a small command prompt app that does the job.

Example of an Assembly full name:
"GetAsmName, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=efc52db0448864e8"

Download the compiled application:
GetAsmName.zip (2,83 KB)

Download the source code:
GetAsmName-src.zip (2,51 KB)