- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a fully functional DLL app which is currently being used from Excel VBA and from several process modelling packages.
I have been asked to make this application available from VB .NET, and I have demonstrated that this is possible using VB code which is very similar to the code in Excel VBA.
The VB programmer says he does not want extra wrapper coding overheads and wants my DLL available in COM form. One claim he made (before I provided the solution above, was that the only way he could call my DLL was by creating a (Excel?) worksheet on the fly in memory for each call. He was concerned in particular that he could not register my DLL.
What changes do I need to make to my DLL project to do this? Obviously I do not want to create a maintenance headache for myself in the process. As far as I'm concerned, my current DLL solution is adequate. Is there a better solution?
Thanks for your help,
David
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page