Below are some frequently asked questions regarding AcceλerateTM for Microsoft 365. If you cannot find the answer to your question, please contact us.
What versions of Excel does Acceλerate for Microsoft 365 support?
Acceλerate for Microsoft 365 supports Microsoft Excel 2016, Microsoft Excel 2019 and Microsoft 365
What are the system requirements for Acceλerate for Microsoft 365?
- Minimum system requirements are:
- Windows 10 or higher operating system
- RAM 8 GB
- Disk Space 290MB
- Prerequisites for optimal performance
- Microsoft Edge WebView2
- Windows Terminal
Can I use Acceλerate for Microsoft 365 on a virtual machine?
No, Acceλerate for Microsoft 365 cannot be used on a virtual machine. However, we do plan on supporting virtual machine use with the release of Acceλerate Pro later this year.
Is Virtual Scheme for Applications (VSA) something that is added with Acceλerate for Microsoft 365 along with Scheme, or is it something that is built in to the Office 365 ecosystem?
Visual Scheme for Applications (VSA) is our name for the Scheme implementation on .NET that our add-in provides, initially to Excel, but eventually to all of the Office applications from 2016 and up. It provides Office automation as well as an alternative language for writing user-defined functions (UDFs) in Excel. Because it is implemented in .NET, interop with the vast array of .NET frameworks and libraries are straightforward.
Can Acceλerate for Microsoft 365 be used in some sort of a full stack type of way where Excel can be the backend server/data manipulator and then use front end, web type of .NET components like Blazor, etc. for something like a dashboard app?
Yes. Backed by a proper .NET language as moldable as Scheme, we envision many possibilities for transforming the data and functions in an Excel spreadsheet into a living, breathing microservice, whether running standalone in Excel on the .NET Framework, or standalone on cross-platform .NET 6. Our professional edition, to be released in the next quarter, will further make development and deployment of such Office-artifact-backed services easy. Regarding UI components, we anticipate providing simple DSLs that can indeed compile to Blazor or create more standard JS-based SPAs, though we would like our user base to support an ecosystem of such libraries whether open source or commercial. So, we like the way you’re thinking, because it aligns exactly with where we are going, and would love to help you explore these approaches! Our motivation is further to create Office-backed microservices that are based on linked-data to facilitate enterprise data interoperability, as our interoperability-focused products, DomainMaster and Unify!, will be able to consume and interact with such modernized Office solutions directly.