Server Extensibility Demos

  • Post category:Development
  • Post comments:5 Comments
  • Reading time:2 mins read

Yesterday, as a part of Microsoft’s Road To Repeatability program, I delivered a live meeting session about server extensibility in NAV in which I focused on certain areas of .NET Interoperability and Web Services that in my opinion align well with the R2R message.

As promised, here are the materials from the presentation:

I provide this as-is, with no comments, documentation or anything – you are free to use any of these materials in your projects, and I welcome your questions here about presentation content and demos. I’ll do my best to answer them on my earliest convenience.

I hope you enjoyed the presentation yesterday (if you were attending) and that you find these materials useful.


Vjeko has been writing code for living since 1995, and he has shared his knowledge and experience in presentations, articles, blogs, and elsewhere since 2002. Hopelessly curious, passionate about technology, avid language learner no matter human or computer.

This Post Has 5 Comments

  1. Johannes Sebastian


    Thanks for sharing.. Codeunit “Set Fields through C/AL” looks interesting, it that, I dont know what it does 😉
    You dont have a recording of the session by any chance?


    1. Vjeko

      No, sorry, I don’t have a recording, but I am sure Microsoft will publish one. This codeunit demonstrates how to overcome a limitation in .NET interop, namely how to set (and get) field values from object. There are plenty of classes that use fields instead of properties, and this demo shows how to do it when you need it.

  2. Chris Blank

    one small question:
    Why do you use a Web Refence instead of a Service Refence? MSDN also say to use Web Refences but they aren’t state of the art for WCF Web Services…

    THX in advance

    1. Vjeko

      Hi Chris,

      The reason is simple – it’s quicker to write code, and since I am not demonstrating the capabilities of Web Services in general, I opted for Web references as it is simpler to just write the code. Personally, as I already said in – I would use Service Reference (for production code) any day, no questions asked. However, be aware that there are differences between how Web and Service references work, and depending on what you do, some may be better than the other (my 3-blog post series about Web vs. Service reference covers some of my findings in this area.)

Leave a Reply