TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
Jon H
NA
18
0
Preventing COM Name Mangling
Mar 8 2011 11:52 AM
Hi,
I am trying to write a replacement for a VB6 dll that is referenced by another VB6 in c# .net.
For now we can only work on the later and I am having some success with this. Except I have run into a problem.
My Enums are being mangling resulting it being called 'A1BACSTrans_BACSAU' instead of the expect 'BACSAU'
the legacy code will (obviously) no longer compile.
Can this be prevented? if so, how? I have heard of modifying the IDL but I can see no references in their to a mangled name only unmangled...
Thank you in advance!
Reply
Answers (
9
)
How to download activex dll files from server to client system using vbscript
MSCOMCTL.OCX raising exception in 64 bit OS (Win 7)