There’s your answer @anon75023439 change the path or give it better permissions. The issue here is your username has periods and it doesn’t like those, give it a path with no periods.
@josecgomez, This was the latest entry.
2019-08-22 11:43:41.217 -04:00 [INF] ===========================================Application Launch==================================
2019-08-22 11:43:41.397 -04:00 [INF] Action was Add
2019-08-22 11:43:43.047 -04:00 [DBG] Created Temp Epicor Directory at: C:\Users\traceyl\AppData\Local\Temp\fa9d4a32-760e-4110-9667-16df02370faa
2019-08-22 11:43:44.647 -04:00 [INF] Got a valid Epicor Session
2019-08-22 11:43:55.363 -04:00 [INF] Downloading Customization. Company: CS, CGCCode: , Key1: CS_CE_PartSearch_V3, Key3:App.HelpDeskEntry.HelpDeskForm, Key3: , LayerType: Customization, ProductType: EP
2019-08-22 11:43:55.363 -04:00 [INF] Sync down is True
2019-08-22 11:43:55.363 -04:00 [INF] Download and Sync a regular customization
2019-08-22 11:43:55.380 -04:00 [DBG] Got in the Function
2019-08-22 11:43:55.380 -04:00 [DBG] Customization Verify
2019-08-22 11:43:55.380 -04:00 [DBG] Got Epicor DLL
2019-08-22 11:43:55.380 -04:00 [DBG] Finding File
2019-08-22 11:44:00.930 -04:00 [DBG] Initialize EpiUI Utils
2019-08-22 11:44:00.930 -04:00 [DBG] Get composite Customize Data Set
2019-08-22 11:44:01.096 -04:00 [DBG] Customization Get By ID
2019-08-22 11:44:01.113 -04:00 [DBG] Get composite Customize Data Set
2019-08-22 11:44:01.130 -04:00 [DBG] Init Custom Controls
2019-08-22 11:44:01.130 -04:00 [DBG] Creating Handle for Top Control
2019-08-22 11:44:02.180 -04:00 [DBG] Generate Refs
2019-08-22 11:44:02.296 -04:00 [DBG] System.IO.FileLoadException: Could not load file or assembly ‘Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: ‘Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed’
at CommonCode.EpicorLauncher.Resync(CommandLineParams o, StringBuilder refds, GenXDataDataSet ds, CustomizationDS nds, CustomScriptManager csmR, Dictionary`2 verdic)
at CommonCode.EpicorLauncher.DownloadAndSync(Session epiSession, CommandLineParams o) in C:\Users\jose\source\repos\CustomizationEditor\CommonCode\EpicorLauncher.cs:line 602
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2019-08-22 11:44:02.317 -04:00 [INF] ========================Application Close=====================
Right click on your newton soft dll in the folder and show me what the version is? Also make sure it is not locked.
Hmm… On my PC it was version 12. I checked another PC and it was version 9 as you show in your screen shot. I copied over version 9 to my PC and it is now working 
Thank you very much @josecgomez
1 Like
Just published a new version of the helper library with an enhancement that the talented @gingerhelp (Adam) cam up with.
This allows you tun Run/Test a customization without necessarily committing those changes to your current (deployed) version.
This button in the toolbox will Run your latest changes wihtout over-writing your actual current code. Very handy when you aren’t sure if something will work.
You can download the helper libraries from the Visual Studio Market Place.
Thanks a ton Adam!
Also check out his article on how to use the extension and github for source control
3 Likes
Nice addition to the app - thank you both. And a beautiful write up @gingerhelp - Thank you!
2 Likes
I’ll second that.
Just added support for 10.2.500.X to the Library, the Helper can be downloaded from the extension page at Visual Studio Extensions Site.
1 Like
With this new feature, does it make version control of customizations easier? (Committing C#/VB code to a git repo)
It always allowed you to use git, since it generates a proper VS project, all you have to do is add that project to your git and commit.
See @gingerhelp’s article above for a walk-through.
All I did in this morning’s update was add support for the next version of Epicor 10.2.500
1 Like
Currently I just copy the customization code into a .cs file. Open it in VS code. Make all changes and commit to the repo. Then take that new code and paste it into the customization.
Why is this way better?
This hooks up directly to Epicor and downloads the customization code for you, creates a project lets you edit it and test (from visual studio) without having to import paste the stuff back in etc.
Watch the demo video (up top)
2 Likes
Beautiful feature. Thanks guys 
1 Like
@josecgomez
I can successfully download an open the code for a customization. When I click the toolbox button visual studio reboots. No log file is created.
Visual Studio Community 2019 V16.3.6
Epicor Version 10.2.500.3
Downloaded the extension and helper libraries today, so they should be the most recent.
We just got an Epicor update today, maybe that is the issue?
Did you download the DLL’s for version 500 of Epicor?
The log file is in the Epicor folder, it should there
Make sure you are downloading the right version of the DLL’s
I downloaded the “CustomizationHelper.10.2.500.X” from the visual studio marketplace website.
It made a log file when I used a folder without permissions for the download folder, but now when I click the toolbox its crashing without making an error message.
Did you make sure the downloaded files are unblocked?>