- 30 11月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
This is a centrally controlled property.
-
由 Jared Parsons 提交于
This setting controls binary deployment hence it needs to be centrally managed to help ensure we have a correct build. Custom projects can continue to control this setting themselves.
-
- 15 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 12 11月, 2016 2 次提交
-
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
Updates the compiler used in the Linux and Mac toolsets and also eliminates the requirement to download the toolset as a zip and instead restores the necessary components over NuGet.
-
- 09 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 08 11月, 2016 9 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Portable unit tests are difficult because as portable libraries they can't truly be built in a runnable fashion. Instead they need a deployment project to provide a runtime on which to delpoy the output of the build. To support running our portable tests on both desktop and CoreClr the build is structured as follows: - Portable tests build w/o deploy to a Dll directory - Desktop delpoyment references all portable tests and outputs to UnitTests\Desktop\Portable - CoreClr deployment references all portable tests and outputs to CoreClrTests This breaks F5 for the moment but gives us the flexibility to restore later.
-
由 Manish Vasani 提交于
Ensure that we set the OptimizationDataFile path after importing the core targets, which sets $(TargetName) that is used by this property.
-
- 05 11月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 04 11月, 2016 4 次提交
-
-
由 Tanner Gooding 提交于
-
由 Kevin Pilch-Bisson 提交于
-
由 Kevin Pilch-Bisson 提交于
-
由 Kevin Pilch-Bisson 提交于
This allows build to succeed at installing the extensions, so that it's possible to debug changes. The wrinkles here are that: 1. SDK's before the RC one don't know how to install on RC. 2. The RC SDK *requires* a <Prerequisites> element 3. The Willow installer fails to install vsixes that have a <Prerequisites> element. To workaround 2 and 3, if we detect that you are building with something before RC, we run an xsl transform to remove the <Prerequisites> element before the SDK uses it. Since our official builds for insertion into Willow are still on VS 2015, they won't have the element.
-
- 03 11月, 2016 1 次提交
-
-
由 Manish Vasani 提交于
-
- 01 11月, 2016 5 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 31 10月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 29 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
VSL is a name no longer relevant to Roslyn. Begining it's removal. This change needs to be comitted first so I can clean up some internal code.
-
- 26 10月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 22 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
TLDR: artifacts are going to move around in Binaries\Debug and the directory is going to get a lot bigger. At a high level build projects can be classified into three categories based on how they write output: - incorrect: a given output path is written to more than once with different contents - less correct: a given output path is written to more than once but always with the same content - correct: a given output path is written to exactly once Today the roslyn build is decidedly “incorrect” as pretty much every file is written directly into Binaries\Debug. This means it ends up writing pretty much every Visual Studio SDK DLL twice: once for Dev14 and once for Dev15. For example at various points in the build Binaries\Debug\Microsoft.VisualStudio.Text.Data.dll may refer to Dev14 and at others it’s Dev15. If this seems like a scary proposition for a build that’s because it is indeed scary and it has real consequences. By now pretty much everyone on the team has hit the build race condition that is dragging down our PRs. The general fix here is to move build outputs into separate directories. Instead of building to $(Configuration) projects now build into say $(Configuration)\Exes\$(MSBuildProjectFileName). This will have a substantial increase in the size of Binaries. We will be looking into ways to reduce that. In the short term though build stability far outweighs the size increase. This change takes us most of the way to "correct". There are several places I had to compromise in order to get this initial change in: - UnitTests still build to a common output folder (one for Dev14, another for Dev15). Pulling unit tests apart is going to take a bit of work. - Every project has a <RoslynProjectType> entry. This will go away in the future for most projects. It's temporarily needed so I can fix roslyn-internal in parallel without taking down the build. - VSL.Imports.targets is messy. Unavoidable for now due to the above. It will get cleaner as I iterate on this. None of these are relevant to the underlying race condition. Hence it's okay to push them off.
-
- 30 9月, 2016 1 次提交
-
-
由 Jason Malinowski 提交于
This won't work anymore. The correct check is in VSL.Versions.targets line 21, which would fire before this anyways.
-
- 22 9月, 2016 1 次提交
-
-
由 Kevin Pilch-Bisson 提交于
-
- 15 9月, 2016 1 次提交
-
-
由 Kevin Halverson 提交于
-
- 11 8月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
Binaries in Roslyn have only three possible signing states: 1. Public signed with Microsoft controlled keys (shipping binaries) 2. Real signed with a full key in the Roslyn repo (non-shipping binaries) 3. Not signed Our build targets still had a lot of dead logic around our old methods which included delay signed binaries. This cleans all of that up and removes some dead variables.
-
- 09 8月, 2016 1 次提交
-
-
由 Kevin Halverson 提交于
-
- 15 7月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
Ensure IBC is running for our official builds. There will be a corresponding update to the Build Definitions to provide the $(IbcMergePath) value.
-
由 Kevin Halverson 提交于
-