When you want to create an interface for a class you can use the helper "extract interface" on the class definition. This does not copy the leading comments used with tools such as Swagger; i.e. the comment block created with the three forward slashes ///

For example:
/// <summary>
/// Configuration manager
/// </summary>
protected readonly IConfigurationKeyManager _configurationKeyManager;

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

Like native SDK plug in registration tool that allows registering for service end point and web hook; it would be nice to have the similar setup within XrmToolkit for Visual studio

Generate POCO or DTO early binding classes which do not have any references to the SDK. Any 1:n relationships are created as Property LIST<MyEntity>. Any Optionsets are generated as enums in separate file so there are no duplicates (i.e. status and statusReason ). The ability for these POCO classes to then generate an XSD without error. At run time AutoMapper could map from POCO to ProxyClasses

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

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.

Currently SVG files don't have the xrmtoolkit menu to add as webresources to CRM. For Unified Interface, the entity icon only supports svg files.

Connecting to online instances of D365 can be a little slow so waiting for this step to complete before compiling and then uploading assembly/code is time consuming. I suggesting starting the connection attempt and building the project (plugin) at the same time, once they are both complete, upload. This will save 10-15 seconds per publish which happens a ton of times over the course of a work day.

Hi Team,
I have updated to the latest version of xrmtoolkit from version 5.1.0.0
Publishing loader message pop-up is shifted to the right of the screen instead of center of screen. Although minor but could be corrected in the upcoming versions.
Thanks,
Anubhav

No need to type in the current credentials.. Use the credentials of the computer who is already logged in.

Ensure correct DateTime operations. Now Dynamics CRM supports two mode of working with dateTime attributes.
With or without UTC conversion.

It would be nice if generated proxy will take it into consideration.

It would be great if I could Execute a CalculateRollupRequest if the field is a rollup field. Currently I have to extend the proxy class and so I could call the function. It could work similar to how lookup fields can RetrieveProxy<T> i.e. contactRecord.new_rollupfield.Rollup(OrganizationService) would execute the function.

Currently, there is no easy way to update all the existing proxy classes (with their respective option sets). Right now I have to select all the class files in the solution explorer, right click, then click 'CRM -> Regenerate...'

Maybe there could be an option group called 'Proxy Classes' in the context menu for the project where you can either add proxy classes or regenerate all

Currently it is not possible to adapt the name of proxy classes during generation.
Please provide an extension to provide custom names for proxy classes and properties.

Some generated names does not fit our naming conventions. For example special chars in german ("ß", "ä","ö" ...) or properties which will start in lower case or underscores in names.

It would be awesome to have the possibility to extend the INamingService implentation of XrmToolKit.

Straight forward instead of manually having to deactivate all of these workflows. Maybe there's a way to remotely deactivate them publish and reactivate them.

The current intellisense feature for picklist attribute will generate something like this.
Xrm.Page.getAttribute("new_dropdownfield").setValue(912210002);

The value 912210002 makes it less readable for future maintenance. A suggestion is to rather do the following.
Xrm.Page.getAttribute("new_dropdownfield").setValue(PicklistA_Option1);

Define PicklistA_Option1 in the same file automatically or in an enumerations.js file that can be include.
As part of the Web Resource Minification remove this reference.

Add the ability to easily create/test plugins and other code. Something similar to https://github.com/daryllabar/XrmUnitTest or https://dynamicsvalue.com/home

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);
...