- 29 2月, 2020 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 21 2月, 2020 1 次提交
-
-
由 Sam Harwell 提交于
* CodeStyle+Workspaces -> CompilerExtensions * CodeStyle+Features -> Analyzers * CodeStyleFixes+Workspaces -> WorkspaceExtensions * CodeStyleFixes+Features -> CodeFixes
-
- 28 1月, 2020 1 次提交
-
-
由 Sam Harwell 提交于
-
- 24 1月, 2020 1 次提交
-
-
由 Sam Harwell 提交于
-
- 23 1月, 2020 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 18 12月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 20 7月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 19 7月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 22 5月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 10 12月, 2018 1 次提交
-
-
由 dotnet-bot 提交于
-
- 31 7月, 2018 1 次提交
-
-
由 Jason Malinowski 提交于
These can be very confusing, since other methods on Contract actually throw exceptions. Since we have endless amounts of code directly calling Debug.Assert, let's just use it everywhere.
-
- 17 6月, 2017 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 01 3月, 2017 6 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 13 11月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 21 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 07 7月, 2015 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 06 7月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 02 7月, 2015 1 次提交
-
-
由 Jared Parsons 提交于
Fell out of our normal cadence for this during the push for RTM. Now that we had a bit more breathing room getting us back on track here.
-
- 01 7月, 2015 4 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 24 6月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 21 6月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
This helps when producing the 'difference' between intervals trees.
-
- 13 2月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 01 2月, 2015 1 次提交
-
-
由 beep boop 提交于
Background: As discussed in the dev team all hands all code under the GitHub dotnet foundation is using a single process for contribution, API review, infrastructure and coding style. The idea is to present a unified view to our customer and give them a single story for contributing to any project under the dotnet foundation. https://github.com/dotnet/corefx/wiki/Contributing#c-coding-style The coding style transition is automated using a Roslyn based rewrite tool: https://github.com/dotnet/codeformatter This will be applied in stages across our developer tree. Right now the focus is on the Open directory as this is what is being presented on github. Code owners will be contacted before the transition happens. Note: this is a soft style requirement. There are no build errors that come from this change. (changeset 1408227)
-
- 15 1月, 2015 1 次提交
-
-
由 jaredpar 提交于
-
- 14 1月, 2015 1 次提交
-
-
由 RoslynTeam 提交于
-
- 20 11月, 2014 1 次提交
-
-
由 heejaechang 提交于
-
- 19 11月, 2014 1 次提交
-
-
由 heejaechang 提交于
-
- 07 10月, 2014 1 次提交
-
-
由 jasonmalinowski 提交于
This change splits the Workspaces layer into two parts, mirroring the Portable/Desktop split that the compilers did. The core parts of the Workspaces layer (managing documents and projects, formatting, some refactoring, code fixes) is kept in the portable subset, with a few non-portable pieces remaining, notably MSBuild support. This change has a major impact on how MEF now works in Roslyn. Traditional MEF (“MEFv1”) is not portable, and so we must move the Workspaces layer over to using the Microsoft.Composition NuGet package (“MEFv2”) which is. The APIs are distinct in that each has its own namespace, but the concepts are more or less identical. It requires some care though: the workspaces layer is simple in that it only references MEFv2, but higher layers have to reference both versions to use metadata attributes. Exports using metadata attributes from the editor (say, ContentTypeAttribute) must use MEFv1 attributes to export, whereas exports for the workspaces layer must use MEFv2 attributes. The rule is subtle and yet simple, and so a diagnostic is provided which catches any offenses to prevent confusion. This also has some impact in how we create MEF hosts: if you wish to host just the base workspaces layer, we can use MEFv2 to compose everything. The HostServices implementation (MefV1HostServices) that consumes a MEFv1 ExportProvider. If you’re in Visual Studio, you can use this implementation to get the full set of host services provided in Visual Studio. Otherwise, most of the changes in here are minor: we react to some APIs that have been moved/renamed in the portable subset we are targeting, and also align our various exception helper utilities with the compiler’s precedent. (changeset 1349276)
-
- 19 3月, 2014 1 次提交
-
-
由 Pilchie 提交于
-