Blazor Development Support
Support Add-in development in Blazor
Simon Shortman
shared this idea
12 comments
-
Anonymous
commented
Blazor support in Office Add-Ins is very helpful and greatly appreciated please. +1
-
Romain Lagrange
commented
Oh yeah, +1 !
-
Anonymous
commented
Possibility to use C# for Office Add-ins development is very important for us. +3
-
Anonymous
commented
Please add Blazor support in Office Add-Ins. My company has used Microsoft products since I joined in 1993 (DOS 6.2 / Windows 3.1). I've developed several Office Add-Ins and automation (VSTO) over the years using Microsoft development tools starting with Visual InterDEV and graduation to Visual Studo (i.e. VB6, Access, VB.NET, SQL Server, C#, WinForm, WPF, ASP.NET) and would really like to use Blazor Server and/or WASM. Please make this happen soon. Thank you!!
-
croma
commented
+3
-
Roger Bonine
commented
Our development staff has been Microsoft-centric for 20 years. We would like to be able to leverage the skills that we already have for the next round of product development. Please make this happen!
-
BlackLarry
commented
Please let us develop Outlook Add-ins in Blazor WASM - our current one is so full of JavaScript it can make a brave man weep.
-
Willinton06
commented
I mean this is Microsoft to Microsoft thing right? Just make it happen! I want advanced VSTO AddIns in C#! Blazor WebAssembly is such a beautiful thing, just make it happen!
-
Clyde Davies
commented
Our team produces the Chemistry Add-In For Word, https://www.chem4word.co.uk/. This is one of the most sophisticated Word Add-Ins ever written. We have used VSTO and C# up to now because they have given us the power and flexibility to allow this kind of sophistication. We have in-document rendering, structure display and editing, all powered by C#. Our entire object model is in C#.
If Microsoft is now going to insist that we all use JavaScript (a horrible language) and React, then I would expect that at the very least, a migration pathway is provided. I really don't want to have to junk all the perfectly serviceable code we already have.
Please reconsider the decision not to support Blazor. You will catch more flies with honey than with vinegar.
-
Steve Bolman
commented
Please at least advise the feasibility of this now that Blazor Cient is released. I can appreciate that Blazor 'Server' would NOT be expected to work because it would be on the wrong side of the HTML. On the other hand (in my ignorance) it seems that Blazor Client could be called from the HTML in the same way as the JS is currently. Of course there is a lack of tooling to bundle all this together and I would have no idea how to even start to address this challenge.
I agree with the sentiment (confusion) shared by other comments, there should at least be some guidance as why this is more than a tooling problem (if someone could at least explain the technical challenges).
ACTUALLY, I am thinking that this line of questions points out the lack of documentation as to what Taskpanes actually are behind the scenes; when using OfficeJS they look and feel like a browser. But according to the Github repo for OfficeJS "The JavaScript API for Office", where I am confused is that there IS an HTML page that calls the JS code that executes in what seemingly is a 'browser-like' environment (how does the HTML render?) and if these observations are true then why is it not almost trivial to call Blazor code from the HTML instead of JS code? It seems that both "RUN" in the browser right?
At least from my perspective answers to these questions may go a long way to clear up this confusion.
The JavaScript API for Office enables you to create web applications that interact with the object models in Office host applications. Your application will reference the office.js library, which is a script loader. The Office.js library loads the object models that are applicable to the Office application that is running the add-in.
-
Dr. Roman Becker
commented
Making all VSTO programmers out there learn Javascript is ridiculous when all technologies to leverage the power of C# and .NET in the Office365 space are at hand. Not going that route first hand but favoring React is a big mistake that needs to be corrected soon.
-
Remo Oser
commented
It's just logical. For years we were waiting to be able to use "c#" - everywhere - with Blazor its now possible. Now it shall not be possible to use c# within Office add-ins?