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

Anybody used Visual Studio 2013 with Creo 2?

scritchley
1-Newbie

Anybody used Visual Studio 2013 with Creo 2?

We're about to jump from Wildfire 4 to Creo 2. Some of our Toolkit apps won't run (built with VS 2008), so I'm going to update Visual Studio and rebuild.


PTC specifies VS 2010, but I was wondering if VS 2013 would be OK (rather than buying an old version now, and having to upgrade again for the next version of Creo).


Has anybody tried using a later-than-specified version of Visual Studio, or is that a really bad idea?


Thanks,


Steve


Wildfire 4.0 M220


Creo 2.0 M110


Windows 7 64-bit


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.
3 REPLIES 3


Hi Steve -

I haven't tried using VS 2013 for anything yet. My past experience with
Creo Toolkit and Visual Studio is that my programs don't link correctly if
I don't use the VC version PTC specifies for your version of Creo. Setting
link options is usually the trickiest and most confusing step in upgrading
these programs.

If you use Creo Toolkit enough, you'll probably find a bug in it. When you
report that bug that you found with a non-standard compiler, it's
reasonable
for PTC to tell you to switch to the standard compiler.

> (rather than buying an old version now, and having to upgrade again for
the
> next version of Creo).

I used to think this way, too, because I didn't appreciate the value of my
own time. I would also prefer to use more recent versions of Visual
Studio.

The time you invest (and likely waste) trying to get those programs to
build
with VS 2013 will cost your employer more than a Visual Studio license.
Just keep your management informed of these upgrade costs.

|+| M a r k |+|

Mark Stallard
Business Application Services
Global Business Services Information Technology
Raytheon Company




(business)
978-436-8487
(cell)
617-331-5443



-



880 Technology Drive
Billerica, MA 01821
www.raytheon.com

This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this message
in error, please so advise the sender by reply e-mail and delete this
message. Thank you for your cooperation.









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

Steve,


Mark is correct, although you can look up the topic -setting build platform - on MSDN.


Creo Parametric works with the Express edition so you don't have to spend extramoney, just make sure the correct SDK's and updates were installed.


Migrating from WF4 to Creo2 would take quite a lot of energy, dealing with extra work involving Visual Studio hacks should be avoided.


My $0.02.


Feliks.

In Reply to Mark Stallard:



Hi Steve -

I haven't tried using VS 2013 for anything yet. My past experience with
Creo Toolkit and Visual Studio is that my programs don't link correctly if
I don't use the VC version PTC specifies for your version of Creo. Setting
link options is usually the trickiest and most confusing step in upgrading
these programs.

If you use Creo Toolkit enough, you'll probably find a bug in it. When you
report that bug that you found with a non-standard compiler, it's
reasonable
for PTC to tell you to switch to the standard compiler.

> (rather than buying an old version now, and having to upgrade again for
the
> next version of Creo).

I used to think this way, too, because I didn't appreciate the value of my
own time. I would also prefer to use more recent versions of Visual
Studio.

The time you invest (and likely waste) trying to get those programs to
build
with VS 2013 will cost your employer more than a Visual Studio license.
Just keep your management informed of these upgrade costs.

|+| M a r k |+|

Mark Stallard
Business Application Services
Global Business Services Information Technology
Raytheon Company




(business)
978-436-8487
(cell)
617-331-5443



-



880 Technology Drive
Billerica, MA 01821
www.raytheon.com

This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this message
in error, please so advise the sender by reply e-mail and delete this
message. Thank you for your cooperation.











In Reply to Steve Critchley:



Thanks for the replies. It sounds like it's possible to use VS2013, but more trouble than it's worth. I discussed it with my boss, who was fine with getting 2010 now and 2013 when the time comes. Then we discovered that under the business agreement our company has with Microsoft, we can purchase 2013, "downgrade" to 2010 for free, then upgrade back to 2013 for free later. So it's all good.


Have a nice day, everyone!


Original question:


We're about to jump from Wildfire 4 to Creo 2. Some of our Toolkit apps won't run (built with VS 2008), so I'm going to update Visual Studio and rebuild.


PTC specifies VS 2010, but I was wondering if VS 2013 would be OK (rather than buying an old version now, and having to upgrade again for the next version of Creo).


Has anybody tried using a later-than-specified version of Visual Studio, or is that a really bad idea?


Thanks,


Steve


Wildfire 4.0 M220


Creo 2.0 M110


Windows 7 64-bit


Announcements