power-maverick/pcf-customcontrolbuilder

XrmToolBox Plugin for building and deploying custom control using PCF

PCF-CustomControlBuilder

Xrm Toolbox Plugin for building and deploying custom control using PCF

Overview

This tool makes it easy to create and build PCF custom control by removing the need to write commands. It runs all the necessary commands in the order in which they need to be executed and using proper folder location to execute the commands. This tool also makes it easy to deploy the solution into D365 CE.

Pre-Requisite

1. Install npm from here - any version of npm will do
2. Visual Studio
3. PowerApps CLI. Download it from here

Usage

Before you begin with your custom control you need to specify the working folder for your custom control along with path to Visual Studio Developer Command Prompt (VsDevCmd.bat). Once you have defined the working folder and path to VS Command Prompt you can click on either you want to create a new custom control or edit an existing one. Based on that different windows will open and guide you through the process.

For more details read wiki

Screenshots

Creating New Custom Control

Tool executing commands

pcf-customcontrolbuilder's Issues

MSBUILD : Error the project doesn't exist

Describe the bug
MSBUILD : error MSB1009 : The project file doesn't exist

To Reproduce
1 - Build the component in "CDS Solution detail" section

Screenshots
If applicable, add screenshots to help explain your problem.

Hello,

I have an error when i'm trying to build my zip solution. The csproj file is well in the folder but i have the issue.
Thanks for your help

[Feature]: Build and deployment of "Debug" version of PCF to the "Prod" environment causes issues

Contact Details

[email protected]

Is your feature request related to a problem?

Yes

Describe the problem?

Issue description by one of customers: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Solution-Checker-and-PCF-Component-with-React/m-p/963736/thread-id/4627

We are having some issues with running the solution checker on unmanaged PCF Components with React imported as a dependency.
If i take this example and compile a solution from it, it will give 398 errors from the solution checker (mostly from the react bundle)
https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/ReactStandardControl
Are there any ways to ignore external libraries or maybe i am compiling this in a wrong way?
msbuild /t:build /restore /p:configuration=Release

Provide a solution or an idea you would like to see in the tool?

Root cause of the issue: customer uses XRMToolBox for building PCF control, where by default build builds Debug version, and there is no ability (to the best of my knowledge) to build Production version.

So, request here is to modify UI so that it is clear which version is build and which version will be publish to the CE environment.

We already made doc change:
MicrosoftDocs/powerapps-docs#2561
MicrosoftDocs/powerapps-docs#2560

Relevant log output

No response

PowerShell Execution Policy - Restricted

Describe the bug
On some machines where PS execution policy is not set to unrestricted we are getting an error.

To Reproduce
Steps to reproduce the behavior:

1. Set execution policy to default/restricted
2. Click on Build solution
3. ERROR

Expected behavior
Error should not occur when building the solution

[Bug]: Unhandled error thrown when additional package selection is missed

Contact Details

No response

What happened?

Filled in all the details but skipped selecting "Additional Packages"
Clicked "Create" button and got an unhandled error.

What version of the tool are you using?

2.2021.05.241

What version of XrmToolBox are you running?

No response

Relevant log output

No response

Generic error when opening tool

Describe the bug
I created a control. Everything was fine until I created and built a solution. After that, on the next open of the XrmToolbox, I got this error and the tool stopped picking up details of the solution.

Expected behavior
The error shouldn't appear and a plugin should pick up details of the existing solution.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Win 10
• XrmToolbox Version 1.2021.5.42
• PCF Custom Control Builder Version 2.2021.5.241

Additional context
Add any other context about the problem here.

Path for SolutionPackager.exe is wrong in the latest version

Describe the bug
Path for SolutionPackager.exe is wrong in the latest version

To Reproduce
Steps to reproduce the behavior:

1. New PCF
2. Build and add to new or existing solution
3. See error

The SolutionPackager.exe is in the %user%\AppData\Roaming\MscrmTools\XrmToolBox\Plugins\Maverick.PCF.Builder folder, but the tool is looking for it in the C:\Users\wbittle\AppData\Roaming\MscrmTools\XrmToolBox\Plugins\Maverick.PCF.Builder\CoreTools folder.

Expected behavior
The tool would find the SolutionPackager.exe to complete the packaging process

Screenshots

Desktop

• OS: Windows 10
• XrmToolbox Version: 1.2020.10.41
• PCF Custom Control Builder Version: 2.2020.10.92

Additional context
Manually creating the CoreTools folder and copying the appropriate files there fixes the issue and is a temporary work around.

Initialize PCF Project with recommended structure

When the pcfproj is initialized, add recommended files and folders for easy access

• css, resx, html, etc.

Control with space does not work correctly

Describe the bug
.pcfproj and .cdsproj have spaces in the name. Would like to get it converted into '_'. Also, some of the pac commands fail due to spaces

Console displays corrupted logs if clicked anywhere on the already displayed logs

Describe the bug
After running some commands, if user clicks somewhere on previous logs in the console and later runs another command the execution displays from the clicked caret position.

Expected behavior
Th logs should always start from where the end of line is shown on the log

Desktop (please complete the following information):

• XrmToolbox Version : any
• PCF Custom Control Builder Version : 2.2020.3.22

Issue with selecting an existing solution

Describe the bug
When I select from the drop down a solution file after clicking the "Use Existing Solution" checkbox, nothing shows up in the Solution Friendly Name field or (Publisher) Friendly Name field. The Publisher Unique Name and Prefix fields DO populate. Clicking the Export and Add Control button fails saying "Project file does not exist."

To Reproduce
Steps to reproduce the behavior:

1. Set the control location to an existing control
2. Click the reload details button
3. Click the Use Existing Solution checkbox
4. Choose a solution you have not chosen before
5. The Solution Friendly Name field remains blank and the Publisher Details - Friendly Name field is blank. The Export and Add Control button is enabled, but when clicked reports "Project file does not exist."

Expected behavior
The fields mentioned before should populate and the Export and Add Control button should work properly.

Screenshots

Desktop (please complete the following information):

• OS: Win 10
• XrmToolbox Version: 1.2021.1.44
• PCF Custom Control Builder Version: 2.2021.2.23

Additional context
N/A

One click PCF project open

Is your feature request related to a problem? Please describe.
Nope just enhancement.

Describe the solution you'd like
When a user creates a new PCF project, tool should automatically show a prompt to open the solution in VS Code. Also would be good if code-workspace file is available to make things easier to open

Use existing publisher option similar to use existing solution

First of all, great work on the tool! It's brilliant.

Wondering if you could add a "Use Existing Publisher" option in a similar way to the "Use Existing Solution" option to populate the publisher details?

Find a way to support publisher names with spaces

Is your feature request related to a problem? Please describe.
Yes. The current pac commands that include --publisher-name are looking for the publisher name without spaces. This is a problem as it's very common for a publisher display name to have spaces.

Describe the solution you'd like
Investigation into the existing pac command line to understand if using single quotes, double quotes, or some other special character would allow support for publisher names with spaces. Alternatively, if this plugin could support it via a custom pac command that does support this.

Describe alternatives you've considered
The current solution is to create a dummy solution with a publisher name without spaces to get the PCF control into the environment and then move it the correct solution with the correct publisher.

Additional context
This is an issue with the pac commands as far as I can tell, so this is a request to see if this tool could work around the limitation.

Publish after import solution

After having imported the solution, could you publish the custom control? I always need to publish before the new version is used by the platform

Data Type are sourced dynamically

Data Types shown in the tool should be sourced dynamically so that if there are any changes by Microsoft on the data types then those can be updated without a new version of the tool
This was requested during the tool demo in PCF ProDev Bootcamp in May 2021 by one of the attendees.

Add the possibility to choose build configuration Debug or Release

Hi,
I don't even know it this is something possible but would be nice to reduce bundles size

Allow Choosing an existing solution instead of filling in a new solution details

When we already have a solution that contains all the controls existing in CDS, the toolbox plugin should allow us to deploy the control to an existing solution. Currently we only have the option of either creating a new solution or use the quick deployment

Ability to launch the PCF project in VSCode.

Button next to "Open Project Directory" saying "Open in VS Code" and launch using code will be helpful :)

Recently used location drop-down gives error

Describe the bug
When double-click on a recently used location options the project details are not populated and wrong info gets populated on the Control location.

Power Apps CLI not detected on this machine

Describe the bug
When PCF Builder oppened this issue comes, i installed Power Apps CLI pac command are working on CMD.

To Reproduce
Steps to reproduce the behavior:

1. Power Apps CLI install
2. Open Tools on Xrm Toolbox

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• XrmToolbox Version:1.2021.1.44
• PCF Custom Control Builder Version : 2.2021.1.122
• Power App CLI Version : 1.4.4+g0574e87

Can’t package in the same folder twice

When creating the package, it seems the package is locked by code. I cannot create the same package twice.
Can’t tell if the lock occurs during package creation or during package import but something definitively locks down the file

Create Managed CDS solution

More details later

Tool crashing while opening

Describe the bug
When opening the Tool from XrmToolBox, i just get an exception :

System.ArgumentOutOfRangeException: La longueur ne peut pas être inférieure à zéro.
Nom du paramètre : length
à System.String.Substring(Int32 startIndex, Int32 length)
à Maverick.PCF.Builder.MainPluginControl.CheckPacVersion()
à Maverick.PCF.Builder.MainPluginControl.MainPluginControl_Load(Object sender, EventArgs e)
à System.Windows.Forms.UserControl.OnLoad(EventArgs e)
à System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
à System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
à System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
à System.Windows.Forms.Control.CreateControl()
à System.Windows.Forms.Control.WmShowWindow(Message& m)
à System.Windows.Forms.Control.WndProc(Message& m)
à System.Windows.Forms.Form.WmShowWindow(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

and the entire XrmToolBox crashed as well.

Maybe it's specifically related to my XTB instance, but maybe you also know what to do !
I tried to uninstall and reinstall the tool, same result.

To Reproduce
Steps to reproduce the behavior:

1. open the Tool from the Tool list

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS:Win10
• XrmToolbox Version : 1.2019.11.35
• PCF Custom Control Builder Version : 2.2019.10.22

Thanks a lot !

Issue with Build

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. New PCF or Edit PCF function?
2. Click on '....'
3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Win10]
• XrmToolbox Version
• PCF Custom Control Builder Version

Additional context
Add any other context about the problem here.

Uncheck Existing Solution checkbox shows invalid directory error

Describe the bug
When you uncheck Existing Solution checkbox it shows an invalid directory error. It should not show any error when you check and uncheck.

To Reproduce
Steps to reproduce the behavior:

1. New/Edit PCF
2. Check on 'Use Existing Solution'
3. Select from the drop down list
4. Uncheck 'Use Existing Solution'

Expected behavior
As I uncheck, I am not expecting an error to be shown

Allow 4-level versioning on Solutions

Is your feature request related to a problem? Please describe.
Currently the tool allows 3 level versioning but Dataverse allows for 4-level versioning of solution

Describe the solution you'd like
Would like the tool to support 4-level version with auto-increments

Requested by @Freeetje

Terminate Running Process explodes if nothing is running

Test with Watch is default option

Test with Watch is default option

first cd command now working

Describe the bug
I was using the tool and everything worked fine, after some updates, the tool is not acting correctly, the path of excitation is not correct (XRMToolBox path), none of the buttons are exciting correctly, the solution is not being created or deployed

To Reproduce
Steps to reproduce the behavior:
creating or loading will have the same message

Expected behavior
not navigating to the path of control

Desktop (please complete the following information):

• OS: Win10
• XrmToolbox Version: 1.2020.2.37
• PCF Custom Control Builder Version: 2.2020.3.22

Auto-Increment the version number during build/deploy

This is something that havent thought through but need to capture this as part of enhancement

Unable to Deploy solution as managed

Unable to Deploy solution as managed

Issue while trying to create New from template (CRM Datacard Master)

Bug Description : When I try to create a new PCF with New from template and i choose CRM-Datacard-Master template, it doesnt get created and an error msg pops up which says report this issue in github

Steps to reproduce the behavior:

1. New PCF - New from template
2. Select CRM Datacard Master
3. See error

Expected behaviour : The new PCF folder should get created

• OS: Win10
• XrmToolbox Version : 2020.4.38
• PCF Custom Control Builder Version : 2.2020.3.22

Screenshot:

Managed should be renamed to Release

Describe the bug
Managed checkbox on Dataverse solution is not correct. That button executes the build command in release more.

Add preview image

Ability to add preview image to the control from UI

ReadMe is out-dated

Describe the bug
With new improvements added to the tool; readme file is outdated with old screenshots.

Tool does not respond when Power Apps CLI is not installed on the machine

Describe the bug
Tool does not respond when Power Apps CLI is not installed on the machine

To Reproduce
Steps to reproduce the behavior:

1. Do not install Power Apps CLI
2. Run the tool in XrmToolBox

Expected behavior
Tool should indicate that Power Apps CLI is missing and provide them with installation process

Dataverse solution details build error

Describe the bug
When building the Dataverse solution.

To Reproduce
Steps to reproduce the behavior:

1. New PCF or existing PCF
2. Click Managed.
3. Click Build.

Expected behavior
A successful build.

Screenshots
https://imgur.com/d6nHR2E

Desktop (please complete the following information):

• OS: Win10
• XrmToolbox Version: v1.2021.2.45
• PCF Custom Control Builder Version: 2.2021.2.52

Additional context

1. New to PCF and starting to learn how to build.
2. No history of successful build on my machine.
3. Happens on New or Existing PCF
4. A friend sent me a working PCF, I opened it on PCF Builder, build it and same error is thrown.

Thank you.

XrmToolbox Execution

When PCFBuilder tool is executed in the context of the XrmToolbox I get the following message:
'Could not retrieve existing PCF project and CDS solution project details'

This may have been caused by the deletion of previously existing folders.
The tool executed flawlessly the first time I used it but has failed on each subsequent attempt.

To Reproduce
Steps to reproduce the behavior:

1. New PCF is desired behavior - but tool may be attempting to access a previous project that no longer exists.
2. A more detailed error occurs when you populate the following fields and attempt execution
3. Control Location is pre-populated with desired path. Reloading the details replicates the error message.
4. Namespace (manually entered) with value 'PowerMeUp'
5. Control Name (manually entered) with value 'CustomTagsPBX'
6. Template = Field (option set)
7. Hit Create button results in

Expected behavior
I expected that the commands would be generated and executed in the PowerShell window. The error I am experiencing seems to interrupt this process.

Screenshots
Added as requested

Desktop (please complete the following information):

• OS: Win10
• XrmToolbox Version 1.2021.2.45
• PCF Custom Control Builder Version: 2.2021.2.52

Additional context
VS code was recently added to my system - which means I have multiple versions of it installed VS 2017, VS 2019, VS code
XrmToolbox was reinstalled in an attempt to get around the error
XrmToolbox was executed as administrator in an attempt to get around the error
I attempted to use the settings menu to clear loaded Control Location - but no change in behavior was observed

Full error details
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Maverick.PCF.Builder.MainPluginControl.BtnCreateComponent_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

XrmToolBox
Assembly Version: 1.2021.2.45
Win32 Version: 1.2021.2.45
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/XrmToolBox.exe

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

XrmToolBox.Extensibility
Assembly Version: 1.2021.2.45
Win32 Version: 1.2021.2.45
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/XrmToolBox.Extensibility.DLL

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

Microsoft.IdentityModel
Assembly Version: 3.5.0.0
Win32 Version: 6.1.7601.24479
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.IdentityModel.DLL

System.IO.Compression.FileSystem
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IO.Compression.FileSystem/v4.0_4.0.0.0__b77a5c561934e089/System.IO.Compression.FileSystem.dll

XrmToolBox.PluginsStore
Assembly Version: 1.2021.2.45
Win32 Version: 1.2021.2.45
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/XrmToolBox.PluginsStore.DLL

NuGet.Core
Assembly Version: 2.14.0.832
Win32 Version: 2.14.0.832
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/NuGet.Core.DLL

Newtonsoft.Json
Assembly Version: 12.0.0.0
Win32 Version: 12.0.3.23909
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Newtonsoft.Json.DLL

McTools.Xrm.Connection
Assembly Version: 1.2021.2.40
Win32 Version: 1.2021.2.40
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/McTools.Xrm.Connection.DLL

McTools.Xrm.Connection.WinForms
Assembly Version: 1.2021.2.40
Win32 Version: 1.2021.2.40
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/McTools.Xrm.Connection.WinForms.DLL

Microsoft.Xrm.Sdk
Assembly Version: 9.0.0.0
Win32 Version: 9.0.46.1802
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.Xrm.Sdk.DLL

Microsoft.Xrm.Sdk.Workflow
Assembly Version: 9.0.0.0
Win32 Version: 9.0.46.1802
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.Xrm.Sdk.Workflow.DLL

Microsoft.Crm.Sdk.Proxy
Assembly Version: 9.0.0.0
Win32 Version: 9.0.46.1802
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.Crm.Sdk.Proxy.DLL

Microsoft.Xrm.Tooling.Connector
Assembly Version: 4.0.0.0
Win32 Version: 4.0.0.77
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.Xrm.Tooling.Connector.DLL

Microsoft.Xrm.Tooling.Ui.Styles
Assembly Version: 4.0.0.0
Win32 Version: 4.0.0.77
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.Xrm.Tooling.Ui.Styles.DLL

Microsoft.Xrm.Tooling.CrmConnectControl
Assembly Version: 4.0.0.0
Win32 Version: 4.0.0.77
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.Xrm.Tooling.CrmConnectControl.DLL

Microsoft.IdentityModel.Clients.ActiveDirectory
Assembly Version: 5.2.8.0
Win32 Version: 5.2.8.0
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/Microsoft.IdentityModel.Clients.ActiveDirectory.DLL

WeifenLuo.WinFormsUI.Docking
Assembly Version: 3.0.6.0
Win32 Version: 3.0.6.0
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/WeifenLuo.WinFormsUI.Docking.DLL

WeifenLuo.WinFormsUI.Docking.ThemeVS2015
Assembly Version: 3.0.6.0
Win32 Version: 3.0.6.0
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/WeifenLuo.WinFormsUI.Docking.ThemeVS2015.DLL

ScintillaNET
Assembly Version: 3.6.3.0
Win32 Version: 3.6.3.0
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/ScintillaNET.DLL

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Net.Http
Assembly Version: 4.1.1.3
Win32 Version: 4.6.26907.01
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/System.Net.Http.DLL

System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll

System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

McTools.StopAdvertisement
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/JohnThibodeau/Documents/XrmToolbox/McTools.StopAdvertisement.DLL

System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll

Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.ComponentModel.Composition
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.Composition/v4.0_4.0.0.0__b77a5c561934e089/System.ComponentModel.Composition.dll

DamSim.SolutionTransferTool
Assembly Version: 1.2020.12.15
Win32 Version: 1.2020.12.15
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/DAMSIM.SOLUTIONTRANSFERTOOL.DLL

DamSim.ViewTransferTool
Assembly Version: 1.2019.11.4
Win32 Version: 1.2019.11.4
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/DAMSIM.VIEWTRANSFERTOOL.DLL

GapConsulting.PowerBIOptionSetAssistant
Assembly Version: 1.2021.2.4
Win32 Version: 1.2021.2.4
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/GAPCONSULTING.POWERBIOPTIONSETASSISTANT.DLL

Javista.AttributesFactory
Assembly Version: 1.2020.12.7
Win32 Version: 1.2020.12.7
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/JAVISTA.ATTRIBUTESFACTORY.DLL

Javista.XrmToolBox.ImportNN
Assembly Version: 1.2020.11.11
Win32 Version: 1.2020.11.11
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/JAVISTA.XRMTOOLBOX.IMPORTNN.DLL

Maverick.PCF.Builder
Assembly Version: 2.2021.2.52
Win32 Version: 2.2021.02.052
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MAVERICK.PCF.BUILDER.DLL

MsCrmTools.AccessChecker
Assembly Version: 1.2018.7.2
Win32 Version: 1.2018.7.2
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.ACCESSCHECKER.DLL

MsCrmTools.AssemblyRecoveryTool
Assembly Version: 1.2019.11.3
Win32 Version: 1.2019.11.3
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.ASSEMBLYRECOVERYTOOL.DLL

MsCrmTools.AttributeBulkUpdater
Assembly Version: 1.2019.5.3
Win32 Version: 1.2019.5.3
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.ATTRIBUTEBULKUPDATER.DLL

MscrmTools.AttributeNamingChecker
Assembly Version: 1.2020.6.0
Win32 Version: 1.2020.6.0
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.ATTRIBUTENAMINGCHECKER.DLL

MscrmTools.AttributeUsageInspector
Assembly Version: 1.2018.9.11
Win32 Version: 1.2018.9.11
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.ATTRIBUTEUSAGEINSPECTOR.DLL

MsCrmTools.AuditCenter
Assembly Version: 1.2019.11.2
Win32 Version: 1.2019.11.2
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.AUDITCENTER.DLL

MsCrmTools.ChartManager
Assembly Version: 1.2017.3.1
Win32 Version: 1.2017.3.1
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.CHARTMANAGER.DLL

MscrmTools.CrmTraceReader
Assembly Version: 1.2018.4.1
Win32 Version: 1.2018.4.1
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.CRMTRACEREADER.DLL

MsCrmTools.DocumentTemplatesMover
Assembly Version: 1.2020.2.4
Win32 Version: 1.2020.2.4
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.DOCUMENTTEMPLATESMOVER.DLL

MscrmTools.EmailAnonymizer
Assembly Version: 1.2019.12.1
Win32 Version: 1.2019.12.1
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.EMAILANONYMIZER.DLL

MsCrmTools.FlsBulkUpdater
Assembly Version: 1.2016.12.1
Win32 Version: 1.2016.12.1
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.FLSBULKUPDATER.DLL

MsCrmTools.FormRelated
Assembly Version: 1.2017.12.3
Win32 Version: 1.2017.12.3
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.FORMRELATED.DLL

MsCrmTools.Iconator
Assembly Version: 1.2018.7.9
Win32 Version: 1.2018.7.9
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.ICONATOR.DLL

MscrmTools.ManagedSolutionDeletionTool
Assembly Version: 1.2016.11.1
Win32 Version: 1.2016.11.1
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.MANAGEDSOLUTIONDELETIONTOOL.DLL

MsCrmTools.MetadataBrowser
Assembly Version: 1.2020.4.13
Win32 Version: 1.2020.4.13
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.METADATABROWSER.DLL

MsCrmTools.MetadataDocumentGenerator
Assembly Version: 1.2021.2.3
Win32 Version: 1.2021.2.3
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.METADATADOCUMENTGENERATOR.DLL

MscrmTools.PortalCodeEditor
Assembly Version: 1.2021.1.15
Win32 Version: 1.2021.1.15
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.PORTALCODEEDITOR.DLL

MscrmTools.PortalRecordsMover
Assembly Version: 1.2020.12.22
Win32 Version: 1.2020.12.22
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.PORTALRECORDSMOVER.DLL

MsCrmTools.SampleTool
Assembly Version: 1.2018.6.23
Win32 Version: 1.2018.6.23
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SAMPLETOOL.DLL

MsCrmTools.ScriptsFinder
Assembly Version: 1.2020.2.12
Win32 Version: 1.2020.2.12
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SCRIPTSFINDER.DLL

MsCrmTools.SecurityRelated
Assembly Version: 1.2020.11.4
Win32 Version: 1.2020.11.4
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SECURITYRELATED.DLL

MsCrmTools.SiteMapEditor
Assembly Version: 1.2019.5.12
Win32 Version: 1.2019.5.12
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SITEMAPEDITOR.DLL

MsCrmTools.SolutionComponentsMover
Assembly Version: 1.2020.5.5
Win32 Version: 1.2020.5.5
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SOLUTIONCOMPONENTSMOVER.DLL

MsCrmTools.SolutionImport
Assembly Version: 1.2016.8.23
Win32 Version: 1.2016.8.23
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SOLUTIONIMPORT.DLL

MscrmTools.SyncFilterManager
Assembly Version: 1.2020.4.2
Win32 Version: 1.2020.4.2
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SYNCFILTERMANAGER.DLL

MsCrmTools.SynchronousEventOrderEditor
Assembly Version: 1.2021.2.0
Win32 Version: 1.2021.2.0
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.SYNCHRONOUSEVENTORDEREDITOR.DLL

MsCrmTools.Translator
Assembly Version: 1.2020.9.14
Win32 Version: 1.2020.9.14
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.TRANSLATOR.DLL

MsCrmTools.UserSettingsUtility
Assembly Version: 1.2020.4.13
Win32 Version: 1.2020.4.13
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.USERSETTINGSUTILITY.DLL

MsCrmTools.ViewLayoutReplicator
Assembly Version: 1.2020.7.5
Win32 Version: 1.2020.7.5
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.VIEWLAYOUTREPLICATOR.DLL

MscrmTools.WebresourcesManager
Assembly Version: 2.2021.2.13
Win32 Version: 2.2021.2.13
CodeBase: file:///C:/USERS/JOHNTHIBODEAU/APPDATA/ROAMING/MSCRMTOOLS/XRMTOOLBOX/PLUGINS/MSCRMTOOLS.WEBRESOURCESMANAGER.DLL

System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4330.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll

WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll

System.Design
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Design/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Design.dll

MetadataViewProxies_ac1feb8b-373e-4cfa-ab71-936291e90f25
Assembly Version: 0.0.0.0
Win32 Version: 4.8.4084.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.Composition/v4.0_4.0.0.0__b77a5c561934e089/System.ComponentModel.Composition.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll

System.Data.Services.Client
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Data.Services.Client/v4.0_4.0.0.0__b77a5c561934e089/System.Data.Services.Client.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll

PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll

System.ServiceModel
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll

System.Web.Services
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Web.Services/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll

System.Runtime.Caching
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Caching/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Caching.dll

Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

System.Deployment
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll

System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll

System.IdentityModel
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IdentityModel/v4.0_4.0.0.0__b77a5c561934e089/System.IdentityModel.dll

Microsoft.VisualStudio.Diagnostics.ServiceModelSink
Assembly Version: 4.0.0.0
Win32 Version: 16.0.102.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Diagnostics.ServiceModelSink/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Diagnostics.ServiceModelSink.dll

System.ServiceModel.Channels
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Channels/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Channels.dll

System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

System.IdentityModel.Selectors
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IdentityModel.Selectors/v4.0_4.0.0.0__b77a5c561934e089/System.IdentityModel.Selectors.dll

System.Security
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4261.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Ability to select Managed/Unmanaged/Both

Add a feature that will allow us to select from the three options provided in the solution.xml file.

Plugin should not assume code file is called index.ts

First of all this plugin saves me the hassle of having to manually run commands to build/deploy these solutions so kudos for that

One thing I noticed though, is the plugin assumes that the code file is called index.ts.

If the file is not called index.ts then the component/solution details do not get loaded.

The manifest file allows for any variation of filename for the code file, so it should not be hardcoded to look for index.ts. Either it should read through the manifest xml file for the code element, or allow an extra input parameter for defining the code file to check

Ability to add new resx files

Add an ability to include new resx files based on the Resource Type

Terminology query Control location vs. Working folder

Not a major issue but may want to consider making this terminology consistent...

Canvas or Model driven on Templates

Define if custom control is supported for Canvas or Model-driven App on the Templates dialog.

Add multiple PCF projects to CDS project

More details later

vs developer command prompt location

Describe the bug
Tool requires full path to the batch file like "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\Tools\VsDevCmd.bat"

This is validated if user is using the browse functionality. I copy pasted the path only
"C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\Tools" and error was not intuitive. May be provide the expected path as hint to the field and also do handling if the path is not ending with VsDevCmd.bat append that and launch it.

Over all it looks great and thanks for the effort .

Deploy button disabled and CDS Solution Details reports Not Initialized

Describe the bug
I can't seem to get the Deploy button to be enabled. Am I using the tool incorrectly or is there a bug? Using the process outlined in the next section was working for me in prior versions.

To Reproduce

1. Point to the control location
2. Click the reload details button
3. Click the Build button under the PCF Component Details section
4. Assuming that succeeded, I click the Use Existing Solution checkbox
5. Select the appropriate solution
6. Click the Export and Add Control button
7. Click the Build button in the CDS Solution Details section
8. The Deploy button is still disabled and the CDS Solution Details section still reports "Not Initialized"

The control builds successfully, the solution is downloaded and extracted successfully, the control is added to the solution successfully, and the MS Build step completes successfully.

Expected behavior
After step 6, I would expect the CDS Solution Details section to report "Initialized". After step 7, the deploy button should be enabled.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• XrmToolbox Version: 1.2020.10.41
• PCF Custom Control Builder Version: 2.2020.10.201

Additional context
When I select an existing solution, the Publisher Name, Prefix, and version all populate correct. However, when I click the Export and Add Control button, it does all the commands, but then clears out the Publisher Name and Publisher Prefix fields - I'm guessing this is why it's "Not Initialized" and the Deploy button is disabled?

Create a new button to just install dependencies

Add a button that will do npm install. This is for projects that are forked from GitHub. Or maybe add some automated mechanism to do npm install.

Add fields for control property

It would be nice to be able to specify properties for this line from the manifest within the tool:

<property name="sampleProperty" display-name-key="Property_Display_Key" description-key="Property_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" />

---

• Deployment: Online
• DB Version: 9.1.0.25551
• Connection Controls Version: 1.2020.10.35
• XrmToolBox Version: 1.2020.11.42
• Tool Version: 2.2020.10.212

Default UniqueName of Published To Lower Case

Describe the solution you'd like
Would it be possible that when creating the Solution.xml file for a PCF solution the UniqueName of the publisher get set to lowercase or you create a field on the PCF Builder for for setting the UniqueName.

I'm asking because recently i have run into some problems with users who have installed my PCF components. The problem occurs because in my components i have always been setting my published name to RAW so the solutions that are generated have the UniqueName of 'RAW'. The publisher though on my primary dev box where I do many of my samples to give to users for the PCF components has the UniqueNameof the publisher set to 'raw'. When doing unmanaged solution this is not an issue but if a user has already installed on of my PCF components as a managed solution they run into an issue when one managed solution with the same Publisher but a difference in the casing of the UniqueNameis imported.

Describe alternatives you've considered
To solve my issue currently I'm going to just go into my dev box and update the publisher unique name to be upercase.

Additional context
Setting the unique name by default to lowercase would match what Microsoft does when you create a new publisher. When you type in the display name they take that to remove any special characters and set it to lowercase.

Here is an image of the Publisher name I typed into the tool and the current way the tool leaves the casing as the way i typed it in for the UniqueName.

Add Release Configuration Mode

Is your feature request related to a problem? Please describe.
Need to reduce the size of the bundle.js files.

Describe the solution you'd like
I would like to be able to select Development or Release mode for the msbuild command that actually builds the component. Currently I am using this tool to build all my components but the bundle.js files are much larger than they need to be.

msbuild /p:configuration=Release

Describe alternatives you've considered
I could also just use DevOps to create a pipeline for these controls to build them in release mode but it would be nice to have the option in the tool.

Additional context
Add any other context or screenshots about the feature request here.