- 20 6月, 2014 40 次提交
-
-
由 BalajiKris 提交于
Devdiv:756226 - Quick info for Await Keyword. Devdiv:756337 - (awaitable) not displayed for types that implement the awaiter pattern. Roslyn behavior now models after Dev12, which 1. shows the type of the await expression in quick info for the Await keyword 2. appends an <Awaitable> prefix if the expression is further awaitable. i.e., it has a type of Task or Task<T> or any type that has a valid GetAwaiter method. Since the changes are shared code, VB also inherits this behavior and shows semantic type information. But, in Dev12, VB shows syntactic help for Await keyword in quick info (Await <expression>). Syntactic quickinfo for keywords are Not yet implemented in Roslyn (user story: 522342). I have added tests to document the current behavior and leave the behavior as such until we implement 522342, when we can decide what the quick info text should be like for VB Await keyword (syntactic or semantic or both)... (changeset 1278712)
-
由 TomasMatousek 提交于
-
由 angocke 提交于
-
由 TomasMatousek 提交于
Replace usage of TypeCode throughout VB code base with SpecialType. TypeCode isn't available in portable profile. (changeset 1278340)
-
由 jasonmalinowski 提交于
-
由 Kevin_H 提交于
This prevents callers from needing to special case DateTime and add them on themselves if they need the formatted literal to re-parse as a valid Date literal (the most common case for callers of this API). (changeset 1277604)
-
由 angocke 提交于
-
由 acasey 提交于
Port EEMethodSymbol to VB and eliminate EEParameterSymbol from both languages (just use SynthesizedParameterSymbol). Bonus: Fix a couple typos. (changeset 1277348)
-
由 TomasMatousek 提交于
-
由 TomasMatousek 提交于
Removes IFieldDefinition.FieldMapping that returned ISectionBlock -- the only section the writer is writing data into is .text, so it suffice to return ImmutableArray<byte> containing the data. Deletes ISectionBlock since it hasn't been used elsewhere. Reduces the amount of state stored on PEWriter. (changeset 1277226)
-
由 AlekseyTs 提交于
-
由 angocke 提交于
Log die timeout in the compiler server and any failures associated with reading the app.config file. (changeset 1276486)
-
由 manishv 提交于
Ensure that we don't add duplicate file keys into analyzerAssemblyKeys list. (changeset 1276230)
-
由 TomasMatousek 提交于
-
由 ChuckStoner 提交于
-
由 Basoundr_ms 提交于
Smart Indenter was not handling all the cases, where the return is pressed twice after a comment The existing case handles only the case where the caret is immediately followed a token which also happens to be the end of an indent operation. The cases that are added: The premise in these cases is, the user has pressed 2 returns after a comment 1. There are executable code after the caret which also belong to the same indent block as the caret Behavior : Place the caret at the column where the other executable statements of the block are placed. Eg: static void Main(string[] args) { // A // B $$ return; } 2. Inside an initializer block with the previous token being the comma token of the separation list Behavior - Place the caret at the column where the previous argument to the list started Eg: var s = new List<string> { "", "",/*sdfsdfsdfsdf*/ // dfsdfsdfsdfsdf $$ }; (changeset 1276027)
-
由 angocke 提交于
Resolves bug 946954. (changeset 1275447)
-
由 TomasMatousek 提交于
Move facade references resolution to MetadataReferenceProvider and override it in desktop implementation (MetadataFileReferenceProvider). (changeset 1275410)
-
由 angocke 提交于
The VBCSCompiler, rvbc, and BasicCommandLineTest projects were all incorrectly building as x86 instead of Any CPU. (changeset 1275381)
-
由 AlekseyTs 提交于
-
由 TomasMatousek 提交于
Move AssemblyMetadata.CreateFromFile and ModuleMetadata.CreateFromFile to a separate type (MetadataFileFactory). We need to move non-portable code to a separate assembly, so these APIs can't be on AssemblyMetadata/ModuleMetadata which are portable. (changeset 1275365)
-
由 manishv 提交于
Add msbuild workspace support to load analyzer assemblies specified in the project file. This change is conditioned around presence of correct msbuild version referenced by workspaces projects. (changeset 1275262)
-
由 cyrusn 提交于
***NO_CI*** (changeset 1275257)
-
由 TomasMatousek 提交于
-
由 TomasMatousek 提交于
Move serialization from CompilationOptions and ParseOptions to dedicated SerializableCompilationOptions and SerializableParseOptions wrappers. (changeset 1274332)
-
由 heejaechang 提交于
-
由 TomasMatousek 提交于
The underlying debugger issue has been fixed, so the calls are not needed anymore. (changeset 1274269)
-
由 Kevin_H 提交于
Add IVT for VB EE (ResultProvider) and change .targets so we don't "Import System.Linq" in projects that target .NET 2.0. (changeset 1274168)
-
由 chandera 提交于
-
由 mattwar 提交于
Change CommandLineParser (and related types) so that all reference computations are accessible via public API's. Change ProjectFileLoader to use CommandLineParser to compute same references as command line compiler. (changeset 1274050)
-
由 AlekseyTs 提交于
More: - Skip checked/unchecked expressions (similar to parenthesized) when we are trying to determine if Declaration Expression is used as an argument. - Fixes/unit-tests for SemanticModel APIs when Declaration Expressions are used inside an “expression bodied” property. (changeset 1273421)
-
由 manishv 提交于
Port changeset 1271826 from C# to VB (Add light bulb support for adding global and local SuppressMessageAttributes for warning and info diagnostics) (changeset 1273323)
-
由 chandera 提交于
If you try to GTD on a global import alias declared in a VB project file, we null ref. This happens because the compiler synthesizes a SyntaxTree for that imports statement, but we assume that all symbols that have Locations have Locations in the current Solution. To avoid this, detect if the caret is on a alias with no locations in the solution, and in that case, GTD on the target instead. (changeset 1272875)
-
由 jmarolf 提交于
The original bug had us trying to contruct a new method M in the scenario below. using System.Collections.Generic; class C { void M(IEnumerable<C> c) { new C().M((a,b) => c.Add) } } because c.Add doesn't exist we get null and pass it through, causing problems. The GFU service could attempt to query the candidate symbols and try to find a reasonable resolution, but in this case there is none. Note: This scenario cannot happen in VB currently. VB and C# return different candidate symbols for the same case so: Imports System.Collections.Generic Class C Sub M(args As IEnumerable(Of C)) Dim tmp = New C() tmp.M(Function(a, b) AddressOf args.Add) End Sub End Class does not have the necessary information for us to begin method generation. Filed Bug #960755 (changeset 1272810)
-
由 AlekseyTs 提交于
-
由 manishv 提交于
Address CR feedback for changeset 1272615 (Handle analyzer type load failures in a better way): Change the newly added diagnostic's severity to be an info rather than a warning. (changeset 1272711)
-
由 manishv 提交于
Handle analyzer type load failures in a better way: If Assembly.LoadFrom throws a ReflectionTypeLoadException, our current behavior is to log a compiler warning and skip the analyzer assembly. However, this exception might be caused by some unrelated missing types in referenced assemblies and it is possible to continue looking for analyzers from the loaded types in the assembly. This change tweaks the behavior to now log a separate warning for a ReflectionTypeLoadException, and continues working with only the loaded types. (changeset 1272615)
-
由 acasey 提交于
Expression Evaluator Restructuring Change Description: Rename assemblies, namespaces, and folders Microsoft.CodeAnalysis.ExpressionEvaluator.ExpressionCompiler.dll [Shared ResultProvider dll not yet created] Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator.ExpressionCompiler.dll Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator.ResultProvider.dll Microsoft.CodeAnalysis.VisualBasic.ExpressionEvaluator.ExpressionCompiler.dll [VB ResultProvider dll not yet created] Roslyn.ExpressionEvaluator.CSharp.ExpressionCompiler.dll Roslyn.ExpressionEvaluator.VisualBasic.ExpressionCompiler.dll Roslyn.ExpressionEvaluator.CSharp.ResultProvider.dll [VB ResultProvider test dll not yet created] TODO: Address CR feedback separately. (changeset 1272594)
-
由 dpoeschl 提交于
Update how the Syntax.xml.Generated.* files are included into the *CompilerSyntaxTests projects to eliminate build warnings in VS. They previously specified a <Link> location which now causes warnings due to recent build process restructuring changing the $(IntermediateOutputPath) location changing to be within the project directory. This change removes these <Link>s. (changeset 1272548)
-
由 jasonmalinowski 提交于
-