Hi Everyone -
I'm having a hard time getting Visual C++ 6 and Pro/E to play nice
with each other. I'm updating a synchronous Pro/Toolkit application
(aka a Pro/E "plug-in"). The only way I know to debug a plug-in on
with VC++ is to use "Build -> Debug -> Attach to Process" to attach
either to the plug-in's .exe (for spawn mode) or the Pro/E xtop process
(for DLL mode). The "Attach to Process" dialog then offers a list of
processes to pick from. This has worked very well for me in the past;
the debugger was for me the most impressive feature in Visual Studio.
What's happening this time, though, is that "Attach to Process" will
not display ANY processes if either Pro/E or Intralink is running.
When I launch Pro/E and refresh the dialog (by toggling the "Show
System Processes" checkbox), the list is empty. When I quit Pro/E
and refresh the dialog, the process list reappears. Consequently,
I can't use the debugger at all.
I'm running Intralink 3.3 and alternating between Pro/E 2001 and
Wildfire 2. Running any of the above will interfere with "Attach
to Process" as I described.
My computer is a Compaq EVO W6000 that was upgraded from Windows NT
to XP this year. Visual C++ 6.0 was installed while the machine
was running NT. I honestly don't know if re-installing Visual
Studio will be any help here.
Has anyone else had these kinds of problems while debugging a
plug-in with VC++ 6.0? If you know of another way to attach
an MS debugger to a plug-in - even if it's command-line driven -
I'd really appreciate hearing from you.
Thanks in advance -
|+| M a r k |+|
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.