PDA

View Full Version : Vsta 4.0



matteo.fabbri
30th January 2014, 14:19
Do you have any plans to update VSTA 2012 that support framework 4.5?

Visual Studio Tools for Applications 2012
http://www.microsoft.com/en-us/download/details.aspx?id=38806

Matteo

zenmyway
31st January 2014, 11:10
Do you have any plans to update VSTA 2012 that support framework 4.5?

Visual Studio Tools for Applications 2012
http://www.microsoft.com/en-us/download/details.aspx?id=38806

Matteo

This question is very important also for our company.
Waiting the COPA-DATA replay.
Bye
Gabriele

martins
31st January 2014, 18:19
hi,

the problem there is that Microsoft does no longer ship an IDE together with VSTA 2012 - see this:

http://social.msdn.microsoft.com/Forums/vstudio/en-US/61879c62-6f39-43e6-be75-0f84ccfa3f2b/vsta-debugging-without-visual-studio?forum=vsta

This would mean that we either have to ship zenon Supervisor licenses together with a full-priced Visual Studio (which would increase the price by a lot!) or not to ship any IDE at all, meaning that the customer would not be able to use VSTA out of the box without installing Visual Studio himself. This also takes the possibility of debugging VSTA code on a runtime PC (or buy a seperate Visual Studio license for debugging code on a runtime).

We are aware of this and we are thinking of a solution. This however is the reason why we stick to VSTA 2.0 for now.

Just because I am curious: why do you need .NET Framework 4 / 4.5 support?

Best regards,
Martin

tsragland
3rd February 2014, 18:38
Martin,

I can think of two reasons .NET 4.0 and 4.5 are important...

1) Asynchronous programming - http://msdn.microsoft.com/en-us/library/vstudio/hh191443(v=vs.110).aspx

2) I am using third party controls which require .NET 4.0 at minimum. As more time passes, I'm sure there will be more users facing this limitation.

The newer versions of the .NET Framework also have the new 'Parallel' class, which is very useful. http://msdn.microsoft.com/en-us/library/system.threading.tasks.parallel(v=vs.100).aspx

Regarding debugging, and the need for a full version of Visual Studio, I think one takes care of the other. I use Visual Studio Professional to debug my user controls, for example. Visual Studio Professional can be used to debug in the following two ways:

1) In the 'Debug' tab of the project properties in Visual Studio Professional, you can set the 'Start Action' to the radio button option, 'Start external program', and set the path to zenrt32.exe.

2) In the 'Debug' menu of Visual Studio Professional, you can use the menu item 'Attach to Process'

I guess the difficulty comes with pricing/distribution of the full version of Visual Studio, and documenting the different ways to debug.

But, where there's a will, there's a way. Right? ;-)