General
51 results found
-
Automatically validate strong name
Sometimes when using ILMerge, the strong name is not valid when the dll is created. It would be a nice feature to validate the strong name first before uploading. And if the strong name is not valid, automatically resign the dll to fix the issue.
1.) Run sn -vf *.dll
2.) Confirm that the dll is either a delay or test signed
3.) Run sn -R *.dll *.snk
4.) Confirm that the dll is now valid1 vote -
New versjon for Vistual Studio Code (Js/Ts functions + publish)
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 :)
14 votes -
Add summary comments to generated public/protected code
In our environment warnings are generated during deployment if any public or protected class, method, or property has no summary and param comments. We use Swagger which utilizes these comments.
For Example:
/// <summary>
/// Gets the error string.
/// </summary>
/// <returns>The error string.</returns>
/// <param name="attributeName">Attribute name.</param>
/// <param name="defaultErrorType">Default error type.</param>
protected override string GetErrorString(string attributeName, BaseProxyClass.eErrorType defaultErrorType)
{
if (_errorStrings.ContainsKey(attributeName))
{
return _errorStrings[attributeName];
}
return defaultErrorType == BaseProxyClass.eErrorType.Text ? TextError : NumberError;
}3 votes -
Support versioning of custom workflow assemblies
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
14 votes -
Ability to register plugin as data provider
I would like the possibility to register a plugin as data provider. Data providers are used in virtual entities.
8 votes -
Add Actions and Views to generated proxy classes
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.
6 votesV7 was just released which includes support for generating proxy classes for ‘Actions’. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Ensure correct DateTime operations
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.
6 votes -
Support Plugin Profiler
I know the ToolKit uses the Plugin Reg Tool to do most of the work, but incorporated in Visual Studio. One feature of the Plugin Registration Tool that isn't with the ToolKit is using the Plugin Profiler. I assume you know what it is, but just in case, it's a solution for CRM that comes with the sDK/Plugin Registration Tool (PRT), from the PRT you can install the solution into your CRM solution, and once installed you can replay plugin messages, workflows, and then by attaching visual studio to it, you can debug. Seems like this would be a great…
30 votes -
Add unit testing mock ability
Add the ability to easily create/test plugins and other code. Something similar to https://github.com/daryllabar/XrmUnitTest or https://dynamicsvalue.com/home
4 votes -
Compare webresouces - advise stale copy before publish
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.
18 votes -
14 votes
-
Support deploying to CRM by providing an API that would support using from a command line or from a .Net app.
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.
11 votesThe initial version of this has been released in v5. It supports merging (ILMerge) of plugin assemblies and publishing them to CRM. A future release will include the ability to deploy other assets, ie web resources etc.
-
Remember 'DO NOT LINK' option and allow link option/target to be changed
I use 3rd party libraries with intellisense files and need to be able to permanently mark these as not linked to CRM.
In other instances I need to be able to correct the link eg. created a new instance instead of linking to an existing instance in CRM or vice versa.
0 votes -
Add Entity Metadata and Lookup values as Javascript Class
Create Javascript/Typescript classes containing entity metadata and lookup values that can be added to a Form and referenced for intellisense.
6 votes -
Support for solution packager to extract files into the project
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.
78 votes -
add javascript calls to crm forms
Provide the ability to add javascript calls to crm forms directly from visual studio.
43 votes -
CRM Chart Editor
CRM Chart Editor (GUI) that would allow you to edit all the properties of a chart without manually editing the XML.
18 votes -
extract interface from class with comments
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;3 votes -
Generate POCO or DTO early binding classes
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
3 votes -
Execute publish and connection in parallel
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.
4 votes
- Don't see your idea?