Blazor Development Support
Support Add-in development in Blazor
Romain Lagrange commented
Oh yeah, +1 !
Possibility to use C# for Office Add-ins development is very important for us. +3
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!!
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!
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#.
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).
At least from my perspective answers to these questions may go a long way to clear up this confusion.
Dr. Roman Becker commented
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?