XrmToolkit v4 was released today. For more information see https://xrmtoolkit.com

Hi Peter,

Thanks for the detailed explanation. We will certainly take this into account when proceeding with implementing this feature. Thanks again!

Hey, these are GREAT news! :)

Assumptions which proved to be sensible based on our daily work on MSCRM Solutions using CRMSM:

## Webresource names

The current default logic for constructing webresource names (Publisher prefix + relative filepath beginning on CRM solution Project root) should be used. Display Name should equal filename.

## Create new or update existing webresource

This feature should not only create webresources when they do not exist yet, it should also check whether a webresource of the given type (determined by file Extension) and an identical Name exists and, if yes, update it. It should be possible to selected several project items and have an "CRM (myOrg)" context menu item that in turn contains a "Publish selected files to CRM" menu command, which simply publishes them - regardless if the actual publishing operations involve updates or creations.

After the publishing process, all selected project items should be linked to their according CRM webresource. That way, we can add several new webresources at once. Finally, some sort of tooltip/bubble should be displayd to the user that tells him what exactly was done. Example: "7 webresources were selected to be published. (5 Updated / 2 Created)". When an error/conflicht occured a simple dialog should be shown, with a list of all webresource items that were part of the previous publishing process along with some brief informational error message (like "webresource XYZ could not be created since a candidate with this name does already exist")). However, CRMSM should not abort the whole publishing process when a single operation failed, just tell the user at the end which ones failed.

There should be a checkbox "Automatically find & link to existing webresources with same schema name" in the preferences that lets the user configure tihs behaviour. When checked, the behaviour described above should apply. When not checked, only creates are performed. When there are already webresources with an identical name, an error should be displayed.

## Conflicts

When a (possible) duplicate webresource is found, it should be skipped and CRMSM should continue with the next webresource. Error messages should be displayed to the user as explained above.