Deep-Thought

Deep-Thought GlynP Ye Olde Programmer

Niner since 2014

Comments

  • End-to-End Walkthrough of Excel JavaScript Add-in Development

    Hi Michael,

    During the pause in this conversation I had to put my experimental Excel Add-In project down and also took a couple of weeks off on holiday. I'm ready to pick the project back up now. The old grey cells are struggling to remember where I was with things, so I think I'll start from scratch! (It's an age thing - you'll get there one day).

    Before I jump back into the tutorials and papers I found back in June, do you know of any more recent and/or comprehensive materials reflecting the latest versions of Visual Studio and Office for this work?

    I'm using Visual Studio Community 2015 v14.0.25425.01 Update 3 and Office 2016 (MSO 365) v16.0.7030.1021.

    Cheers,

    Glyn.

    P.S. I've made the suggestion concerning a visual designer for the app manifest file on user-voice as you suggested.

  • End-to-End Walkthrough of Excel JavaScript Add-in Development

    @Michael Zlatkovsky:

    Hi Michael,

    Yes, the developer tools are installed. I wouldn't see the Office project templates in VS2015 if they weren't.

    I've tried refreshing their installation, as well as uninstalling and reinstalling them. It has made no difference. The manifest is still presented as raw XML.

    I've also tried this on my laptop with a clean install of Windows 10 Pro and VS2015 Community. The problem presents itself on that machine too.

    Any clues or pointers would be appreciated!

    Cheers,

    Glyn.

  • End-to-End Walkthrough of Excel JavaScript Add-in Development

    Hi Michael,

    I'm making a start developing an Excel Office Add-in.

    I've got to the section in your video on publishing.

    I'm using VS2015 Community (fully patched) and it will not open the app manifest file in any view other than raw XML.

    This isn't a critical problem, but it would be nice to have the interface you demonstrated to work with finding and changing the various options.

    Is there a fix for this problem?

    Cheers,

    Glyn.

  • Auto History Extension

    @MarkWT: Hi Mark. Thanks for the reply. I understand the distinction you want to make/keep between source control and auto-history. However...

    Maybe it is just the way I work, but source control check-in for me (I use VS online TFS) tends to happen when major chucks of functionality have been completed, breaks, dawning incompetence, or at the end of the day. I tend not to check-in then out each time I decide to 'experiment' or when I have one of those lovely stretches where the code just falls out of my fingers and into the keyboard ;)

    It is the granularity of your auto-history which appeals, its informality, its appeal as a safety net when I have one of my free-form jazz-code odyssey moments...

    I've also assumed (again) that as auto-history keeps an eye on around 72 hours of code it would be useful to gain access to that fine-grained history across my various development machines rather than the more gate-kept lumps managed by TFS.

    Am I making sense or talking tosh?

     

  • Auto History Extension

    Ok, keeping in mind the old Benny Hill sketch about when you assume, "u" make an "*" out of "me"; assuming the developers have signed the usual NDA (knowingly or not), synchronising via personal OneDrive accounts would surely keep the copyright lawyers happy in terms of personal accountability (for leaks)?

    Scenario: Long hard frustrating blind cul-de-sac day at the office. Light bulb moment during the commute home. Auto-history to the rescue... laptop back home; point proved; restful sleep follows...

    Go on, add the feature... ;)

     

  • Auto History Extension

    If this could sync my AutoHistory between my development machines using my OneDrive account I would be a very happy little developer :)