Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs for v2! What is builderSettings.json? #394

Closed
skfd opened this issue Apr 6, 2023 · 3 comments
Closed

Docs for v2! What is builderSettings.json? #394

skfd opened this issue Apr 6, 2023 · 3 comments

Comments

@skfd
Copy link
Contributor

skfd commented Apr 6, 2023

Fantastic work with version 2!

Just wanted to ask for some docs explaining the new config file format. Should this be a dot file like .builderSettings and git ignored?

@daryllabar
Copy link
Owner

Good point. Added to the doc (https://github.com/daryllabar/DLaB.Xrm.XrmToolBoxTools/wiki/Version-2.2023.4.3-Upgrade-To-PAC-ModelBuilder)

  1. CrmSvcUtil.exe.config replaced by builderSettings.json - EBG-v1 would populate the CrmSvcUtil.exe.config file in the XTB\Plugins\EarlyBoundGenerator folder and then shell out to the CrmSvcUtil in order to generate the entities. This worked but was kind of a hack since the CrmSvcUtil.exe assumed all parameters were inputted via the command line. Microsoft instead allows for the specification of a json file that is used to define the settings to be used. The EBG-v2 maps its settings to the MS properties in this file, as well as it's own custom properties in the "dLaB.ModelBuilder" property. It is recommended to check this file into source control if there is a desire to generate the entities via the PAC command line. Being JSON it may be easier to see changes in configuration of settings used to generate the classes than in the DLaB.EarlyBoundGenerator.Settings.xml file, and is another valid reason to check the file into source control, but again, there is no requirement to since it will be regenerated by the EBG-v2.

@daryllabar
Copy link
Owner

Let me know if that wasn't what you're looking for.

@skfd
Copy link
Contributor Author

skfd commented Apr 6, 2023

That's exactly what I wanted, thank you! Trying to upgrade my project now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants