简体   繁体   中英

What's the accepted way to distribute an Excel template with .NET dependencies?

I've created a handy-dandy excel template for myself that other people want it now as well. It has VBA and a couple of dependencies in the form of .NET /C# libraries that I've built. For the template to work on another machine, currently I have to drop down to an administrator command window, regasm all the libraries and then the template will work.

So is there a better way to distribute a template that doesn't require all this manual work? For instance, Excel embeds VBA - can it also somehow embed C# code?

您可以创建一些Install批处理文件(或其他类型)来为您做这些重新regasm事情。

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM