Proposed end of support for Microsoft Visual Studio 2005 (VC8)


Frank Quinn <fquinn.ni@...>
 

Hi Folks,

Does anyone have any objections to ending support for Visual Studio 2005 for OpenMAMA? There are several reasons for wanting to do this:

1. Visual Studio 2005 is 10 years old
2. It is out of mainstream support from Microsoft
3. We are limited to Visual Studio 2005 Solution file syntax to maintain backwards compatibility
4. We suspect none of our users or developers actually using it

Cheers,
Frank


Alpert, Reed <reed.alpert@...>
 

HI,

 

We don’t use VS2005, but do build with 2012 and soon 2013.

We also have some interest in 2008, but haven’t gone down that road yet.

 

Thanks,

 

Reed.

 


Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...

 

 

From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Frank Quinn
Sent: Saturday, October 10, 2015 7:45 AM
To: openmama-dev
Subject: [Openmama-dev] Proposed end of support for Microsoft Visual Studio 2005 (VC8)

 

Hi Folks,

 

Does anyone have any objections to ending support for Visual Studio 2005 for OpenMAMA? There are several reasons for wanting to do this:

 

1. Visual Studio 2005 is 10 years old

2. It is out of mainstream support from Microsoft

3. We are limited to Visual Studio 2005 Solution file syntax to maintain backwards compatibility

4. We suspect none of our users or developers actually using it

 

Cheers,

Frank

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.