Comments by Picaro2015 (Top 2 by date)

Hello, thanks for your reply. The use case is that this is a professional environment where currently a solution is excel based with logic in VBA. It is becoming bloated and made up of several spreadsheets. For many reasons I will be creating a library in C# that contains business logic. One of the Excel interfaces still should exist (although be refactored). My goal is that the Excel interface will reuse the new C# code containing the business logic. As far as I can see the best ways to go are either VSTO or to make a COM DLL. Both as far as I could see would work, so my goal really is to go for the most future proof and "standard" solution. Hope this clarifies!