- 23 11月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
Internal APIs are aligned with these public APIs. VB Symbol Display for ByRef returns is adjusted according to the latest design decision.
-
- 21 11月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 17 11月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
-
- 04 11月, 2016 1 次提交
-
-
由 VSadov 提交于
Fixes:https://github.com/dotnet/roslyn/issues/14334
-
- 06 5月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
- Added support for properties and events in tuple type symbol. - Made additional adjustments to implementation of tuple symbol display around presence of element names.
-
- 04 5月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
- Substitute underlying type with corresponding tuple type at the point of type reference. - Adjusted implementation of symbol display to account for presence of names in the extension tuples. - Implemented proper retargeting for tuple types (multi-targeting support).
-
- 28 4月, 2016 1 次提交
-
-
由 Julien 提交于
-
- 18 6月, 2015 1 次提交
-
-
由 bkoelman 提交于
-
- 24 2月, 2015 1 次提交
-
-
由 Dennis Fischer 提交于
Add docs for ISymbol and its derived interfaces that say that they should not be implemented outside Roslyn
-
- 25 1月, 2015 1 次提交
-
-
由 jaredpar 提交于
These were accidentally changed to UTF-16LE during a recent scripted change. This went unnoticed because the encoding change didn't register in CodeFlow (indeed if you view a shelve of this change in CodeFlow it will report no changes). UTF-16 does not work well with Git as it is often interpreted as a binary file. Moving back to UTF-8 so our GitHub experience works well for customers. closes #66 (changeset 1403787)
-
- 24 1月, 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 1403394)
-
- 15 1月, 2015 1 次提交
-
-
由 jaredpar 提交于
-
- 14 1月, 2015 1 次提交
-
-
由 RoslynTeam 提交于
-
- 20 6月, 2014 1 次提交
-
-
由 TomasMatousek 提交于
Splits Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.CSharp and Microsoft.CodeAnalysis.VisualBasic into portable and desktop assemblies. Existing Core\Source, CSharp\Source and VisualBasic\Source directories are renamed to Core\Portable, CSharp\Portable and VisualBasic\Portable. New sibling Desktop folders are added and non-portable source is moved there. "System.Runtime" references has to be removed in order for the portable project system magic to automatically add facade references. (changeset 1281686)
-
- 25 3月, 2014 1 次提交
-
-
由 AlekseyTs 提交于
-
- 21 3月, 2014 1 次提交
-
-
由 AlekseyTs 提交于
Public API Change: Rename IFieldSymbol.AssociatedPropertyOrEvent , IMethodSymbol.AssociatedPropertyOrEvent and INamedTypeSymbol. AssociatedEvent APIs to AssociatedSymbol to accommodate for future language changes. (changeset 1210026)
-
- 19 3月, 2014 1 次提交
-
-
由 Pilchie 提交于
-