Vjeko

NAV TechDays 2014 Pre-conference goodies

Post published:November 19, 2014
Post comments:8 Comments
Reading time:2 mins read

So, NAV TechDays 2014 have started, again, with the pre-conference sessions that were all sold out and packed full.

Today I had an extraordinary pleasure to teach the advanced .NET Interoperability concepts to 15 people that came from all over the world, from Brazil to Australia. It was an interesting workshop, challenging – I must say (thanks to Rafael who made me improvise a solution to a typical DotNet limitation), and I am looking forward to delivering two more sessions about .NET and Control Add-ins tomorrow, and on Friday.

As promised, I am making the materials from the presentation available for the download, in case you want to learn the same stuff the attendees learned today.

(more…)

Do you have a value, Mr. BLOB?

Post published:November 3, 2014
Post comments:7 Comments
Reading time:1 mins read

To check if a BLOB field has a value, you call its HASVALUE function. For example: IF Item.Picture.HASVALUE THEN; In older versions, earlier than NAV 2009, you had to call…

Improving semantics through function properties

Post published:October 30, 2014
Post comments:14 Comments
Reading time:1 mins read

Any function that accepts only one parameter can be called as if it were a property, and this applies to built-in system functions, your own custom functions, and even .NET…

Try..Catch for .NET Interoperability

Post published:October 29, 2014
Post comments:2 Comments
Reading time:13 mins read

While it may be a cold day in hell before we see any TRY..CATCH constructs in pure C/AL, we are all far more lucky when it comes to .NET interoperability. In this blog post I’ll (re)present the same concept I demonstrated during NAV TechDays 2013 last year in Antwerp, because I am quite sure this nifty little trick got lost under piles of other posts on this blog.

So, let’s learn how to do try..catch..finally for .NET interoperability C/AL code, using mostly C/AL code.

(more…)

Adding a ControlAddInReady event to custom controls

Post published:October 23, 2014
Post comments:19 Comments
Reading time:6 mins read

When interacting with custom controls on your pages from C/AL, you must be absolutely sure that the control has been instantiated. If it is not, you’ll get an error such as this:

The reason why this happens is that C/AL code gets to execute before the page has been rendered, and thus also before the custom controls have been instantiated.

(more…)

Vjeko on Testing in isolation
Speed up your automated tests without really doing anything.. on Testing, testability, and all things test
David Hofschneider on Testing in isolation
Vjeko on Directions EMEA 2023 demo – decoupling base app
Vjeko on Directions EMEA 2023 demo – decoupling base app