Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Help! LNK error of Pro/E in Visual Studio

stomata

New member
Hi all,
It's my first time being in this forum and I found a lot of helpful people here.
I am a beginner of Pro/E and I want to develop a plugin for Wilfire 3.0.
I tried to setup a visual studio. NET project according to the tutorial I read from another thread from http://www.frotime.com/Tutorials/Tutorials_Free_Download.asp x?ProductID=204
I setup the project and try to compile my sample code and error pops up.


NewProE error LNK2019: unresolved external symbol _GetModuleFileNameExW@16 referenced in function _get_module_path_by_address
NewProE error LNK2019: unresolved external symbol _GetModuleInformation@16 referenced in function _get_module_path_by_address
NewProE error LNK2019: unresolved external symbol _EnumProcessModules@16 referenced in function _get_module_path_by_address

Here is my testing code

#include "ProToolkit.h"
#include "ProUtil.h"
static ProName msgfil;
int user_initialize()
{
int menu_id, UsrModAngle();
ProPath PATH;
ProFileOpen("", "*.txt","","","","",PATH);
return(0); }

void user_terminate()
{
}

I didn't try anything fancy but just one line of Pro/E toolkit code and it fail. Note that I can have the code compiled if I delete the line of ProPath and ProFileOpen....
Please help me on this, I am getting very frustrated with this project....

, thanks
, Grant
 
Hi Grant,


Befor you start compiling your code,you need to make some setting for Pro-Toolkit application code.I am familiar with VC++ 6.0 Settings,but i am least aware of .Net.


You need to have the Includes,Libs....path settings properly with you code,so that you can avoid errors.There might be give some documentation given as TPI in the PTC Technical Support for .Net(Wildfire 3.0).


With regards,


Kishore V
 
stomata,


That tutorial was written for Wildfire 2.0. In Wildfire 3.0 there is an additional library that needs to be included on the link line. You need to add psapi.lib and it should link fine.
 

Sponsor

Back
Top