• Initial support for Arm64 (Beta)
• Automatically add the necessary elements to the project file to support Dependent Assemblies
• Added the ability to change the Gulp timeout in the Global Settings UI.
• Added the ability to renew a license registration from the 'About' form.

• Fixed an issue with invalid message names being created during the proxy generation.
• Fixed an issue with the Gulp service crashing Visual Studio.

• Added the ability to turn off the use of existing proxy names when regenerating proxies. You can selectively determine which object types will use existing names and which will use the proxy naming method and overwrite any of the current names.
• Added the SdkMessageConfigs and SdkMessageFilterConfigs to the PluginAssemblyConfig data.
• You can now compare CustomAPI config data to what is deployed in D365.
• Added support for registering/modifying webhooks and service endpoints along with their accompanying steps in the plugin registration tool.
• Updated the CLI to allow registering a license without supplying a username and password.

• Fixed an issue where an error was thrown due connecting to a D365 version that does not support CustomAPI's.
• Fixed an issue where the current organization version would be lost when switching branches causing an 'Object Reference Not Set to an Instance of an Object' error.
• A plugin assembly project is no longer requred to be signed if deploying as a NuGet package.
• Fixed an issue when using the CrmSvcUtil proxy generation method that would remove valid enums and properties from the CrmContext when regenerating them or when adding a new proxy class to the project.
• Fixed an issue when trying to deploy a new plugin assembly that uses the 'NuGet' merge type and the project has never been built.
• Fixed an issue when trying to download report files (.rdl) from D365 and adding them to the project.
• Fixes an issue with the 'Copy links from another Organization' process.
• Fixed an issue where publishing all customizations would timeout.

• Improved menu text for some dynamically generated menu items.
• Added the 'Form Type' to the display of the forms when selecting TypeScript intellisense files to generate.
• Make the 'Execute' method of the PluginBase class virtual to allow inheritors to override it.
• Allowed the Reports project build to fail and still be able to publish as report.
• Ignore serializing/deserializing the OrganizationVersion from the xrm2 file.

• Fixed an issue where attempting to auto-install ILMerge was throwing an error.
• Fixed an issue where you would be logged out and prompted to log back into and organization after changes to the .xrm2 file.
• Fixed some issues with naming conflicts when using the CrmSvcUtil method of generation.
• Fixed an issue with the 'openQuickCreate' Javascript method signature.
• Fixed an issue where ILMerge was not found as a package if it was installed with a LowerCase for the name.
• Fixed an issue that was causing an error to appear in the logs, even though it was not a critical error.

• Fixed the crash error: The type initializer for 'DevExpress.Xpf.Utils.Themes.WindowTracker' threw an exception. ---> System.InvalidCastException: Unable to cast object of type 'DevExpress.Xpf.Core.StirlitzHashTable' to type 'System.Collections.Generic.Dictionary`2[System.Int32,MS.Internal.Automation.EventMap+EventInfo]'

• Added the ability to specify the 'Prompt to login' when using the 'OAuth/MFA' authentication type.

• Fixed an issue in the MonoHelper where it would throw an error if v6.x had not been previously installed.
• Fixed an issue where enum proxy classes were being generated multiple times during a single operation.
• Fixed an issue where an error would be thrown if no 'Current Solution' was set and you tried to add a new webresource.
• Fixed an issue where the filtering attributes were not displaying correctly.
• Fixed an error while generating proxy classes for custom actions when the parameter type was a 'BusinessEntityCollection'.

• Updated some methods and properties in the 'BaseProxyClass' to be 'Protected' so that inheritors could access them.
• Updated some items in the Xrm.d.ts that were not typed correctly.
• Added back in the overloaded methods for 'Relate' and 'UnRelate' entities to retain backwards compatibility with proxy classes that have not been generated yet with v7.
• Created a new NuGet package: XrmToolkit.Linq.Core which utilizes the updated CRM SDK's which are compatible with .Net Core and .Net 5+.

• Fixed an issue where the 'async' JavaScript keyword was not being handled properly by the prettify logic.
• Fixed an issue causing Visual Studio to crash if it could not checkout the .xrm2 file in order to update it.
• Fixed an issue where TypeScript intellisense was missing controls from the header and footer of the form.
• Fixed an issue where changes to global optionsets were not being detected and so proxy enum classes were not able to be regenerated properly.
• Fixed an issue where the CLI was unable to publish a project that used ILMerge.
• Fixed an issue where the 'Name' property of a FileAttributeMetadata attribute was being duplicated during proxy generation.
• Fixed an issue preventing you from linking a project or solution in some instances.

• When editing the project properties of a Plugin assembly, the updates are pushed to Dynamics 365 only when properties have changed that affect the registration in Dynamics 365.
• Allow the ability by project to turn off the automatic deletion of links when the files do not exist on disk.
• The 'FileSystemWatcher' is turned off during build operations which provides greater performance and stability to Visual Studio.
• Update the CRM SDK references to the latest (9.0.2.42).

• Fixed an issue where multi-select optionset columns were not available in the list of filtering columns when registering a plugin step or image.
• Fixed an issue where the relative path was being calculated incorrectly when setting the output file name of a web resource.
• Fixed an issue where updates to plugin assemblies would fail for certain organizations.
• Fixed an issue where you could not connect to a new organization in the CRM17 region.

• Added new overloaded methods to the 'IProxyNamingService that allows the ability to specify a custom proxy base class for your proxy files.
• Updated the BasePluginTemplate to make some properties 'virtual'.
• Content from Dynamics is no longer automatically prettified when comparing to local file.
• If an item has a Gulp task specified, XrmToolkit will now execute this before doing a 'Compart to Local'.
• Added a new option to the Global Settings to allow turning off the prompt to remove links when a project is removed/unloaded from the solution.
• Typescript intellisense: WebApi.retrieveMultipleRecords now returns a 'RetrieveMultipleResponse' type.
• TypeScript intellisense: now generates the empty 'getControl' method which returns an array of all controls.
• Typescript intellisense: Added 'Xrm.App' to the TypeScript intellisense so that you are no longer required to declare this in your TypeScript files.
• Typescript intellisense: Added the 'formContext.ui.headerSection' and 'formContext.ui.footerSection' to TypeScript intellisense.
• Typescript intellisense: Added the 'getContentType' and 'setContentType' methods to the 'tab' control.
• Updated the 'SetPropertyValue' in the proxy base class to be virtual to allow custom base classes to inherit from and override that method.
• Only the last 3 versions of cached plugin assemblies are preserved on disk. Frees up disk space.

• Fixed an issue where the namespace would be deleted when only trying to regenerate the 'BaseProxyClass' file.
• Fixed an issue in the BaseProxyClass that would cause a runtime exception to be thrown when specifying a 'TopCount' as part of your 'RetrieveProxies' query.
• Fixed an issue where generated items (proxy classes, message names, table names, etc) would not generate with a default namespace when the namespace had been removed from the existing file.
• Fixed an issue where shared project files would show in the linked project when using the 'Link items' project or solution menu.
• Fixed an issue where the 'Gulp' process was not using the correct input file.
• Fixed an issue where the MSBuild targets were not logging information.
• Fixed an issue where the BeforePublishAssembly and AfterPublishAssembly MSBuild targets were not being called.
• Fixed an 'Object reference not set to an instance of an object' when generating a TypeScript intellisense file.
• Fixed an issue where line breaks in attribute descriptions would cause compile errors after generating a proxy class.
• Fixed an issue when copying links from another organzation.
• Fixed an ILMerge dialog issue.
• Fixed a 'NullReferenceException' error when trying to save the .xrm file in some instances.

• XrmToolkit CLI now included in the Visual Studio extension to allow custom naming service functionality without needing to download the CLI separately.
• Added Xml comments for public members of the proxy base class (C# only).

• Fix issues with windows where copying/pasting into a textbox copies text to the underlying open file instead of the textbox. All windows are now shown modally.
• Fixed an issue with trying to connect to a CRM 2013 on premise instance.
• Fixed an issue when a referenced file does not have a file extension.
• Fixed an issue when trying to generate a lot of proxy classes (~200+) that used either the CrmSvcUtil or custom naming service which threw an error due to the command line args going over the allowed limit.
• Fixed an issue where double quotes were not being handled correctly for labels for optionsets in proxy classes.
• Fixed an issue when trying to add items to a project from a CRM 2015 organization.
• Fixed an issue when an 'Active Solution' is not set for the organization.
• Fixed an issue where line breaks in comments or summaries was causing compile errors.
• Fixed an issue where proxy naming logic was not using existing enum names in some instances.
• Fixed an 'Object reference not set to an instance of an object' when trying to register a plugin step.
• Fixed an issue with an 'ObjectDisposedException' being thrown while trying to connect to your organization.
• Fixed an issue when using the CrmSvcUtil method that was having an issue with organization URL's that included the service endpoint.

• Fixed regression introduced that prevented completing the 'New Solution' wizard.

• Added logic to remove duplicate CrmFile entries in the .xrm2 file upon loading of the file.
• Added the ability to specify a connection timeout in the global settings for connections with Dynamics365.
• Improved the connection error message when the error is due to the WS-Trust authentication protocol being deprecated for an organization.
• Updated Microsoft.CrmSdk.* packages to the latest.
• Improved handling and reloading of the .xrm2 file when it is modified outside of Visual Studio or when the source control branch is changed.

• Fixed an issue where the progress bar would not display when automatically publishing an item when the item is saved.
• Fixed an issue where certain file types were not automatically publishing when the item was saved.
• Restored the ability to publish a plugin project using the XrmToolkit CLI.
• Fixed an issue where entity metadata was duplicated in some dropdowns/windows.
• Fixed an issue where creating a new plugin project would error out if you tried to generate the proxy classes using the CrmSvcUtil method.
• Fixed an issue where custom proxy settings would not be used/saved when using the 'Create new plugin/workflow' menu.
• Fixed issues with previous proxy generation not being taken into account when generating new proxy classes during the 'New Plugin/Workflow' process.
• Fixed an issue where bitmap errors were causing XrmToolkit not to load properly.
• Fixed an error that was being thrown while trying to call the 'AddPluginAssemblyToCRM_BeforeQueryStatus' method.
• Fixed an issue with the .xrm2 file not loading when the solution contained a 'Setup' project.
• Fixed an issue where the 'SetState' and 'SetStateAsync' methods were not being generated when using the 'XrmToolkit' generation method.
• Fixed an issue where a '/' was being added to the suggested name of a web resource when it was not necessary.
• Fixed an issue where the XrmToolkit CLI expected path was incorrect.

• The 'Link Items from Solution/Project' is now able to recognize 'OptionSetEnums', 'PluginBaseClass', 'TableNames', and 'MessageNames' classes.
• 'Link Items from Solution/Project' window now shows files that it recognizes but was not able to find a match for.
• Added the ability to View/Save logs when a connection error occurs.
• Added the ability to view Gulp errors/issues when viewing a linked item properties.
• Added the ability to change the logging level in the global settings to allow capturing verbose level logging.
• Updated to the latest CRM SDK packages.

• If an error occurs during the assembly key generation, the error is logged instead of thrown which prevented the project create process from completing successfully.
• Fixed an issue where Gulp tasks were not showing if the Gulp NPM package was installed at the solution level instead of the project level.
• Fixed issues when trying to find a match for an existing item when the output extension is different than the file extension, ie TypeScript, LESS, SASS etc.
• Fixed an issue where the 'Create License Activation Request' window would not show when license activation failed over the internet.
• Fixed an issue where the D365 menu would not show for a valid item if the project was not yet linked.
• Fixed an issue where NuGet packages for a project were not displaying in the 'ILMerge' window.
• Fixed an issue where WebHooks and their corresponding steps were not displaying in the 'Plugin Registration' window.
• Fixed an issue where duplicate table names were being generated in the 'TableNames' class.
• Added appropriate 'using' statements to proxy classes that were causing compilation errors when they were missing.

• Proxy naming now takes into consideration whether language keywords are case sensitive and handles any conflicts accordingly.
• Removed unnecessary 'using' statements from proxy templates.
• If NodeJs is not installed globally, then XrmToolkit defaults to the version installed with Visual Studio.
• If no language is related to a portal asset then assets are grouped under an 'Unspecified Language' node and subsequently downloaded to an 'Unspecified Language' folder.

• Fixed an issue preventing the ability to publish a web form step.
• Fixed an issue that prevented being able to connect to an on-premise organization.
• Fixed an issue where duplicate enum definitions were being generated when a table used the same global optionset for multiple columns.
• Fixed an issue where custom actions were not being generated when using the CrmSvcUtil generation method.

• Content snippets are now grouped by their associated language in the download window.
• Web form steps are now grouped by their associated web form in the download window.
• Ability to save or view the log file when an error is shown.
• Web projects that are created by XrmToolkit now specify the output type of 'Library' by default.

• Fixed an issue when trying to create a new plugin or workflow and a 'System.InvalidCastException' is thrown.
• Fixed an issue where plugin type configs were not correctly determining if there were any differences between deployed configs and saved configs.
• Fixed an issue where you couldn't register a new plugin if the target .Net Framework version was higher than the recommended version.
• Fixed an 'Object reference not set to an instance of an object' error when generating proxy enums that contained 'null' option values.

• Fixed an issue where you were not able to register a plugin or workflow that existed in the published assembly.
• Fixed an issue where an image and/or secure config were not registered when the options were specified in the 'Register Step' window.
• Fixed an issue when creating a new web resource and the publisher prefix was not prepended to the suggested name with an underscore (_) in the window.
• Fixed namespace issues when generating Visual Basic proxy classes.
• Fixed an issue where the 'Build and Publish' was failing due to an 'Object reference not set to an instance of an object' error.

• Fixed an issue where you could no longer regenerate proxy enums that had been previously generated using the CrmSvcUtil method and combined into a single file.
• Fixed proxy generation issue where proxy enums were generated in their own files regardless of the setting when using the XrmToolkit generation method.
• XrmToolkit now recognizes the preview versions of the Dataverse SDK packages and no longer tries to install the current SDK if the preview is already installed.
• Ability to link multiple files to the same Dynamics 365 asset has been restored.
• Fixed an issue when trying to downlaod a 'WebForms' asset from a portal website.
• Fix an issue where trying to type in the column filter loses focus and constantly overwrites the filter text.
• Log a warning about a possible issue when targeting a .Net Framework version in a plugin assembly instead of throwing an exception which would cause the publish to fail. See here about the recommended .Net Framework.

• Added the ability to download/import Portal assets to a Visual Studio project.

• Fixed an issue when generating proxy classes that used the 'CrmSvcUtil' method.
• Fixed an issue when generating proxy classes in a solution that contained a Solution Folder.
• Fixed an issue where the TypeScript intellisense files did not include the entity name as part of the file name causing collisions between different file names.
• Fixed an issue on the 'Download assets from D365' window where filtering items and then selecting the parent node still selected all children, not just the filtered children.

• Fix an issue while trying to register/edit a step that was 'Synchronous'.
• Fix issue with 'Compare to D365' not showing in menu.

• Fixed an issue where you couldn't select multiple entities in the 'Register Multiple Steps' window. All messages were filtered out in some instances.
• Fixed an 'Object reference not set to an instance of an object' error during proxy generation in certain circumstances.

• Fixed an issue where the 'Add Reports Project' menu was greyed out even though SSRS/BIDS was installed for VS2017 and VS2019.
• Fixed an 'Object reference not set to an instance of an object' error during 'Build and publish' execution in certain circumstances.

• Fixed an issue where there was a conflict between different versions of the CRM SDK.
• Fixed an issue when trying to link a Plugin assembly to CRM causing a "Mono.Cecil.ModuleDefinition" exception.
• Fixed an issue with the SS.Crm.Linq.dll causing a "Bad binary signature" exception.

• Fixed an issue where plugin configurations were not appearing in the 'Edit Plugins and Steps' dialog when using VS2015.
• Fixed an issue where the version was not showing in the 'Solutions' dropdown.

• Fixed an issue where new workflows created using the wizard were not being added to the Visual Studio project.
• Fixed an issue where N:1 relationships were not being generated when using the CrmSvcUtil generation method.
• Fixed an issue where 'ReadOnly' properties were not being generated when using the CrmSvcUtil generation method.
• Fixed an issue where relationships were not generating for proxy classes in some instances.

• Fixed regressions introduced in update 6.4.4 to naming of proxy classes/enums.
• Improved logic for displaying splash screen during operations.
• Fixed an issue causing VS to crash when switching source control branches.

• Various fixes around proxy class generation.

• Improved ProxyClass enum name generation for non-English languages.

• Fixed an issue with TypeScript intellisense generation.

• Fixed an issue with Proxy class generation.

• Added the ability to specify a connection string for connecting to CRM.

• Fixed an issue where 'System.Compiler' was not found.
• Fixed an issue with proxy class regeneration.
• Fixed an issue where the 'New Plugin Wizard' would error at completion.

• Improved the "auto-format" of a JavaScript file upon download so that it understands ES6 concepts such as template literals and arrow functions.
• Added the "process.setStatus" method to the Xrm.d.ts file.
• Enhanced the proxy base class so that it better handles "null" values after being retrieved from CRM.
• ILMerge is no longer required to be downloaded as a separate file. It is included as part of XrmToolkit package.

• Fixed an issue where Visual Studio would hang after switching source control branches.

• Added the ability to generate proxy classes for entities that do not have a display name.

• Fixed an issue where not all SDK messages would load due to more than 5000 records.
• Fixed an issue where proxy classes were not being added to the project after generation.
• Fixed an issue where Visual Studio would hang after being prompted to reload the XrmToolkit configuration file.
• Fixed an issue where the .Net Framework version was not being set correctly for newly created projects.

• Added the ability to force XrmToolkit to use the old proxy method of generation (Enums in the same file as the proxy class)
• Added the ability to use the default Windows credentials to login instead of requiring a username and password.

• Fixed various connection issues due to missing dlls.
• Fixed an issue where proxy class enums were being created in the directory 'ProxyClasses/Enums' regardless of the 'Proxy Classes Path' setting.

• Fixed an error with Microsoft.VisualStudio.LanguageServices.dll

• Fixed an issue with proxy class name and property name generation.
• Fixed an issue with proxy class file name being generated as ".cs"

• Support for Visual Studio 2019
• Improved Proxy Class Generation - Individual Enum files are now generated for each optionset and only a single file is generated for global optionsets.
• Improved TypeScript and JavaScript intellisense generation.
• Support for MFA
• Support for SVG files
• Support for Resx files
• Support for MFA when using the API
• Support for specifying the connection protocol (Tls 1.1 vs Tls 1.2 etc)
• Added the ability to specify the 'Use Strong Types for One-To-Many relationships' at the organization level.
• Support for relative directories when overriding references for the ILMerge process.

• Visual Studio 2013 is no longer supported.

• Fixed an issue where not all of the Sdk Messages were being retrieved to be able to register steps against.

• Fixed an issue with CrmSvcUtil proxy classes not generating with an "Object reference not set to an instance of an object" error.

• Fixed an issue with CrmSvcUtil proxy class generation.

• Fixed issue with license registration dialog not closing.
• Fixed issue with Enum property on a proxy class not being decorated with the 'AttributeLogicalName' attribute.
• Fixed an issue where only the top 5000 web resources would show in the 'Add Items to Project' dialog.
• Other misc bug fixes.

• Fixed issue with incorrect namespace being generated for proxy classes when being placed in the root folder of the project.
• Fixed issue where license registration wizard would not close upon completion.
• Fixed an issue with Microsoft.VisualStudio.LanguageServices.dll error upon startup.
• Fixed an issue with Microsoft.Xrm.Telemtry.dll error when loading plugins and steps for the solution.
• Fixed issue with TLS 1.2 protocol when connecting to D365 on-line.
• Fixed an issue where the 'AttributeLogicalNameAttribute' was not being applied to decimal properties related to 'money' properties when generating proxy classes.

• Fixed error that was being thrown when starting up Visual Studio
• Fixed issue with multi-select option sets generating incorrectly for proxy classes

• Fixed an issue with VS2015 not responding to any XrmToolkit menu actions.

• Added support for the updated Xrm SDK (v9)
• Added support for multi-value option sets

• Fixed issue with the base proxy class template where a maximum of 5000 records were being retrieved for N:N relationships.
• Fixed an issue where the base workflow class and workflow class templates were switched when generating them in VB.
• Fixed issue where web resources were not downloading to correct file location.
• Fixed an issue introduced by a VS 2017 update where you would not be prompted to login when opening a linked solution.

• Updated the Xrm.d.ts files to be compatible with TypeScript >= 2.4
• Added the ability to include the Microsoft.Xrm.Client.dll as one of the assemblies that can be ILMerged

• Fixed issue where you could not publish a web resource with the file extension of '.htm'
• Fixed an issue where you could not set a value to 'null' in a proxy class if the value had not been set previously.
• Fixed an issue with not being able to navigate to a license file while registering XrmToolkit.
• Fixed an issue with not being able to register a step that doesn't require an entity to be selected using the 'Register Multiple Steps' dialog.
• Fixed an issue with not being able to link SSRS reports using the 'Link Items To CRM' command.
• Fixed an issue with not being able to manually login to an organization if the 'Prompt to Logon' setting is un-checked.
• XrmToolkit Api - Provided a better error message when the project specified does not exist.

• Fixed issue where you could not generate JavaScript or TypeScript intellisense files
• Fixed issues with VB.Net Proxy class generation

• Support for Dynamics 365
• Support for Visual Studio 2017
• XrmToolkit API to allow deploying plugin and workflow DLL's without Visual Studio
• Support for JSX and TSX files
• Ability to download and edit email templates
• Ability to download and edit system and user views
• Ability to execute FetchXML queries and view the results directly in the Visual Studio IDE
• Ability to download and edit Process (workflow) XML definition files
• Improved serialization of the .xrm file so that less conflicts occur when working with multiple developers.
• When 'getting latest' in Visual Studio, if the .xrm file has changed, you will now be prompted to reload it. Reduces the chance that users will overwrite changes others have made to the file.

• Support for Visual Studio 2012 has been dropped.

• The base plugin template now includes 2 structs for easily specifying both the message name and entity name when registering a plugin. New plugins or workflows automatically use these new structs for the registration of the logic in the constructor.
• Support for LESS and SASS (scss) files have been added. You can also optionally specify GULP tasks related to these files that should execute before they are published to CRM.
• Improved support and error handling for source control systems when files are locked and cannot be checked out for edit.
• Moved the logic to check the signature of a plugin assembly until after the assembly has been built. This allows for a build task to sign the assembly.
• When publishing multiple items that perform a Gulp task, if the same task is specified for more than one item then the task is only executed a single time, unless the 'Force Execution Of Gulp Task On Bulk Updates' is checked.
• Updated the plugin registration window to use the 'DisplayName' as the name to display for plugin types when appropriate.
• Added the ability to download and store Silverlight (Xap) webresources in a CRM assets project.
• Added the ability to specify different locations for Xml, Xsl, and Silverlight Web Resources.
• CrmSvcUtil generated classes now include properties for related entities.

• Fixed an issue where a project that was linked to CRM would not appear to be linked. The project was located in a different location from the solution.
• Fixed an issue where you could not download a CRM Solution that included the sitemap after editing the sitemap with the sitemap editor.
• Fixed an issue for certain scenarios when a webresource did not have an 'Output File Name' on the Gulp settings tab.
• Fixed an issue where CSS was not being minified properly.
• Fixed the following error: "Unable to load one or more of the requested types" while trying to generate early bound/proxy classes.
• Fixed some layout issues when using a high DPI monitor.

• You can now specify a Gulp task to perform during the publishing of a TypeScript, JavaScript, Html, CSS or XML file. See here.
• Added the 'assembly: Microsoft.Xrm.Sdk.Client.ProxyTypesAssemblyAttribute()' attribute to the Proxy Base Class allowing the XrmToolkit base classes to be used with a CrmServiceContext.
• Added the ability to create a plugin or workflow in a specific directory by right-clicking on the folder and selecting the 'Create New Plugin or Workflow' button item under the 'CRM' menu.
• Added the ability to specify an action to perform upon linking a file to CRM. Options are: 'Nothing', 'Download from CRM', 'Publish to CRM'.
• Support for SSRS reports in Visual Studio 2015 (on-prem only). Download the SQL Server Data Tools for Visual Studio 2015.

• Authentication now sets the 'useDefaultCredentials' to 'true' for networks using proxies. Resolves some issues related to connecting to CRM if you are using a proxy server.
• Resolved an issue where creating a new 'CRM Assets' project would not save the links to CRM for the newly downloaded files.
• Resolved issue where new CRM asset files would not get automatically added to the selected solution.
• Fixed an issue where selecting an existing file to link to in the 'Link Items to CRM' dialog was not actually linking to the file.
• Fixed an issue where enum descriptions containing quotes were not escaped properly.
• Fixed an issue where the base plugin class and plugin template files were mixed for VB.net.

• The 'Step Name' is now automatically calculated based on the entity, message name, and pipeline stage when using the 'Create Step' dialog in the plugin registration window. You can still manually change it if a different name is preferred.

• Fixed an issue with the enum name for status codes being generated incorrectly for proxy classes.
• Fixed conflict with System.Threading.Tasks.Task while generating a proxy class for the 'Task' entity in CRM.
• Fixed formatting issue for proxy classes for cultures that use a comma instead of a period as a placeholder.
• Fixed NewtsonSoft.Json deserialization error message.
• Fixed issue with JavaScript intellisense files not generating correctly on initial creation.
• Fixed an issue where the System.Collections.Immutable.dll could not be found.

• OptionSet enums are now generated for all the specified entities and placed in a separate file titled 'OptionSetEnums' when using the CrmSvcUtil method for generating early bound classes.

• Updated Visual Basic code templates to the new templates introduced in v4.
• Fixed issue with early bound/proxy class generation during the plugin wizard where the current settings were not being used if the 'Custom Settings' option was chosen.

• You can now compare your local file with what is currently in CRM by clicking a single button. For more info see here.
• Improved 'Link Items to CRM' logic and added the ability to 'Find And Replace' part of the name in bulk.
• The 'Step Name' is now automatically calculated based on the entity, message name, and pipeline stage when using the 'Create New Plugin or Workflow' wizard. You can still manually change it if a different name is preferred.
• Added the 'Depth' and 'MessageName' property to the LocalPluginContext class.
• If the corresponding JavaScript file of a TypeScript has not been generated, a message will appear when trying to publish the file instead of publishing an empty file to CRM.
• Added a check to make sure that a TypeScript file compiles correctly before trying to publish to CRM.

• When using the 'Update All Linked Items in CRM' menu item, the items were being published as well. The logic has been changed so that the items are no longer published.

• Official support for CRM 2016
• Added support for the CRM LINQ query provider. You can now use the Proxy classes just like the early bound classes generated by the CrmSvcUtil. For more information regarding the LINQ provider please see the documentation here.
• Proxy classes now implement INotifyPropertyChanging and INotifyPropertyChanged
• Generate early bound classes using CrmSvcUtil. See here.
• New Plugin Wizard for creating Plugins and Workflows. See here.
• Bulk Link Items to CRM. See here.
• Improved Plugin and Workflow Templates. See here.
• Transfer links between different CRM organizations. See here.
• Easily transfer plugin configurations between organizations and save to version control. See here.
• Improved CRM Linq query provider. See here.
• Ability to specify all report properties when creating/modifying a report. See here.
• Publish the currently open document - A right-click menu in code window for JavaScript, TypeScript and Html for publishing the file to CRM. This allows you to setup a keyboard shortcut for publishing. For more information see the documentation here.
• Ability to link a file without first linking the project.
• Ability to create plugin configurations without first registering them. This allows you to setup all your plugin configuration and then register everything at once.
• Ability to download the 'DLL' of any plugin registered in the database.
• Ability to see what other steps are registered for the same entity and message. This allows you to determine the order that plugins are executed in the pipeline very easily.
• Proxy classes now implement INotifyPropertyChanging and INotifyPropertyChanged interfaces

• CRM Solution Manager now requires .Net Framework 4.6
• Since the Proxy Classes now derive from the 'Entity' class instead of instantiating a backing field for the entity, if you are converting an 'Entity' to a proxy class, you are essentially creating a copy of the record. Any changes to the proxy class do not get persisted to the original entity record and vice versa. This comes into play if you are manipulating the 'Target' of a plugin. You can no longer create a 'Proxy' class of the 'Target' just for manipulation of the underlying record. All changes will need to be done to the 'Target' entity itself.
• New file extensions and formats used for the configuration files. Previously the extensions .crmsm, .crmsmu, and .crmmeta were used. They have been replaced with .xrm, .xrmsuo, and .xrmcache. The file contents are now saved in json instead of Xml. You shouldn’t encounter any issues unless you were creating/modifying these files outside of the GUI interface. Due to the new files and formats, an upgrade process will occur to the files. Both sets of files will exist at the end of the process but only the new formats will be used moving forward. If you have users on older versions they can continue to use the older version and files but they will not stay in sync with the updated version of the files. See the documentation for more details.
• Ability to debug web resources has been removed. Since this functionality only worked with CRM 2011 RU12 or less, it was decided to drop support of this feature.
• Auto-backup feature has been removed. Most developers use a source control system similar to TFS and so it was decided to drop support of this feature.
• Visual Studio 2010 is no longer supported.

• Fixed issue with constructor in Proxy Classes.
• Improved performance of loading the plugin registration window.
• Many other minor bug fixes.

• Fixed issue with generating Proxy Classes.
• Improved performance of the loading of the entity metadata on the 'Add Items to Project' dialog.

• Added support for Visual Studio 2015
• Added the ability to specify the ILMerge output name.
• Added the ability to override the ILMerge target .Net Framework version.
• Added the ability to provide a Home Realm URL if necessary.

• Fixed errors related to using ILMerge.
• Fixed issues with the 'Edit Plugins and Steps' window not showing properly.
• Fixed an error that would show if you were not using TFS as your source control system.
• Plugin projects for CRM 2015 now target the .Net Framework version 4.5.2

• CRM 2015 officially supported.
• Enhanced JavaScript intellisense for OptionSets. Ie, Xrm.Page.getAttribute("OptionSetName").getValue() == [Intellisense here for all possible values]
• Added the ability to create proxy classes for 'Intersect' entities.
• Added the ability to specify the ILMerge output directory.
• Added the ability to specify whether or not you wanted ILMerge to generate a pdb file.
• Before writing file contents to disk, a rudimentary check is performed to see if the existing contents are the same. If so, then the contents are not written to disk thus preventing TFS from checking out the file.
• Added CRM 2013 and CRM 2015 specific JavaScript methods to Xrm.js and Xrm.d.ts intellisense files.
• Updated the Xrm.d.ts templates to use the TypeScript definition files found on GitHub here.

• Fixed an issue where you could not specify only a backslash '\' as the file path for web resources to be downloaded to.
• Fixed proxy class issue where some N:N relationship names were generated incorrectly when 'Custom Labels' were used.
• Fixed and issue where an error would appear upon loading a solution: "Please update the 'GetJavascriptType' function to include the new AttributeMetadata type: AttributeMetadata"

• CRM Solution Manager now requires .Net Framework 4.5.2 - This is to provide official support for CRM 2015 which uses the .Net Framework 4.5.2.

• VB.Net proxy classes now contain all the enhancements that were introduced in version 3 for C# classes.

• Fixed an issue where in certain instances Visual Studio was crashing upon loading CRM Solution Manager.
• Fixed an issue where 'BaseProxyClass' was not generating properly.

• Proxy methods for retrieving 1:N related entities now use the name of the attribute on the related entity instead of just a number. Ie, "GetAccounts_Owner" instead of "GetAccounts1". This helps reduce confusion between methods and is also less likely to change the meaning of the method by adding another relationship to the entity.

• Fixed issue when no source control software is installed.
• Fixed issue with enum property name generation.
• Fixed issue with being able to paste into the 'New Web Resource' window.

JavaScript / TypeScript

• TypeScript files are now supported. The JavaScript output is what gets published to CRM.
• Intellisense files can be generated for TypeScript similar to the JavaScript intellisense that is already available. See here.
• Intellisense for Xrm.Page.getAttribute("XXX").setValue() for Optionset attributes. The list of possible values appear and then the intellisense enters the integer value upon selecting a value. See here.
• Added the 'Save' method options to the intellisense prompt. See here.

Proxy Classes

• Proxy classes are now full fledged objects in CRM Solution Manager and are linked to CRM. This allows you to right click on a proxy class and refresh from CRM with the click of a single button. You generate Proxy classes in the same way that you download web resources or other files in CRM Solution Manager. See here.
• Proxy classes can automatically update when the metadata changes and is refreshed in CRM Solution Manager. See item 2 here.
• Proxy classes can enforce length, min, max on text and number attributes. See here.
• Proxy classes can auto truncate text that is longer than is allowed for a string attribute. See here.
• Proxy class names can now be based on a specified pattern. See item 7 here.
• Proxy classes now return records as Proxy classes without the need for casting, ie GetLeads() now returns List<Lead> instead of List<Entity>. This only applies to proxy types that have already been generated or are selected for generation at the same time.
• Optionset properties now have a method allowing you to easily get the text of the current value. See here.

Misc

• When updates are made to a security role using the Security Role Modification tool the modified roles are now added to the currently selected solution as a solution component.
• You can now specify 'Privileges' on the SubArea of a sitemap.
• New "Download All Linked Items from CRM" button at both the solution and project level.
• New "Update All Items" and "Update and Publish All Items" at the project level. This was only available at the solution level previously. See here.
• Ability to auto publish a webresource or report when the item is saved in Visual Studio. See item 3 here.
• New "Refresh Metadata" and "Clear Cache and Refresh Metadata" buttons at the solution level. See here.

• JavaScript intellisense is now split into 2 separate files. Xrm.js contains the entity agnostic code and the "Entity Form.js" contains the form specific intellisense data. Both files must be referenced on the JavaScript file in order for the intellisense to work properly. This is the same for TypeScript.
• OptionSetAttributes for Proxy Classes now have the following naming convention when using the 'Display Name' for generation: 'DisplayName_OptionSetValue' instead of 'DisplayNameOptionSetValue'
• Enum types in Proxy Classes are now nullable.