General
56 results found
-
Support Visual Studio 2017
The current plugin doesn't work with Visual Studio 2017 RC. As we're planning to move to VS 2017 on release, and have already started evaluating it, it would be nice to have VS 2017 support in XrmToolkit.
183 votesV5 has been officially released which includes support for Visual Studio 2017 and Dynamics 365. For more information see the website: https://xrmtoolkit.com/WhatsNew/WhatsNewInV5
Thanks everyone for your patience and feedback during the beta testing!
-
Acces to XrmToolkit on multiple instances(2) with one license.
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.
85 votesIf you would like to test out the preview of v8, you can use one of the links here:
- https://xrmtoolkit.com/downloads/xrmtoolkit_8_0_1_0.vsix (VS2017/19)
- https://xrmtoolkit.com/downloads/xrmtoolkit.x64_8_0_1_0.vsix (VS2022)
Please note that there is not any documentation yet for any new features. You can only request a trial license at this point after installing the new version. However, the trial duration is for 120 days currently until v8 is released. Please submit any issues via the regular support options and not directly to this suggestion.
-
Provide NamingServiceExtension for proxy classes
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.
67 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Support VS2015 Shared Projects
Be able to add shared files (such as proxy classes) into a VS2015 Shared Project, so that they can be managed in one place, without having to resort to building a DLL and using ILMerge
45 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Support Visual Studio 2022
Visual Studio 2022 is coming soon and currently available as Preview 2.1. Is XRMToolkit going to be supported?
40 votesIf you would like to test out the preview of v8, you can use one of the links here:
- https://xrmtoolkit.com/downloads/xrmtoolkit_8_0_1_0.vsix (VS2017/19)
- https://xrmtoolkit.com/downloads/xrmtoolkit.x64_8_0_1_0.vsix (VS2022)
Please note that there is not any documentation yet for any new features. You can only request a trial license at this point after installing the new version. However, the trial duration is for 120 days currently until v8 is released. Please submit any issues via the regular support options and not directly to this suggestion.
-
Support for VS2019
VS 2019
20 votesYou can try out the beta of V6 by installing the following: https://xrmtoolkit.com/downloads/xrmtoolkit_6_0_0_11.vsix
To learn about what’s new see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV6
Please report any issues to support@xrmtoolkit.com
-
TypeScript support
Add the ability to link a TypeScript file to CRM. The JavaScript output of the TypeScript is what actually will get published to CRM.
19 votesThis feature was released as part of v3.
-
Support multi select of C# projects to publish all at once
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,
19 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Connecting to CRM Online instances where authentication is MFA.
If the CRM instance implements MFA, the XRMToolkit fails to connect to the CRM Instance. Need to have different Authentication types enabled for XRMToolkit.
18 votesYou can try out the beta of V6 by installing the following: https://xrmtoolkit.com/downloads/xrmtoolkit_6_0_0_11.vsix
To learn about what’s new see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV6
Please report any issues to support@xrmtoolkit.com
-
Support for Powerapps Component Framework (PCF Control)
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?
18 votes -
Support for MSCRM 2015
Please add support for MSCRM 2015 asap.
Thank you
18 votesOfficial support for CRM 2015 was added in v3.3 which was just released.
-
Add support for Dynamics 365/DataVerse portal assets
Please add the ability to modify portal assets similar to the way that you can download/update/publish web resources.
17 votesAn initial implementation has been completed and you can test this out in the following build: https://xrmtoolkit.com/downloads/xrmtoolkit_7_0_4_5.vsix.
You can add a new portal project from the solution level: ‘D365 → Add New Project → New project from Portal Website’.
Please reach out to support if you find any issues.
-
TypeScript intellisense
Add intellisense for TypeScript similar to what is provided for JavaScript
16 votesThis feature was released as part of v3.
-
Support new .net Core Client
(https://www.nuget.org/packages/Microsoft.Powerplatform.Cds.Client.Dynamics)
Should require minimal change - new compile target. Client only, leave aside workflow & plugins etc.
15 votesXrmToolkit will now not try to install the other SDK NuGet package if it detects that the newer SDK is already installed. Perhaps when the new SDK is officially released we can provide the option to choose which package to install by default (when nothing is installed yet).
-
Easily update all proxy classes
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
14 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Ensure IntelliSense Fully Works Alongside ReSharper
The attribute intellisense didn't seem to work unless I suspended ReSharper. (using ReSharper 2016.2.2).
13 votesYou can try out the beta of V6 by installing the following: https://xrmtoolkit.com/downloads/xrmtoolkit_6_0_0_11.vsix
To learn about what’s new see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV6
Please report any issues to support@xrmtoolkit.com
-
Refresh all items in Visual Studio solution that are linked to web resources in CRM
Similar to the TFS 'Get Latest Version' option, there should be a way to get all the currently published files from CRM and download them to your Visual Studio solution for any files that are linked to CRM.
13 votesThis feature was released as part of v3.
-
Add Support for Source Control - Store Plugin Config and CRM Links as a File in the Project
When working in large teams on large projects, one might not know how each plugin step should be configured. Also, linking files that are newly downloaded from TFS is tedious.
This metadata should be stored in a project file and shared with the team via Source Control VSTS (TFS) or Git.
11 votesThis is already supported. See the documentation here: https://xrmtoolkit.com/General/XrmToolkitFiles
-
Allow relative Reference Directories for ILMerge
When using ILMerge for project, when Override CRM Reference Directory is used, it uses absolute directory locations and thus every developer must add their own reference directories.
Would be nice if we could use relative paths to, for example, reference dlls from nuget packages.
11 votesYou can try out the beta of V6 by installing the following: https://xrmtoolkit.com/downloads/xrmtoolkit_6_0_0_11.vsix
To learn about what’s new see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV6
Please report any issues to support@xrmtoolkit.com
-
Show custom actions in the "Message Event" list when creating new plugins
Currently, only system messages are available when creating/registering new plugins (e.g. Create, Save, Update, etc.). Users should be able to select from active custom actions that have already been created as well. Microsoft's plugin registration tool currently supports this.
11 votesThis should already be the case… but you may need to close and re-open Visual Studio in some instances. This will be improved in v7 such that they will show up immediately after creating new ones in CRM.
- Don't see your idea?