Debug point not hit on the acumatica maint in 23R1 Version:23.105.0016
Best answer by Evgeny Afanasiev
View original
+11
There really isn’t a lot of information to go on here.
Hi
Thank you for the question.
It is a product issue that some .PDBs not matching .DLLs that appeared in late 2022R2 and early 2023R1 versions, including 23.105.0016 that you’ve mentioned.
The first fixed version is 2023 R1 update 6 - 23.106.0050.
The fix will be also in 2023 R2 beta
Hello, does this mean that these versions (late 2022R2 and early 2023R1) cannot be used for Acumatica development (or at least cannot be debugged)?
I ask because we have recently had this issue when trying to step through Acumatica code in Visual Studio. We wasted many hours trying to understand what was happening and why our breakpoints were not being hit. We eventually figured out that the .PDB were the source of the problem.
Are there any plans to update the installations for the versions with incorrect PDB files? If not, is there an easy way to identify versions which can be debugged and ones which cannot?
Thanks
Steve
Hi
There is similar post on community with some comments and build mentioned where this issue is reproduced:
To know for sure, I am afraid the best was is just to try.
Beside VS you also can use SymChk (comes with WDK) to check whether PDBs matching DLLs.
It should be something like:
C:\Program Files (x86)\Windows Kits\10\Debuggers\x64>symchk PathToSite\Bin\PX.dll /s PathToSite\Bin*
IMHO, this is of course an unfortunate situation, but from another hand, how often we see that ERP vendor providing pdbs and source code of the product.
This should not be a blocker, as in theory you can still debug Acumatica, used ICSharp that now comes build in VS, or generate matching PDB yourself. You’d just need to set Match Source Code option of the breaking point to Allow the source code o be different from original.
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.