Hi @Prat ,
Migrating from .NET Framework to .NET 8 while retaining MS Access as a front-end introduces challenges, particularly with COM registration for .NET DLLs. .NET Core/5/6/7/8 has no direct support for COM registration like .NET Framework, which leads to issues when using tools like regasm
.
You can manually expose classes to COM by using ComVisible
, and export COM interfaces manually. However, this will require a good deal of coding for each class.
If you want to avoid COM entirely, here are a few alternatives:
- REST API or Web API: You could expose your .NET 8 logic as a REST API (or use gRPC) and have MS Access consume it via HTTP requests. This modern approach allows you to decouple the two systems and doesn't rely on COM registration.
- Named Pipes or TCP Sockets: Another inter-process communication method, though more complex to implement, would be to use named pipes or TCP sockets for communication between MS Access and your backend .NET 8 components.
Best Regards.
Jiachen Li
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.