- 04 3月, 2015 2 次提交
-
-
由 Manish Jayaswal 提交于
-
由 Andy Gocke 提交于
-
- 03 3月, 2015 10 次提交
-
-
由 Neal Gafter 提交于
Fixes #74 Closes #799
-
由 Andrew Casey 提交于
When we try to bind something that is from a not-yet-loaded winmd, we generally see ErrorCode.ERR_DottedTypeNameNotFoundInNS because the namespace Windows.X is only provided by Windows.X.winmd. When this occurs, heuristically ask the debugger for an assembly with name Windows.X and content type AssemblyContentType.WindowsRuntime. The VB equivalent of ERR_DottedTypeNameNotFoundInNS is ERR_NameNotMember2. However, VB also has a second error code to consider: ERR_UndefinedType1, which is only produced in type-only contexts. Since the argument to ERR_UndefinedType1 is the qualified name, as a string, we have to do some extra work to determine the next part that needs to be resolved. Caveat: This doesn't work end-to-end (DevDiv #1130191).
-
由 Brett Forsgren 提交于
-
由 Andrew Casey 提交于
-
由 Charles Stoner 提交于
-
由 Andrew Casey 提交于
The expression compiler returns information to the debugger in the form of .NET assemblies. These assemblies should not contain embedded declarations (i.e. "My.*"). At best, these declarations are useless. At worst, they hide the declarations in the user's own assembly. As a bonus, this fixes an issue we were having with being unable to compile the embedded declarations in cases where two copies of EditorBrowsableAttribute were loaded (since neither is "closer" or more accessible while debugging). Fixes #946.
-
由 VSadov 提交于
The file locking cannot be consistently guaranteed on multiple platform, on remote files, when builds share process via compile server vs. running separately. Besides we are unable to handle sharing conflicts regardless, so at best the locking was serving only diagnostical purposes.
-
由 Brett Forsgren 提交于
-
由 Andrew Casey 提交于
-
由 Charles Stoner 提交于
-
- 01 3月, 2015 1 次提交
-
-
由 AdamSpeight2008 提交于
-
- 28 2月, 2015 13 次提交
-
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
由 Heejae Chang 提交于
more clean up after feedback
-
由 Andy Gocke 提交于
This change brings back the SimpleMSBuild test, which sets up a "hello world" C#+VB solution and builds it using msbuild using the build task. Two build-task-specific tests have also been added, which directly load and call execute on the Csc and Vbc tasks. Closes #866.
-
由 Heejae Chang 提交于
some code clean up - rename and such
-
由 Neal Gafter 提交于
Fixes #223
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
由 Balaji Soundrarajan 提交于
Fixes #725: 'this' keyword should be available in the completion list, in the context of member expression body.
-
由 Neal Gafter 提交于
Replace many uses of uint which are unwrapped string indices with StringIdx, the wrapped form, for type safety.
-
由 Vladimir Reshetnikov 提交于
-
由 Vladimir Reshetnikov 提交于
-
由 beep boop 提交于
Been almost a month since the code formatter was run so this change was a bit larger than would be expected for a normal (weekly) update. Diffs mostly around: - Whitespace changes - Missing copyright headers - Missing visibility modifiers
-
- 27 2月, 2015 14 次提交
-
-
由 Heejae Chang 提交于
-
由 Heejae Chang 提交于
all tests passing. now StateManager owns all state related operation.
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
由 Andrew Casey 提交于
The problem arises when more than one expansion shares the same value - for example, those parented by a common AggregateExpansion. Since this is an optimization anyway (the debugger would eventually close them on its own), we'll just conservatively focus on data items without children. Fixes #901.
-
由 David Poeschl 提交于
Allow navigation to metadata definitions in the Find Symbol Results window.
-
由 Balaji Soundrarajan 提交于
Fix #872 : Indent appropriately on Enter inside InterpolatedVerbatimString If the Return is issued in the context of the InterpolatedString, the next line is placed at the column 0 If the Return is issued inside the Interpolated syntax of the InterpolatedVerbatimString then place the next line accordingly to the indentation rule
-
由 Jason Malinowski 提交于
-
由 Ravi Chande 提交于
Completion on backspace uses the caret position to determine if it should trigger, which involves inspecting the subject buffer. It did not map the text view caret position onto the subject buffer position. This resulted in crashes in projection scenarios when the surface buffer was longer than the subject buffer.
-
由 Brett Forsgren 提交于
-
由 Jared Parsons 提交于
Add stack guards for the ParseExpression and ParseStatement calls. These are other public entry points into the parser which needed to be guarded in the same way as ParseSyntaxTree. close #839 close #848
-
由 Jared Parsons 提交于
The MSBuild workspace code should respect the ReferenceOutputAssembly flag. Before only the C# implementation of MSBuild was doing so. Now all implementations will properly respect the flag. closes #900 closes #909
-
由 Ravi Chande 提交于
Automatic brace completion of "(" parses as a cast, but the user might be trying to type a parenthesized expression.
-