Dynamics 365 – Developer Toolkit & Extensions for VS2017

Microsoft Dynamics 365 Developer Toolkit and Dynamics CRM & 365 Developer Extensions are great Dynamics 365 development accelerators available in the Visual Studio Marketplace. Still, these tools are not compatible with Visual Studio 2017, which is the latest release of VS. This is a workaround that you can make use of these tools with Visual Studio 2017.

Dynamics 365 Developer Extensions is a great replacement for Dynamics 365 Developer Toolkit, steps of the workaround has been given below for both the tools.

Step 1: Download  Toolkit or Extensions from following links.

Microsoft Dynamics 365 Developer Toolkit

https://marketplace.visualstudio.com/items?itemName=DynamicsCRMPG.MicrosoftDynamicsCRMDeveloperToolkit

Dynamics CRM & 365 Developer Extensions

https://marketplace.visualstudio.com/items?itemName=JLattimer.DynamicsCRMDeveloperExtensions

Step 2: Extract the .vxis file as follows.

Extracting Microsoft Dynamics 365 Developer Toolkit vxix file Continue reading “Dynamics 365 – Developer Toolkit & Extensions for VS2017”

Advertisements

Intellisense for Xrm.Page in CRM 2011

In CRM 2011 javascripts for crm forms can be stored externally as web resources and those are no longer embedded in CRM forms. Javascripts in web resources can be edited using an external editor. Visual Studio IDE provides intellisense to the Javascripts in Xrm.Page with the help of XrmPage-vsdoc.js. It works with Visual Studio 2010 and Visual Studio 2012. Thanks to Patrick Verbeeten for bringing this cool feature in.

In order to get the intellisense Visual Studio IDE needs the reference of the XrmPage-vsdoc.js file. Follow the following steps to enable intellisense for Xrm.Page in the Javascript.

[1] Download XrmPage-vsdoc.js from HERE

[2] Add XrmPage-vsdoc.js in to the Visual Studio IDE

Continue reading “Intellisense for Xrm.Page in CRM 2011”

Debugging a Plug-in

Plugin is a .NET assembly that can be used to intercept events generated from the CRM system to perform a variety of actions. Some common plug-ins will perform a complicated update routine on CRM entities and\or attributes when it might be impractical to use Javascript or Workflow.

Not like in most of the other developments, in Plugins developers have to debug the CRM plugin code at the time of running the application. Developers writing the plugin code inside the plugin and some times the logic can be write in a seperate assembly and from the plugin code it can be invoked. When writing the whole logic inside the plugin is little complex to test the plugin logic by debugging the plugin as it executes from the application itself in a given event such as create an entity, update or delete.

There are two ways of debugging a CRM plugin as follows,
[1] Attaching the debugger to the w3p.exe process
[2] Forcing the add-in to call the debugger

Demonstration
A plugin has written targeting Account entities as follows and a step has registered to be fired on Account entity’s Create step.
Continue reading “Debugging a Plug-in”

ASP.NET MVC 3 Web Application Project Template

ASP.NET MVC 3 is a framework for building scalable, standards-based web applications using well-established design patterns and the power of ASP.NET and the .NET Framework.

However only the MVC 2 Web Application Project Template is available with Visual Web Developer 2010 Express initially and you have to download MVC 3 from following link and install it in order to get ASP.NET MVC 3 Web Application Project Template on VS Express.

http://www.asp.net/mvc/mvc3