Mark Brummel - Author of Microsoft Dynamics NAV 2009 Application Design

Mark Brummel - Author of Microsoft Dynamics NAV 2009 Application Design

Recent Posts

Tags

News

  • Published : Microsoft Dynamics NAV 2009 Application Design

Community

Email Notifications

Other Blogs

Archives

NAV 2013 | Debugging (1)

NAV 2013 has a new debugger. It allows us to debug the RTC.

But that does not mean that Microsoft has just migrated the debugger from Classic to RTC. No, they've done much more. It's quite a cool and complete debugger that allows you to do much more than we used to.

For example:

1. You can debug every user on the service tier from one debug session, including webservices.

2. You can put breakpoints in objects that are higher in the stack hierarchy

3. The debugger is designed as pages in C/AL that allow you to modify the debugger to fit your needs.

In this post I want to briefly touch the last example, since I was aggravated by one small issue that I solved and want to share to prevent this from happening to you.

Translation

Because the debugger is now part of the application, it is also translated to your local language.

Now you should know that the Dutch translation in the RTC is to cry. Terrible terminology is used.

This is how the debugger looks in Dutch:

Now I like to use Dutch for the RTC, but I want the debugger to be in English.

This is now an easy task, since we can remove the translation from the objects.

And then the debugger is in ENU.

Except off course the parts that are translated by the RTC itself.

Hopefully more about debugging in a next post

Posted: 2012-12-5 22:55 by Marq | with 8 comment(s)
Filed under: ,
Bookmark and Share

Comments

Mark Brummel - Microsoft Dynamics NAV Blog said:

NAV 2013 has a new debugger. It allows us to debug the RTC. But that does not mean that Microsoft has

# December 5, 2012 11:40 PM

Mark Brummel - Microsoft Dynamics NAV Blog said:

NAV 2013 has a new debugger. It allows us to debug the RTC. But that does not mean that Microsoft has

# December 6, 2012 12:05 AM

Natalie said:

The same here in Germany.

The German translation is so poor that (before having seen it in English) I did not try some functions because I thought they did something totally different.

A feature about the new debugger I like very much and use quite often:

You are able to quit the debugging process together with the NAV transaction.

That way you can prepare the test data, debug and quit, and your test data are still the same as before.

# December 6, 2012 8:35 AM

Erik P. Ernst said:

The debugger is really just another reason why I love NAV 2013, especially compared to NAV 2009.

My only only real issue with NAV 2013, is that I have also seen quite a lot of localization/translation issues in the Danish version of NAV 2013. Not so much bad translations as functionality that seems to work differently depending on the language.

# December 6, 2012 1:10 PM

Andy said:

It seems that the new NAV debugger still has the exact same problems as the old debugger: it only works if there are not comment lines in code. If there are comment lines you have to guess which line is executed, and placing breakpoints doesn't work good either.

# December 6, 2012 1:28 PM

Andy said:

I'm not very fond f the new debugger. It seems very slow, and has the same major problem as the old one: it doesn't work if there are comment lines in the source code. Then you can only guess what line of code is executed, and setting a breakpoint after a few lines of comment doesn't work eigher

# December 6, 2012 1:32 PM

Van Vugt's dynamiXs said:

Not a very creative title, right? Indeed I am not the first one to blog about this. And surely I am not

# April 6, 2013 8:47 PM

Van Vugt's dynamiXs said:

Not a very creative title, right? Indeed I am not the first one to blog about this. And surely I am not

# April 6, 2013 9:00 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)