- 01 5月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
This is an automated migration of our project files to the new SDK / PackageReference. It is done using the tool located here: https://github.com/jaredpar/ConvertPackageRef
-
- 07 4月, 2017 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 15 3月, 2017 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 20 2月, 2017 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 31 12月, 2016 3 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
- 29 12月, 2016 4 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
- 02 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 01 11月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 31 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 28 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 26 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 24 10月, 2016 2 次提交
-
-
由 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
-
- 02 9月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 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.
-
- 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 次提交
-
-
由 Tomas Matousek 提交于
-
- 13 7月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 07 7月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 24 6月, 2016 1 次提交
-
-
由 gafter 提交于
-
- 15 6月, 2016 1 次提交
-
-
由 Tanner Gooding 提交于
-
- 30 4月, 2016 2 次提交
-
-
由 Tomas Matousek 提交于
-
由 Tomas Matousek 提交于
-
- 25 4月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 21 4月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
This reverts commit 7debfc47.
-
- 20 4月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 16 4月, 2016 1 次提交
-
-
由 David Kean 提交于
To prevent projects across the tree from having different dependencies, we unify external package dependencies by creating empty C# projects that represent them. We then make use of project.json package inheritance (where a project inherits all packages dependencies from their dependencies) to unify it across the tree. No projects outside of this tree, should be directly referencing versions of these dependencies manually. For this check-in I've tackled Metadata, Reflection, and DiaSymReader. Will tackle the rest in future commits.
-
- 04 3月, 2016 2 次提交
-
- 02 3月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
This reverts commit 7bb0b4ea.
-
- 01 3月, 2016 1 次提交
-
- 24 2月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-