As a developer, I'm using at least two laptops for developing software. I would love to have an option to transport my license when I'm developing. Now, I need tot think about activating the license on a virtual machine and move the virtual machine from one to another.

Add support for solution packager to extract files into the project after a publish to CRM - make it optional during a publish. Currently this would need to be done via creating build scripts and updating the targets. It would be nice if this was built in to CRM Solution Manager and could be controlled by the UI.

Provide the ability to add javascript calls to crm forms directly from visual studio.

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.

We sometimes have multiple developers working on same webresources. Ability to download the latest from CRM before start of edit and to compare server version with the original downloaded version before publish will allow us to know if some one else have make script changes while I am working on a file. This will prevent developers overwriting each others changes. Comparing local and server files manually each time you modify is not productive.

Support PCF development which currently requires a lot of additional scripting to build/publish into CDS/XRM. This looks set to replace replace custom web resources so would be an appropriate progression for the product.

May be worth considering a change of name to CDS or PowerApps Toolkit?

Should be able to call an API to publish a crm asset or plugin/workflow assembly to the CRM organization taking into account all the XrmToolkit configuration information.

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.

It would be nice if the the ExtensionMethods or some other feature in the BaseProxyClass would return an option set value via text based on the [Description] in the enum. Perhaps this already exists but, I did not see it in the documentation.

Something like
OptionSetValue ov = new OptionSetValue(ExtensionMethods.GetOptionSetValue("Active"));

A light versjon that only support Javascipt/TS with Vistual Studio Code - generating intel. fiels for Js/TS and with publish to CRM funksjon.

• more if you like :)

It would be nice if XrmToolkit supported the concept of versioning workflow assemblies in Dynamics. If you increment the major or minor build number of a workflow assembly, you can register a new copy of that workflow assembly with that new version and then switch over the workflows to the new version at your leisure. Here's an article on how it works: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/workflow/update-custom-workflow-activity-using-assembly-versioning

I would like the possibility to register a plugin as data provider. Data providers are used in virtual entities.

Add Entity Metadata Repository
Instead of hardcoded metadata information inside proxy classes, it would be awesome to provide this information inside a repository.

Something like:

var entityRepositoryItem = MetadataRepository.GetEntity(param entity);
var attributeItem = entityRepositoryItem.GetAttribute(string name);

Console.WriteLine(attributeItem.Max Length);
Console.WriteLine(attributeItem.Logicalname);
...

It would be great to be able to select Actions and Views to automatically generate their own proxy classes. For Actions, it would generate a strongly-typed proxy that accepted the typed parameters and returned the output parameters. For Views, it would generate a proxy that lets you quickly get results from System Views on each entity by just querying that View proxy. This way you could quickly model queries in Dynamics in the Advanced Find and then easily reference them in code.

Create Javascript/Typescript classes containing entity metadata and lookup values that can be added to a Form and referenced for intellisense.

We would like to have crm data model to be kept in TFS including entities and fields. We want to track/version any changes on the data model, associate these changes with proper workitem in source control.

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.