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

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

compiler support for WF4 64 bit

vinaym
1-Newbie

compiler support for WF4 64 bit

PTC support site mentions following.

Microsoft Visual C++ .NET 2005 SP1
Note: Supported for Microsoft Windows 32-bit platform.
Not supported for Microsoft Windows 64-bit platform in DLL mode.

Does this still hold true? Has anyone had success with .NET 2005 SP1 on
64-bit?

Regards,

Vinay

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.
4 REPLIES 4
FV
17-Peridot
17-Peridot
(To:vinaym)

Works for us, WF4.0-M080 seems to work better then M040.

Feliks.



In Reply to Vinay Marje:

PTC support site mentions following.

Microsoft Visual C++ .NET 2005 SP1
Note: Supported for Microsoft Windows 32-bit platform.
Not supported for Microsoft Windows 64-bit platform in DLL mode.

Does this still hold true? Has anyone had success with .NET 2005 SP1 on
64-bit?

Regards,

Vinay

Hi Vinay,



I had problems when trying to start apps compiled with 2005 SP1 on Vista
x64 and XP x64 systems with WF4. The first toolkit app would never
start but all of the others would start okay. After lots of testing and
working with PTC to figure out what was wrong it turned out to be 2005
SP1 that caused the issue. When I compiled the apps to x64 on 2005
(without SP1) all of the apps would start fine. It was strange that
only the first app would not start - even if I changed the order of apps
in config.pro or through the protk.dat, so that's why it took so long to
figure out. The last one I tested with was WF4 M070 and it still had
the problem.



Here is something from PTC's site that sort of explains why:



The issue is caused by an incompatibility between the base package and
SP1 of Microsoft Visual Studio .net 2005. The Wildfire4.0 libraries that
are built with the base package, fail to work with SP1. In order to make
the Wildfire4.0 libraries work with the SP1, they would have to be
compiled with SP1 as well.
However, since the base package is the supported configuration
(published in our platform support notes), there are currently no plans
to support the SP1 at the expense of the base package. Once the SP1 will
be supported, it will be updated in the platform support pages.
At this time the platform support pages will be changed to explicitely
decertify the SP1 on Windows XP 64-bit Edition for dll creation with
Pro/TOOLKIT.



Bryan




FV
17-Peridot
17-Peridot
(To:vinaym)

Try M080 - the failure of the first appto start is no longer there.

Feliks.

nikhil
1-Newbie
(To:vinaym)

Workingfineon , WF4.0-M070