Hi @hotdok,

I assume that you are getting issues with the URL path.

One way is to escape all characters that are special to C#. In this case, the double quotation mark (") is used to denote the end of the string, and the backslash (\) denotes a C# escape sequence. Both need to be prefixed with a backslash (\) to properly escape them in C#.

Eg)
<add key="SitePhysicalPath" value="C:\\Acumatica\\PhoneRepairShop1" />
    <add key="GenResultPath" value="C:\\Acumatica\\Plugins\\Test SDK\\ClassGenerator\\Out" />
 

The other way is to prefix the string with @ and escape only the double quotation marks by replacing them with two double quotation marks (""):

Eg)
string a = @"C:\\Acumatica\\PhoneRepairShop1";

Hi @jinin ,

Thanks for advice. Due to Test SDK docs its ok to have unescaped path. Also I have check inputting incorrect path and it gave me acumatica not found error

Can you log into the site?  I generally get this message when my site is hosed for whatever reason.  

Hi @Patrick Chen 

Yes I can login with specified user. Acumatica works fine

Hello @hotdok 

Acumatica recommends doing classgeneration via TestSDK code for ISV partners and is a requirement to do it as such to certify your solution.

See the below guide, test.cs line 23 for the method. The readme and also the word documents  inside the project will have the correct steps laid out clearly.

https://github.com/Acumatica/Test-SDK-Starter-Guide

Please note you should actually download the git project and rename it - deleting unused files and use it as your test base solution to ensure compatibility.

A common reason for wrappers to not generate on a version update or first time run is because you must update the nuget repository manually using the “packages” folder contents of the testSDK official download zip. Then update the project dependencies to the newly added & version matching ones to the test project/site.
This is all explained in the How to generate Wrappers” guide inside the git project above.

Hi @AaronB 

Thanks for reply. I used latest test SDK 21.225.0006 I found. But Im using acumatica version 22.208.0012 so I think this may be the reasone. Also I found “How to Generate Wrappers.docx” file with code snippet. I updated it and integrated into my test solution. Now I see more logs:

=== Pre-bind state information ===
LOG: DisplayName = PX.Web.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b136cac2f602b8e
 (Fully-specified)
LOG: Appbase = file:///C:/Acumatica/PhoneRepairShop1/
LOG: Initial PrivatePath = C:\Acumatica\PhoneRepairShop1\bin
Calling assembly : Host, Version=21.225.6.7, Culture=neutral, PublicKeyToken=null.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Acumatica\PhoneRepairShop1\web.config
LOG: Using host configuration file:
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: PX.Web.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b136cac2f602b8e
LOG: Attempting download of new URL file:///C:/Acumatica/TemporaryAspFiles/PhoneRepairShop1/testgen/e0fc5271/cebacbcd/PX.Web.UI.DLL.
LOG: Attempting download of new URL file:///C:/Acumatica/TemporaryAspFiles/PhoneRepairShop1/testgen/e0fc5271/cebacbcd/PX.Web.UI/PX.Web.UI.DLL.
LOG: Attempting download of new URL file:///C:/Acumatica/PhoneRepairShop1/bin/PX.Web.UI.DLL.
WRN: Comparing the assembly name resulted in the mismatch: PUBLIC KEY TOKEN
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

So it looks like publicToken keys are different for wrapper generator and acumatica release. How this could be fixed?

Hi @hotdok 

Hi @davidnavasardyan09 

I have reversed engineered Host.dll from ClassGenerator tool and found it references PX.WEB.UI.dll with PublicKeyToken=3b136cac2f602b8e and acumatica of version 22.208.0012 references without PublicKeyToken. When I tried to add public token to acumatica it stops compiling so the issue is public key tokens difference. It looks like ClassGenerator was developed for acumatica of 21 version on 22 but may be Im mistaken. 

Hi @hotdok were you able to find a solution? Thank you!

Hi @Chris Hackett 

No I think the problem is with PX.WEB.UI.dll PublicKeyToken compatiblity. I was not able to solve it. 

Hi @hotdok,

Edit: seems I gave a similar response already. 
Something else to try
1. Delete the classgenerator and any other relevant package from your nuget cache to ensure you download and use fresh references C:\Users\username\.nuget\packages
2. Ensure your %appdata%\NuGet NuGet.config is pointing to valid paths​​​​​​​

3.The Acumatica website, and TestSDK download must be the exact same version. 22.207 will not work with 22.208. If you are using the 21.225 nuget references for sure it will cause major problems like this.

My previous written comment may still help and is valid feedback so I will leave it below

____________________________________

I must agree with @davidnavasardyan09 It looks like you have to update your project references, or you may be using the wrong version of .net in your project.

I highly recommend downloading the TestSDK project I have shared here and using it as your new test project. Follow the steps in the readme to configure it then pasting your existing test code into the project.

https://github.com/Acumatica/Test-SDK-Starter-Guide

Note: we recommend using the GenerateWrappers() method form the above to generate your wrappers now, it uses the same code on the backend but it brings the wrapper generation process into the source control instead of a manual config step each tie you update.

The likely solution to your issue from the Readme:
In your test project inside Visual Studio:

1. Remove all the old Dependencies -> Packages

2. Go to Manage Nuget Packages -> Add a new package source and add the packages folder from C:\AcumaticaTestSDK\TestSDK_23_200_0144_156\packages

3. Add all references from the new source to the project