- 29 12月, 2016 3 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
- 28 12月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 22 12月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
This property is controlled by our central build targets. It shouldn't be used in indivdidual projects anymore as it can lead to bugs. See the following PR from @KirillOsenkov for an example of how this leads to bugs https://github.com/dotnet/roslyn/pull/15880
-
- 17 12月, 2016 3 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
- 16 12月, 2016 1 次提交
-
-
由 Tanner Gooding 提交于
-
- 30 11月, 2016 4 次提交
-
-
由 Andrew Arnott 提交于
-
由 Andrew Arnott 提交于
I'm spreading goodness both directions so that the best of both are everywhere, and all copies of these files are identical.
-
由 Andrew Arnott 提交于
An extra space would have broken its functionality. The template doesn't share this bug. It is unique to the samples.
-
由 Andrew Arnott 提交于
-
- 23 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
The dependency projects were added as a way to help unify our project.json references. Instead of every project referencing the NuGet package, we had a dependency project which referenced it and everyone referenced that dependency project. Due to the transitive nature of NuGet it would be roughly equivalent. This system had a number of downsides: 1. There was no enforcement. Even though dependency projects existed, there was no mechanism to force developers to use them. 2. Getting the granularity correct was tricky. 3. The projects themselves have special props / targets to get them to produce no output. This can trip up MSBuild up to date checks. Since then though we've begun using RepoUtil to verify our NuGet reference correctness. This removed the need for these projects and hence I'm removing them from our build.
-
- 08 11月, 2016 4 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 05 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 04 11月, 2016 1 次提交
-
-
由 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.
-
- 02 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 31 10月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 29 10月, 2016 1 次提交
-
-
由 Kevin Pilch-Bisson 提交于
This reverts commit 8115c019.
-
- 28 10月, 2016 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 27 10月, 2016 2 次提交
-
-
由 Kevin Pilch 提交于
-
由 Jared Parsons 提交于
-
- 24 10月, 2016 5 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
This should either be defined globally or not at all. Repeating all the logic on a local level is just wasted time.
-
由 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.
-
- 24 9月, 2016 1 次提交
-
-
由 Andy Gocke 提交于
This change drops support for .NET 4.5 and retargets to desktop 4.6 + CoreCLR. It also fixes up various analyzer warnings that were created due to the move. Fixes #12926
-
- 17 8月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
The ImportGroup element is just noise. It was also used very inconsistently in the repo and often within the same project file. Just remove it.
-
- 05 8月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 02 8月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
The dependency projects serve a few purposes: - Help ensure package unity by serving as a single place for a NuGet reference. - Make NuGet updates simple by having a single place to change. - Grouping together related packages to make it easy to take a dependency on say Visual Studio editor. The first two points are largely obsolete now that our project.json references are strictly validated on every build and have a single update mechanism. This meant a lot of our depnedency projects were just making Roslyn.sln bigger. As such I went through and deleted all of them which had only 1 or 2 project.json entries. I left the VS ones which tend to group 10+ references together. They are still serving a valid "reference VS" purpose.
-
- 21 7月, 2016 1 次提交
-
-
由 Manish Vasani 提交于
* Enable building and testing on machines with only Dev15 Preview 3 installed 1. Auto-detect the VS common tools path 2. Convert analyzer samples to import Roslyn targets 3. Ensure dependencies are copied to the output directory 4. Workaround: Use local Microsoft.Net.Compilers.props until we move to a compiler toolset with https://github.com/dotnet/roslyn/commit/05c12ebfcdd08a02dbceded5327a8da7a7df23be 5. Replace references to Microsoft.VisualStudio.ComponentModelHost.dll (VisualStudioReferenceAssemblyVersion) with a nuget reference to RoslynDependencies.Microsoft.VisualStudio.ComponentModelHost 6. Add nuget references to Roslyn.Microsoft.Build, Roslyn.Microsoft.VisualStudio.ExtensionManager, RoslynDependencies.Microsoft.VisualStudio.Diagnostics.PerformanceProvider and RoslynDependencies.Microsoft.VisualStudio.CodeAnalysis.Sdk.UI. * Remove workaround now that new NuGet packages have been uploaded to nuget.org * Remove preprocessor directive MSBUILD12 and its references
-
- 25 6月, 2016 1 次提交
-
-
由 Manish Vasani 提交于
Fixes #11442
-