On 2014-02-26, 4:11 PM, Cameron McCormack wrote:
Ted Mielczarek wrote:
Historically we haven't updated toolchains without a pressing reason,
since there's a lot of hassle involved. Is there a specific reason
you're asking?
The two recent things I have had to work around in VS2010 were bugs in
Ted Mielczarek wrote:
Historically we haven't updated toolchains without a pressing reason,
since there's a lot of hassle involved. Is there a specific reason
you're asking?
The two recent things I have had to work around in VS2010 were bugs in
handling sized enums > 32 bits (enum Blah : uint6
On Wed, Feb 26, 2014 at 6:58 AM, Ted Mielczarek wrote:
> On 2/26/2014 2:15 AM, Cameron McCormack wrote:
> > When do we plan to drop support for Visual Studio 2010? I remember at
> > one point that it was not possible to generate builds that ran on
> > Windows XP with
On 2/26/2014 2:15 AM, Cameron McCormack wrote:
> When do we plan to drop support for Visual Studio 2010? I remember at
> one point that it was not possible to generate builds that ran on
> Windows XP with VS2010, but Update 1 (released in November) added
> support for that.
&g
Cameron McCormack wrote:
When do we plan to drop support for Visual Studio 2010? I remember at
one point that it was not possible to generate builds that ran on
Windows XP with VS2010, but Update 1 (released in November) added
support for that.
Not possible to generate builds that ran on
Cameron McCormack wrote:
When do we plan to drop support for Visual Studio 2010? I remember at
one point that it was not possible to generate builds that ran on
Windows XP with VS2010, but Update 1 (released in November) added
support for that.
November 2012, that is
When do we plan to drop support for Visual Studio 2010? I remember at
one point that it was not possible to generate builds that ran on
Windows XP with VS2010, but Update 1 (released in November) added
support for that.
___
dev-platform mailing list
7 matches
Mail list logo
