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

Community Tip - You can change your system assigned username to something more personal in your community settings. X

VB API WF4 and WF5 on 1 machine

AndreasHellmann
3-Visitor

VB API WF4 and WF5 on 1 machine

Hi,

I am using VB API for developing applications for my customers on Wildfire 4 until today and I had no problems with that during the last months....

Now I installed Wildfire 5 M010 and the VB API cannot be used for Wildfire 4 anymore, but WF5 is running well. I have installed WF3, WF4 and WF5 on one machine of course...

My installation:
WF4 M100 and M120
WF5 M010

The problem is that it's impossible to connect with the app to an already running Pro/E session. Again: WF5 is running well, WF4 not. So it's not a problem with my application code.

What I did to switch between WF4 and 5:

1. setting the environment var for pro_comm_msg_exe to the correct version (WF4 or 5)
2.Unregister the version I don't need with <wildfire_version>\bin\vb_api_unregister.bat.
3.Register the version I need with <wildfire_version>\bin\vb_api_register.bat.

In Visual Studio I checked the correct path to the COM reference in either WF4 or WF5. This settings are always correct (the path to pfclscom.exe), either to WF4 or WF5.

Any ideas?

Andreas


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.
1 REPLY 1

That might have something to do with:

C7424204

Dave

Sent from my iPhone

On Jan 7, 2010, at 4:42 AM, Andreas Hellmann <->
wrote:

> Hi,
>
> I am using VB API for developing applications for my customers on
> Wildfire 4 until today and I had no problems with that during the
> last months....
>
> Now I installed Wildfire 5 M010 and the VB API cannot be used for
> Wildfire 4 anymore, but WF5 is running well. I have installed WF3,
> WF4 and WF5 on one machine of course...
>
> My installation:
> WF4 M100 and M120
> WF5 M010
>
> The problem is that it's impossible to connect with the app to an
> already running Pro/E session. Again: WF5 is running well, WF4 not.
> So it's not a problem with my application code.
>
> What I did to switch between WF4 and 5:
>
> 1. setting the environment var for pro_comm_msg_exe to the correct
> version (WF4 or 5)
> 2. Unregister the version I don't need with <wildfire_version>\bin
> \vb_api_unregister.bat.
> 3. Register the version I need with <wildfire_version>\bin
> \vb_api_register.bat.
>
> In Visual Studio I checked the correct path to the COM reference in
> either WF4 or WF5. This settings are always correct (the path to
> pfclscom.exe), either to WF4 or WF5.
>
> Any ideas?
>
> Andreas
>
Top Tags