- 19 2月, 2020 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Clean up string resources, use Arcade resx generator * CodeLens resources * Use NET20 instead of NETFX20
-
- 23 1月, 2020 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 02 5月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Remove RoslynProjectType * Remove ToolsVersion, namespace from Project tags * Remove updating of MSBuildAllProjects * Update BuildBoss * Delete DeployTooolsetCompiler
-
- 19 1月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
-
- 11 12月, 2018 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Remove RuntimeIdentifier specification * Arcade directory layout
-
- 04 12月, 2018 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Use Arcade testing targets * Skip CodeStyle tests on Mono * Include net472 in test target frameworks for Mono * Remove incorrect file existence check. * Update ADO integration test yaml
-
- 02 11月, 2018 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 13 9月, 2018 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Move xunit package references to Roslyn.Toolsets.Xunit.targets * Remove dependency on Microsoft.NET.Test.Sdk
-
- 19 7月, 2018 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 17 7月, 2018 1 次提交
-
-
由 Jared Parsons 提交于
-
- 11 7月, 2018 1 次提交
-
-
由 Andy Gocke 提交于
The C# syntax tests were missing a reference to xunit.runner.visualstudio which prevented them from working in the Test Explorer in 15.8 Preview. Rather than just adding a reference to this one test, I've added a reference to the root test utilities project, that almsot every test references, and deleted the explicit references in the test leaf projects. This should hopefully be a more robust method of using the XUnit VS test adapter.
-
- 20 6月, 2018 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Use Microsoft.SourceLink.GitHub 1.0.0-beta-63001-01 * Workaround XAML bug * Fix CommitHashAttribute * Update compiler package to 2.9.0-beta7-63018-03 * SymLink .git directory for 2nd deterministic build
-
- 18 5月, 2018 1 次提交
-
-
由 Tomáš Matoušek 提交于
Even though Roslyn can only every be deployed where at least net461 or netcoreapp2.0 is available Roslyn cannot depend on netstandard2.0 assemblies. This is due to the setup of Visual Studio which has a minimum target of net46 and hence only deploys netstandard1.3 facades. In order to prevent netstandard2.0 versions of NuGet references to deploy, at build or test, we must limit the desktop target framework used in our projects to net46. There is nothing functionally wrong with having our tests target net461. At the same time though it would mean our tests were running against the netstandard2.0 version of references, such as System.Collections.Immutable, which is not what we deploy against. Hence not testing what we ship which creates a small but real hole.
-
- 21 3月, 2018 1 次提交
-
-
由 Neal Gafter 提交于
-
- 05 3月, 2018 1 次提交
-
-
由 Jared Parsons 提交于
-
- 09 2月, 2018 1 次提交
-
-
由 Gen Lu 提交于
-
- 19 12月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
-
- 07 12月, 2017 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Many of our VB projects today rely on having an empty default namespace and explicitly specifying the full namespace in source. In the new SDK / dir props world this can only be done by explicitly marking the namespace as empty in the project file. Can't do the centralized control that we do today.
-
- 15 11月, 2017 1 次提交
-
-
由 Ashley Hauck 提交于
-
- 14 11月, 2017 1 次提交
-
-
由 Ashley Hauck 提交于
-
- 01 9月, 2017 2 次提交
-
-
由 Jared Parsons 提交于
These projects reference the compiler EXE projects and hence copy them to the output directory. This appears to not cause the correct app.config file (ex csc.exe.config) to be copied along with it. It's missing the necessary binding redirects that are generated from a direct compile of the project. As a result when it' invoked from the unit tests it fails. It's possible this is a SDK bug and I will dig into that. For now though I need to unblock the suites.
-
由 Jared Parsons 提交于
This primarily moves us to the 2.2.0 version of xunit. In order to make that transition though a number of other changes needed to happen as well: 1. Needed to move our desktop target to 4.6.1. This should've been required some time ago but we were essentially depending on bugs in the SDK / NuGet. 1. Remove the DeployCoreClrTestRuntime project. This entire idea depended on having the xunit.console.netcore package. This has since been deleted and doesn't work with the 2.0 SDK. 1. Remove the deploy compiler tools project. Can just use dotnet exec now and that's much more efficient. 1. Resolve a new ambiguity with KeyValuePair. A helper of ours now exists in netcoreapp2.0. I fully expect a number of Jenkins legs to fail with this change: build correctness, coreclr and ubuntu. But I want to validate our other legs and am still trackind down answers needed to fix the others.
-
- 26 7月, 2017 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 11 7月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
In the new SDK we no longer have a need for ProjectGuid. This change will: - Remove ProjectGuid from project files - Remove Name + Project items from ProjectReference entries - Change BuildBoss to enforce both of these items
-
- 04 7月, 2017 2 次提交
-
-
由 Srivatsn Narayanan 提交于
-
由 Srivatsn Narayanan 提交于
-
- 03 7月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 01 7月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
-
- 28 6月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
Migrated the remainder of our code base to use the new SDK via the ConvertPackageRef tool. https://github.com/jaredpar/ConvertPackageRef
-
- 09 5月, 2017 2 次提交
-
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
- 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
-
- 02 2月, 2017 1 次提交
-
-
由 Jared Parsons 提交于
This project is no longer necessary. It used to help us get TDD working fine in Visual Studio. That's no lonegr needed with the recent build cleanup. TDD still functions with this project removed.
-
- 31 12月, 2016 4 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-
- 29 12月, 2016 2 次提交
-
-
由 Tanner Gooding 提交于
-
由 Tanner Gooding 提交于
-