Hello, I would like to run debug for an on-premise AX7 environment.
I did get it to run with the following process. Is this the proper way to run debug?
As an example…
I want to research modifying an Electronic Payment Format for ACH file for Payroll, which is different than AX2012.
I would like to put a breakpoint in class VendOutPaymNACHAPayroll method generatePaymentLines().
The procedure to run this starts on the Payroll Menu > Pay Statement Processing > Payroll Journal
This is run with the Display Menu Items - LedgerJournalTablePayrollDisbursement which is in the Application Suite.
In Visual Studio I create a dummy project and add the menu item to it and “Set as Startup Object”
then click on the Start button on the menu bar.
Is this the proper procedure to start Debug?
in AX2009/AX2012 with the AOT it is so much easier to run debug.
Thank you,
Tony Bruno
It’s a possible way, but you can also attach Visual Studio debugger to a running process.
Hi Martin,
On the cloud version I attach to the w3wp.exe process but what process do I attach to for on Premise? I have not been able to get Debug to work that way in the On-Premise version.
I’m not sure if I understand. It doesn’t matter which topology (cloud or on-premises) you use for your production environments; development (and debugging) is always the same.
It doesn’t matter either where you install your development VM; the content is the same.
And there is no development in production, either in cloud or on premises.
Hmm, Thanks. I was looking to attach debug to “w3wp.exe” in an on-premise environment and could not find it. I just tried attaching it to “iisExpress.exe” and it worked. How do you determine what process to attach debug to?
All right, so you’re talking about a local developement VM, not the on-premise deployment option of D365FO (which is all about production environment and there is no IISExpress).
Your can use either IIS or IISExpress for development; it can be set up in configuration files. Originally only IIS was available, but when Microsoft wanted to remove administrator permissions in T1 environments hosted by them, they introduced the option of using IISExpress (and made it the default).