Visual Studio 2015 Update 2 was released just days after we switched
automation from VS2013 to VS2015 Update 1. We know we were going to take
Update 2 eventually and we didn't want to run a Windows toolchain for as
short as a single release, so we just landed the switch from VS2015 Update
1 to Update 2 on inbound. This means we should never ship a Firefox dev
edition, beta, or release using VS2015 Update 1: we'll go from 2013 to
2015u2.

You may want to take the time to upgrade to VS2015 Update 2 so your local
builds match automation. If you run the Visual Studio 2015 installer, it
should auto update an out-of-date installer then prompt you to update
out-of-date packages. There's a "Tools (1.3.1 and Windows 10 SDK
(10.0.10586)" update under "Windows and Web Development" -> "Universal
Windows App Development Tools" *that was released after VS2015 Update 2 was
initially released*. This contains some minor Windows SDK updates and a
UCRT rebuild and is the version automation is now running. So even if you
are running VS2015u2, you may not have this "Tools 1.3.1" update and may
not match automation. It's probably worth 2 minutes of your time to run the
installer to double check everything matches.

Bug 1259782 if anyone has problems.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to