| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Support for Visual Studio 2013 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Dave Ziegler |
 Posted: Fri May 02, 2014 10:42 am Post subject: Support for Visual Studio 2013 |
 |
|
Centurion
Joined: 15 Apr 2014
Posts: 118
|
I'm new to IB, we are starting out on V9. I did have VS2012 installed, but recently upgraded to VS2013. MGK mentioned at Impact that VS2013 is not supported yet, and sure enough once I got back and opened VS I noticed my C# templates were gone. I tried recompiling an existing .NET compute node project and can't redeploy.
For the heck of it, I tried running IBM.Broker.DotNet.vsix from C:\Program Files (x86)\IBM\IntegrationToolkit90\wmbt, but it didn't detect a version of VS that it liked and would not proceed.
So two questions, 1) I assume this means I have to keep a version of VS2012 around on this machine, or are there other options? 2) When is "official" support for 2013 coming, is that in V10? |
|
| Back to top |
|
 |
| Simbu |
| Posted: Fri May 02, 2014 5:06 pm Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| VS2013 is not supported in IIB v10.0 Open Beta. you can submit RFE so that IBM may consider it. |
|
| Back to top |
|
|
| DirtyHowi |
| Posted: Thu May 08, 2014 4:45 am Post subject: |
|
|
Novice
Joined: 17 Feb 2014
Posts: 22
|
Yes for initial development you need 2012, fortunately it sits side by side with 2013. I believe once the basic stuff is in place you can then open it with 2013 and work on it same as ever. and it wont even mess up your 2012 version (back to 2010 sp1 this works).
so if you have other devs who have not upgraded (which i cant see why they wouldnt) you can still check things out in 2012 and they will run and compile like 2013 never existed. |
|
| Back to top |
|
|
| Dave Ziegler |
| Posted: Thu May 08, 2014 6:26 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2014
Posts: 118
|
| DirtyHowi wrote: |
Yes for initial development you need 2012, fortunately it sits side by side with 2013. I believe once the basic stuff is in place you can then open it with 2013 and work on it same as ever. and it wont even mess up your 2012 version (back to 2010 sp1 this works).
so if you have other devs who have not upgraded (which i cant see why they wouldnt) you can still check things out in 2012 and they will run and compile like 2013 never existed. |
I don't think you can step into the VS debugger from Toolkit if you're on 2013 though, right? Didn't work for me anyway. |
|
| Back to top |
|
|
| DirtyHowi |
| Posted: Thu May 08, 2014 6:52 am Post subject: |
|
|
Novice
Joined: 17 Feb 2014
Posts: 22
|
i think for that you need to use 2012 to attach to the process so you can step into a .net compute node, otherwise if its a WCF service, making your WSDL point at the localhost version of the service (you run it with break points set) it will halt there.
you should be able to attach to process in 2013, but i'm not sure we ever tried it. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
