ClickOnce能否部署单个带COM接口的DLL并完成终端机注册？

Question 1: Is your understanding correct? #

Yep, you’re mostly on the mark here—ClickOnce was built to deploy full Windows applications (EXEs), not standalone DLLs with COM registration. Here’s the breakdown:

• ClickOnce’s core design centers around executable entry points and sandboxed, self-contained app installations. It doesn’t have native support for deploying just a DLL and handling COM registration out of the box because COM typically requires system-wide registry changes, which ClickOnce avoids by default to keep deployments isolated.
• That said, there are ways to work around this if you still want to use ClickOnce to deliver your component:
  • Wrap the DLL in a tiny EXE: Build a minimal console or WinForms app whose only job is to register your COM DLL on first run. Include the DLL and your text files as part of the ClickOnce deployment’s application files. For a .NET COM DLL, you can use the RegistrationServices class to register it programmatically; for a native DLL, you’d call regsvr32.exe (note: this requires elevated permissions, so your ClickOnce app needs to request full trust).
  • Package as a ClickOnce prerequisite: If your DLL is a dependency for another app, you can create a separate MSI installer for it and mark it as a prerequisite in your ClickOnce publish settings. This way, ClickOnce will install the DLL and register it before deploying the main application.

Question 2: Unfinished Question #

It looks like your second question got cut off! Whether you’re asking about alternative deployment methods, troubleshooting registration issues, or something else related to making your COM DLL accessible via VBA, share the details and I’ll help you work through it.

内容的提问来源于stack exchange，提问作者Kevin