Office Development–The Good, The Bad and The Ugly?

Office Development - Good Bad Ugly

In my last post we’ve seen that there are just a whole list of options covered under Office Development. Just to get a starting point we start to focus on Office add-ins –without the capital A– first. With Office add-ins I mean Office add-ins in general, that is … from the early start to where we are today.

I know that these days the name Office Add-ins is considered to be the part where Office Add-ins are built using the OfficeJS APIs but in the early years you had Office add-ins in many forms and technologies.

The Ugly

Initially the only option to customize Office was by adding code using Microsoft’s Visual Basic for Applications (VBA). This was, or should I say is – it still exists and you can still use it, the embedded code engine running a subset of the full Visual Basic command set capable in addressing the Office Object Model to quickly build some Office automation functions to make life as an Office Worker easier. The language appeared to be very powerful and in the real world people built some crazy complex stuff with it.

The Bad

To add more structure to building Office add-ins a new development paradigm was developed. Still using the Office Object Model but this time using the managed languages such as VB.NET or C Sharp (C#).

Managing code with VBA could be a pain in the … Code traveled with the documents and when the document was copied another ‘branch’ was created and you would never know you were working on the latest version unless you managed your distributions very strictly. Also the declaration of variables wasn’t always enforced causing all sorts of runtime errors to surface just after releasing the production code.

By using this new way to build your Office add-ins or customizations (I will return on customizations vs. add-ins later in a separate blog post, that’s a story on itself) with the new tools: Microsoft’s “Visual Studio Tools for the Microsoft Office System” (VSTO) at least you had a better control over your source code and you could even use Source Control to keep track of your code versions.

With this, the first versions of VSTO, seemed to be very hard when it came to installing the add-ins. Security was improved a lot, but that came at the high price of tough installation issues.

The Good

In these days, deploying add-ins can’t be limited to the Windows Platform so another change was rising … these are the add-ins built using the combination of well known web technologies and by including a Manifest you are now able to run your Office Add-ins (with the capital A) on all platforms in all supported and still growing number of client applications. Currently the client applications are Excel, Outlook, PowerPoint, Word and recently added Project, Access and OneNote.


Are these three technologies really The Good, The Bad and The Ugly? Well no, obviously not, you can still build add-ins in all three of these technologies but VBA for instance always had a very bad name, also caused by virus developers using this technology to harm innocent computer users by exploiting the technology to take over the computer and in worst case disable it.

VSTO was considered to be a real improvement but this technology also had his downsides. Deployment could be really hard, but this improved in later versions. Still going multi platform was no option for VSTO.

So is all good with the OfficeJS add-ins? Again, not at all … for starters these technologies used here are in general very hard to understand when you come from the VBA or managed code languages. Also, the APIs are not fully completed.

It still isn’t possible to do all the things that you could do with VSTO. With VSTO there is not really a limit. Whatever you can do with managed code you can do with VSTO as it just is interfacing between Office and .NET. This of course in itself could be very dangerous and should be managed to the max. Also VSTO is used by shady guys building malicious code.

We will get more in detail (we are still diving in, going deeper and deeper at this time) in my following blog posts so subscribe and join me in this adventure called Office Development!

Office Development – Where to Start

Office Development – Where to Start


Starting at you see a wide variety of options related to Office Development. There are a couple of sections to identify when you enter the Getting Started entry

  • Microsoft Graph
  • SharePoint Add-ins
  • Office Add-ins
  • Office 365 Connectors

Apparently, this is not all, as below the four options there is another option:

Can’t find what you’re looking for? Check out this full list of all development options for Office linking to the URL If you follow this URL you’ll notice that it is redirected to, you might have guessed it:, the documentation part of

Here the options are not limited to the options above but now you can see there are sections for:

  • Microsoft Graph
  • Office Add-ins
  • Office 365 Connectors

And below this

  • Office Clients
  • OneNote
  • SharePoint
  • OneDrive
  • Yammer
  • Exchange
  • Skype

Wait …, what …, why is there a section Office Clients separated from the Office Add-ins?

Well, I don’t know. Looking at this it you might think the ‘older technologies’ are under the ‘subsections’. This is true for Office Clients, covering:

  • Office 2013
  • Office 2010
  • Visual Basic Reference

The last item in the list is in fact incorrect, and should have been called “Visual Basic for Applications Reference” or “VBA Reference” or even better “Language Reference VBA” as it redirects to Language reference VBA. It has nothing to do with Visual Basic. Sure Visual Basic resembles a lot compared to Visual Basic for Applications (I will reference to VBA from now on for Visual Basic for Applications) but it isn’t the same. It’s as if you compare Visual Basic to VB.NET they aren’t the same either.

To continue the ‘older technologies’ theory … under SharePoint you find:

  • SharePoint Framework
  • SharePoint WebHooks
  • SharePoint Add-ins
  • SharePoint 2013
  • SharePoint 2010

In this case you see a combination of older and newer technologies. Also under the other subsections you find a mix of newer and older technologies (Exchange) or just newer technologies (, OneDrive, Skype, OneNote and Yammer).

There are even parts missing on this part of the documentation. What about Microsoft Teams as a newer application of Office or existing applications like Microsoft Access. Office and therefor Office Development is just huge, we can spend so much time on these sections, there is no end in all of this.

To start the research, I first want to focus on the Office Clients and their Add-ins. The reason for this is that this was the part that was applied the most when you look at Office customization (adjusting the Office client applications in a way that it suited the needs of the productivity workers).

So, I will drill down from the part covered under Office Clients and move over from there to the section Office Add-ins. This will provide a sense of history and slowly move into the newer technologies as provided in the OfficeJS APIs.

Enough stuff to dig in, so hang in there … see you in my next blogpost(s)

Office Development 2017

Office Dev Center

After many years of Office Development, starting with Excel Functions, VBA, COM (VSTA/VSTO) it is time to dive in and see how things are in done in 2017. What are your options, is it still possible to do things in VBA or doesn’t it exist anymore?

In my upcoming blog posts I want to look at the options available and look at the Office Platform in general. What clients are there these days and on what platform do they run.

The world changed a lot in the last decade and Microsoft Windows is not the only platform anymore. There is iOS, Android, MacOS, Windows … even Linux distributions are growing in popularity.

Even if you just look at it in the online (web) world many of the ‘old’ clients are now available in an Online version. Think of Word Online or Excel Online where you get your editor or spreadsheet application running in a browser application. Again, not so easy as you might think … browser applications should be running in a wide variety of browsers. Do they run in Internet Explorer, Chrome, Safari, Opera etc. etc.

My goal with these Office Development blogposts is also maybe a bit selfish … coming from the ‘old’ (as you might discover) VSTO world, or even older VBA world, I need to polish my knowledge around the current options available and I can already tell you that this ‘new’ Office Development world is huge compared to what it was as the number of clients increased dramatically with the operating systems that I mentioned above, but there is also a huge amount of mobile applications for Android, iOS and (currently not so many for) Windows Mobile.

So … a big challenge. I have no idea where this ends because Office Development these days also include developing for Microsoft Graph (it was Office Graph before, but it was revamped into Microsoft Graph this year, growing bigger than it already was), SharePoint Framework or Office Connectors to extend your Groups or Teams.

That said, stay tuned and feel free to share your comments, tips or complaints in the comments section below!

For now, your starting point for Office Development (next to my blog off course) is:  

SharePoint Framework Extensions Developer Preview now available

SharePoint Framework Extensions Preview

Today the Office Team announced the availability of the SharePoint Framework Extensions Developer Preview. With this you can build site, list and command extensions.

To start building your own Extension Preview projects you can go and start looking at the Preview documentation. If you don’t already have an Office 365 Developer Tenant you can get one if you go to the Office Developer Program so there is no argument not to start using that.

The preview is obviously meant to serve as a way to collect feedback from the community and while the preview is running you can expect new SharePoint Framework Extension capabilities and changes based on your feedback.

If you want to provide your feedback you can do this by adding issues to the GitHub issues list but on the SharePoint tech community, the SharePoint Developer section on the Microsoft Tech Community site.

To give you an impression of what the SharePoint Framework Extensions Developer Preview brings, here are three:

1. Build your own Custom Banner using the ApplicationCustomizer.

Adding a Custom Banner is now one of your options to build your own banner with exactly the information you want to share on your list page.

1. Custom Banner SP

2. Create your own Custom Field Rendering using the FieldCustomizer.

In this example you see that the fields of the list are blurred to hide sensitive list information.

2. Custom Field Rendering SP

3. Adding Command Extensions with CommandSet

With this option you can add your own custom menu actions to be able to trigger your own custom actions.

3. Custom Extensions

If you are looking for more examples (extensions examples will be added soon) for what you can do with SharePoint there is a special SharePoint Showcase site for you to look at and to enjoy all the great options and examples.

Now go ahead, and build your own Extensions using the SharePoint Framework Extensions Developer Preview!

Office Development at //Build/ 2016 – 2 – Graph Changes


Microsoft Graph is a gateway to data and insights in Office365 allowing you to easily traverse over objects and relationships to access the information that is sitting in the Office365 services using web standards. Microsoft Graph is an open platform accessible through a secure data access mechanism.

Microsoft Graph API developer stack.

At Build, with regards to Microsoft Graph the following changes have been announced for General Availability:

  • Webhooks on Outlook Entities
  • Access to consumer services OneDrive and
  • OneDrive large file upload/download

The following, but not only this – there is more, went in preview:

  • Excel REST API
  • Administrative Units
  • Find Meeting Time API
  • Get/set out of office
  • Online meeting links
  • Updates to People API
  • Updates to trending APIs

Documentation on Microsoft Graph can be found at:

Microsoft Graph: The easiest way to call

Office Development at //Build/ 2016 – 1 – The numbers

As you may know I have been visiting Build 2016 the last couple of days, and I plan to get into some more detail of the announcements made at Build this year. A lot of the ‘smaller’ announcements did not make it into the keynotes so hopefully I can share some information with you that you didn’t already hear before. Even if you did it is nice to have a little recap of what goes on right now.

The numbers:


  • 1.2B Office Users
  • 85% of Fortune 500 have at least one Microsoft Cloud Offering
  • 4T+ emails sent with O365 to-date
  • 50K+ new O365 small businesses per month
  • 340M downloads of Office mobile
  • 3B minutes of Skype calls daily
  • 1B+ meetings created per month
  • Microsoft Graph API calls 420% monthly growth

The numbers are impressive, but what is it to you? You are probably only one of these users and who cares? Well, the point is, as an Office Developer there is just a huge big open market to target. Build your tools properly and you have 1.2B potential customers of your tooling. The other thing is that more or less Office is the -standard- for most people or at least provides you with the output that everyone is able to read/use, even the ones using tools from competitors.

Happy wishes and some Office predictions for 2016


Another year has gone, a new year started … this is 2016. Welcome!

My year, for the eleventh time already, started with receiving the Microsoft Most Valuable Professional (MVP) Award again.

After nine years of receiving the award for Visual Studio Tools for the Office System (VSTO), one year of Office365 I now, after the award update, received the award in the award category “Office Servers and Services”. This is where all former Office365, Exchange, SharePoint, Skype for Business and Yammer are grouped today. As of October 2015 the MVP Award categories have changed, there are now less categories and in theory you can get the MVP Award in multiple categories.

So what will bring 2016 to you and me? Well nobody knows… so I don’t know either, but let’s see if we can make some educated guesses here.

2015 was the year Office Microsoft released some early updates on the Office 365 APIs. Starting with the outer ring of Office365 we got access to files, contacts and much more. Access to the documents itself (the structure of the document, in VBA the Object Model) was fairly limited.

In 2016 I expect to see much more APIs providing access to the Office document model. This will give you the functionality, but now cross-platform, like you used to see with VBA, COM-Addins and in VSTA/VSTO solutions.

Let’s see how the Office365 APIs progresses in the year of 2016. Join me in the process of learning the ‘modern’ ways of developing Office solutions on x-plat. Keep an eye on my blog …

%d bloggers like this: