Skip to main content

Hi,

A customer of ours is currently using Visual COBOL under Visual Studio 2012. We are discussing the possibility of upgrading them to VC 3.0. Because of other constraints the customer can potentially use Visual Studio 2012 or 2015. In order to understand better whether an upgrade of Visual Studio from 2012 to 2015 is worthwhile I would like to find out what differences there are in the developer experience on VS 2015 as compared to VS 2012.

So my question is: What differences there are in the developer experience on VS 2015 as compared to VS 2012 using VC 3.0? Is this documented in a concise way anywhere? If so where can I find that?

Many thanks,

Leigh.


#VisualStudio
#VisualCOBOL

Hi,

A customer of ours is currently using Visual COBOL under Visual Studio 2012. We are discussing the possibility of upgrading them to VC 3.0. Because of other constraints the customer can potentially use Visual Studio 2012 or 2015. In order to understand better whether an upgrade of Visual Studio from 2012 to 2015 is worthwhile I would like to find out what differences there are in the developer experience on VS 2015 as compared to VS 2012.

So my question is: What differences there are in the developer experience on VS 2015 as compared to VS 2012 using VC 3.0? Is this documented in a concise way anywhere? If so where can I find that?

Many thanks,

Leigh.


#VisualStudio
#VisualCOBOL
I have thoughts you might need to bear in mind. If the application is being widely distributed to end users and the executable or entry point DLL's has been recompiled with Visual COBOL 3.0, you might well need to update the end users runtime. For a lot of end user companies this might not be an easy task due to various compliance regulations.

For myself and the way Visual COBOL is used within my environment the differences that I might take advantage of are minor.

It was more important for me, before shipping a newer version of product, to be on the latest development software and runtime, that way I know I'm going to get a 4 year life-cycle window. A new version of product can be deployed with a newer version of the runtime ,as it's all new and the end user accepts compliance testing etc.

Neil

Hi,

A customer of ours is currently using Visual COBOL under Visual Studio 2012. We are discussing the possibility of upgrading them to VC 3.0. Because of other constraints the customer can potentially use Visual Studio 2012 or 2015. In order to understand better whether an upgrade of Visual Studio from 2012 to 2015 is worthwhile I would like to find out what differences there are in the developer experience on VS 2015 as compared to VS 2012.

So my question is: What differences there are in the developer experience on VS 2015 as compared to VS 2012 using VC 3.0? Is this documented in a concise way anywhere? If so where can I find that?

Many thanks,

Leigh.


#VisualStudio
#VisualCOBOL

Did you check the release notes  Of v 3.0

Also the online documentation contains a section "Welcome > Existing Customers: Upgrading from an Earlier Release > New Features" that might be useful.

It's all very brief but it's a start.