- 17 12月, 2016 3 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
- 15 9月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 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 4月, 2016 2 次提交
-
-
由 Tomas Matousek 提交于
-
由 Tomas Matousek 提交于
This reverts commit 31377ce7.
-
- 20 4月, 2016 2 次提交
-
-
由 Tomas Matousek 提交于
Update TargetFrameworkVersions.
-
由 David Kean 提交于
-
- 04 11月, 2015 1 次提交
-
-
由 Neal Gafter 提交于
-
- 24 10月, 2015 1 次提交
-
-
由 Jason Malinowski 提交于
With Visual Studio 2015 Update 1 you should not specify -anycpu in the runtimes section. Right now we'll have both to allow us to build with and without Update 1, and we'll remove the old ones once we've made the transition. Update 1 also tries deploying implementations for some class libraries, so I'm updating all our test and VSIX deployment class libraries to now include implementations.
-
- 18 10月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 13 10月, 2015 1 次提交
-
-
由 Tanner Gooding 提交于
-
- 10 10月, 2015 1 次提交
-
-
由 Jared Parsons 提交于
-
- 03 9月, 2015 1 次提交
-
-
由 Andy Gocke 提交于
-