Feedback by UserVoice

Lance Austin

My feedback

  1. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Lance Austin commented  · 

    Yeah, I would add to this. There are two big challenges that I have faced thus far when developing Office Add-in's.

    #1 - The gap between the VSTO and Add-in API's
    #2 - The developer tooling

    I know the team is continuing to address the gap in API's between VSTO and the Add-ins and this will continue to improve over time. The area I haven't seen much progress or discussion is around developer tooling.

    I would extend Sameera's request to be broader than just Mac and be more about improving the overall Developer Experience. From my understanding the main ways to debug the office clients today are Vorlonjs and Edge Debug Tools (assuming you have windows 10). I do development on both my Mac and PC (Windows 8.1).

    Vorlon is ok and is better than nothing but it is very buggy and doesn't seem to like modern web tools like browser sync. Based on the Github Repo it doesn't seem to be getting any love either.

    Also, I'm an Angular 2 developer so it would be really great to leverage the developer tools that they provide such as the Augury Chrome Extension. Therefore, being able to attach the Chrome Debugger would be ideal on both Mac and PC.

    A lot of times what I end up doing is opening it on Office Online which is much better but since it runs in an iFrame I still end up not being able to use extensions like Augury.

    Overall, the point I'm trying to make is that the Office add-in model is awesome in concept but without a better developer experience it will continue to frustrate users. I'm fully committed to adopting the new add-in model so please let me know how I can help and if I can add additional color around these areas!

    Lance Austin supported this idea  · 
  2. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests and Feedback » Add-in: Excel  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your request!

    We are collecting API requirements for developing Office Add-ins in Excel, specifically for Events API.

    If you are considering moving an existing COM/VSTO/VBA Add-in to Office Add-in, or creating a new Office Add-in in Excel, and have events requirements, please fill the survey below and help us focus on the right set of events and design. We truly appreciate your help!

    https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR-JHDwXr1WhPtbjLQNPOgHtUOFhNTTRVNEE5WE9VVzExOVY5Tko2V05TSi4u

    Thanks!
    Office Extensibility Team

    An error occurred while saving the comment
    Lance Austin commented  · 

    This missing feature is a show stopper for my team. We were excited to leverage the addin model but we need to be able to do formatting on an individual cell when it is changed to indicate to a user that they have edited those cells. Along with that we need to know which row as well so that we can batch all the changed rows into a single update to the backend API. Therefore, this event or a new type of event is needed that would indicate what cell has changed and what row. I'm sure there is other information we could use but at a minimum row and cell.

    Since this doesn't exist today (to my knowledge) my team will have to go with a VSTO solution which ideally we would have wanted to avoid.

    Lance Austin supported this idea  · 

Feedback and Knowledge Base