.dll debugging issues with Visual Studio 2013 CU8

(0) Share

Report

Posted on by MBinder

I am having an issue debugging a Visual Studio project after we completed the CU8 upgrade. It worked fine with Visual Studio 2010, but not so much with 2013. The project is in the AOT and the code is being executed properly within AX. The previous routine to debug it was to deploy the project from VS then close and reopen the client so the newest .dll would be pulled into the users VSAssemblies folder. I also had to manually add the .pdb file to the VSAssemblies folder. Then I was able to debug and attach to the AX32.exe process and it would load the symbols and hit the breakpoints within the project. Doing the same process with VS2013 does not work. It is saying the .pdb that is deployed with the .dll does not match, even when manually trying to load the symbol file. I have restarted the AOS, deleted VSAssemblies folder so it refreshes everything, compared the VS2013 debug settings with VS2010, and checked the server configuration settings and they all appear to be the same. Has anyone else ran into this issue?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Anton Venter 20,345 Super User 2025 Season 2 on at

Like (0)

Report

The "Require source files to exactly match the original version" option in Visual Studio might be what you are looking for.

Was this reply helpful? Yes No
MBinder on at

Like (0)

Report

Thank you for the response Anton. That option was enabled in VS2010 and it worked. I tried with it enabled and disabled in VS2013 but it is still not recognizing the .pdb file as a match to the .dll

Was this reply helpful? Yes No
Verified answer

MBinder on at

Like (0)

Report
For anyone that may run into this, I seem to have fixed the issue. Here is what I had to do:

Delete .dll out of server/AX/bin/VSAssemblies folder.

Build and deploy project from Visual Studio.

Go into the AOT and compile the project (Deploying from Visual Studio did not deploy the .dll to the server/AX/bin/VSAssemblies folder, but compiling the project from the AOT did. I was under the impression that it supposed to deploy to server/AX/bin/VSAssemblies according to msdn.microsoft.com/.../gg889192.aspx. I had done a compile in the AOT previously, but the .dll versions still seemed to be mixed up and did not match the .pdb file.

Close AX.

Delete user/VSAssemblies folder.

Open AX.

In Visual Studio, add the symbol path of where the .pdb file is located.

Attach to process AX32.exe process in Visual Studio.

I am guessing I messed up a step somewhere previously or a setting was changed, but following these steps in order seemed to ensure the .dll and .pdb matched.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Mbinder,

In Dynamics AX 2012 we have the standard functionality to import the Credit card Transaction using Csv/TXT (Path- Travel and expense- Periodic- Credit Card- Credit card import from folder). I am trying to import the file and file is importing successfully but to modify some of the fields information, I need to modify the DLL fro the same. I have deployed the DLL on client and the debugger is not hitting in .NET code during this process.

Could you please suggest me If I am missing anything ?

Regards

Was this reply helpful? Yes No