- 06 8月, 2016 1 次提交
-
-
由 Neal Gafter 提交于
Similarly for TupleDeconstructionVariableDesignation. Also found many places to handle both kinds of foreach statements.
-
- 21 5月, 2016 1 次提交
-
-
由 lorcanmooney 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 27 8月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 07 7月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 01 7月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 15 1月, 2015 1 次提交
-
-
由 jaredpar 提交于
-
- 14 1月, 2015 1 次提交
-
-
由 RoslynTeam 提交于
-
- 07 1月, 2015 3 次提交
-
-
由 TomasMatousek 提交于
Marks CSharpKind and VBKind extension methods as Obsolete and adds equivalent extension methods Kind for both languages. Marks CSharpKind and VBKind instance methods on language specific syntax nodes Obsolete as well. (changeset 1389494)
-
由 TomasMatousek 提交于
-
由 TomasMatousek 提交于
Marks CSharpKind and VBKind extension methods as Obsolete and adds equivalent extension methods Kind for both languages. Marks CSharpKind and VBKind instance methods on language specific syntax nodes Obsolete as well. (changeset 1388816)
-
- 24 12月, 2014 1 次提交
-
-
由 dustincampbell 提交于
-
- 08 11月, 2014 1 次提交
-
-
由 chandera 提交于
-
- 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)
-
- 02 10月, 2014 1 次提交
-
-
由 AlekseyTs 提交于
-
- 12 7月, 2014 1 次提交
-
-
由 jasonmalinowski 提交于
1) Remove duplicated extension methods to IsKind() and rename everything else to match. 2) Remove extension methods that are unused 3) Remove bizzare ChildNodes<T> which you can just write ChildNodes().OfType<T> in the three places that wanted it. (Most were passing T = SyntaxNode anyways) 4) Delete CommonSyntaxNodeExtensions.cs and move the surviving bits into SyntaxNodeExtensions.cs. (changeset 1295574)
-
- 02 7月, 2014 1 次提交
-
-
由 chandera 提交于
-
- 29 5月, 2014 1 次提交
-
-
由 BalajiKris 提交于
-
- 05 5月, 2014 1 次提交
-
-
由 AlekseyTs 提交于
Migrated state of “Declaration Expressions” implementation equivalent to https://roslyn.codeplex.com/SourceControl/changeset/b7fd08a5695e21cd4d23b8b70815c53656dab65f. (changeset 1249879)
-
- 26 3月, 2014 1 次提交
-
-
由 Pharring 提交于
Fix various typos across the codebase. Mostly in comments, but some in resources and member or variable names. (changeset 1214314)
-
- 23 3月, 2014 1 次提交
-
-
由 Pilchie 提交于
-
- 19 3月, 2014 1 次提交
-
-
由 Pilchie 提交于
-