With a solution structure, where every plugin has an own visual studio project its very hard to publish multiple plugins at once. (e.g. when a method in the base class has been changed)
Please support multi selection of C# projects, like on webresources by "Right click" > "CRM" > "Build and publish".

Thanks,

...so that when I commit it to source control, I can use standard diff tools to review changes

I have a project with the namespace "com.crengland.services.Web.CrmApi.Xrm" but XrmToolkit always capitalizes the first character of the namespace when generating proxy classes. I have to manually replace the namespace in generated proxy classes to fix this issue.

I tried using the option to auto-publish on Save, but I actually save a lot (because VS crashes hurt) and only want to incur the publish delay when things are in a particularly good state. In other development this is when I do a Build, and I do build my CRM client scripts (Typescript ftw), so my ideal would be for a build to publish files changed since the previous build. Slightly less ideal but still good: publish all of the project's checked-out files. Worst case, manually flagging files to publish works, too.

Would it be possible to add StringLengthAttributes to string properties of auto generated classes? The length should reflect the maximum length of the CRM field.

https://msdn.microsoft.com/en-us/library/system.componentmodel.dataannotations.stringlengthattribute(v=vs.95).aspx

It would help much, because right now setting a value that is to long for CRM does not raise an exception but just leaves to field empty in CRM (nothing is saved).

Right now when you register a plugin step the name is blank. I suggest that name to be default to something.

for example if the Plugin is 'MyPlugin' and the Message is 'Update' and the entity is 'Opportunity' then default the plugin name to 'MyPlugin - Update - Opportunity'

A configurable default would be nicer (as I'm sure there are a lot of different naming standards out there)

I would like to see a feature comparison of your product vs other tools/SDK options available

I know there is a ton of overlap between the CRM Solution Manager and the CRM Developer Toolkit.

If I develop a solution that has a Packaging project from the developer toolkit, I can ensure other CRM developer can deploy customizations. The only problem is that I can't right click an Web Resource in the Packaging project and quickly publish to CRM using the CRM Solution Manager.

Grid-like editor to allow bulk editing of attributes. Also allow editing all aspects of individual attributes. Allow pushing all changes to CRM at one time after all edits have been made.

CRM Chart Editor (GUI) that would allow you to edit all the properties of a chart without manually editing the XML.