- 27 3月, 2019 1 次提交
-
-
由 Filip W 提交于
* Analyze nullability in script initializer * C# 8 for scripts for now * nullable context script test * extra null check * added possibility to set c# Language Version on ScriptOptions * adjust tests * added ScriptOptionsTests for C# lang version * adapted tests after rebase * code review changes * fixed test names & resx CDATA * changed the ScriptOptions.WithLanguageVersion error message text and moved it to ScriptingResources.resx * Update CSharpScriptingResources.Designer.cs
-
- 04 5月, 2017 2 次提交
-
-
由 BattleRush 提交于
And minor fix in Scripting resources
-
由 BattleRush 提交于
Resource file schema update from 1.3 to 2.0
-
- 29 12月, 2015 1 次提交
-
-
由 Kevin Halverson 提交于
... in the #help text for csi/vbi.
-
- 04 11月, 2015 1 次提交
-
-
由 Neal Gafter 提交于
-
- 30 10月, 2015 2 次提交
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 10 10月, 2015 1 次提交
-
-
由 Gen Lu 提交于
-
- 24 9月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 17 9月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 15 9月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 30 8月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 30 6月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 10 6月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 01 2月, 2015 1 次提交
-
-
由 ManishJ 提交于
Bug-1116460 : Renaming the scripting assemblies and namespaces. Making corresponding changes in InstallDogfood and RoslynBuildAndTtest to account for new names (changeset 1408119)
-
- 28 1月, 2015 1 次提交
-
-
由 beep boop 提交于
-
- 14 1月, 2015 1 次提交
-
-
由 RoslynTeam 提交于
-
- 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 提交于
-