Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Toolkit support DLLs


Toolkit support DLLs


I am trying to put together a DLL that has come common/generic functionality
that we use in a number of our applications. For a simple example:

void __declspec(dllexport) WriteMessageChar(char * Message)
ProName msgfil;

ProStringToWstring(msgfil, "usermsg.txt");
ProMessageDisplay(msgfil, "USER%0s", Message);

might be one of the functions that I would include. Because all of the
functions in this DLL are just support functions, I am not registering it
with Pro/E (maybe this is part of my problem???). Again, since this is not
registered, it does not have a text directory of its own. My thinking is
that if I had a registered toolkit DLL that had a text directory with
usermsg.txt in that directory, that the support DLL would use that text
directory. That does not seem to be the case. Anytime my support DLL
interacts with anything in a text directory, it kills Pro/E. I have tried
to put the usermsg.txt (as well as resource files where required) in the
text directory of the calling DLL and in the text directory of the Pro/E
load point with no success. Has anyone done anything like this before and
could offer some guidance?



This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Attention: Creo 7.0 Customers
Please consider upgrading
End of Life announcement here.

NEW Creo+ Topics:
PTC Control Center
Creo+ Portal
Real-time Collaboration