Skip to content

Commit 21a413a

Browse files
authored
Merge pull request #681 from MicrosoftDocs/FromPublicMaster
Confirm merge from FromPublicMaster to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
2 parents e4f6b34 + 9881349 commit 21a413a

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/debugger/intellitrace-features.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ You can use IntelliTrace to record events and method calls your application, whi
6262
This isn't enabled by default, but IntelliTrace can record method calls along with events. To enable collection of method calls go to **Tools > Options > IntelliTrace > General**, and select **IntelliTrace events and call information**.
6363

6464
> [!NOTE]
65-
> Call information is not currently available for ASP.NET Core apps.
65+
> Call information is not currently available for .NET Core apps.
6666
6767
This lets you see the call stack history and step backward and forward through calls in your code. IntelliTrace records data such as method names, method entry and exit points, and certain parameter values and return values.
6868

@@ -128,4 +128,4 @@ You can use IntelliTrace to record events and method calls your application, whi
128128
## Videos
129129
[IntelliTrace Experience](https://channel9.msdn.com/Series/Visual-Studio-2015-Enterprise-Videos/IntelliTrace-Experience)
130130

131-
[Historical Debugging with IntelliTrace in Microsoft Visual Studio Ultimate 2015](https://channel9.msdn.com/events/Ignite/2015/BRK3716)
131+
[Historical Debugging with IntelliTrace in Microsoft Visual Studio Ultimate 2015](https://channel9.msdn.com/events/Ignite/2015/BRK3716)

docs/extensibility/roslyn-analyzers-and-code-aware-library-for-immutablearrays.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ You can drag the yellow execution pointer on the left side of the editor window.
176176
**Get the object creation expression's type.** "Type" is used in a few ways in this article, but this means if you have "new Foo" expression, you need to get a model of Foo. You need to get the type of the object creation expression to see if it is the ImmutableArray\<T> type. Use the semantic model again to get symbol information for the type symbol (ImmutableArray) in the object creation expression. Enter the following line of code at the end of the function:
177177

178178
```csharp
179-
var symbolInfo = context.SemanticModel.GetSymbolInfo(objectCreation.Type) as INamedTypeSymbol;
179+
var symbolInfo = context.SemanticModel.GetSymbolInfo(objectCreation.Type).Symbol as INamedTypeSymbol;
180180
```
181181

182182
Because your analyzer needs to handle incomplete or incorrect code in editor buffers (for example, there is a missing `using` statement), you should check for `symbolInfo` being `null`. You need to get a named type (INamedTypeSymbol) from the symbol information object to finish the analysis.
@@ -206,7 +206,7 @@ private void AnalyzeObjectCreation(SyntaxNodeAnalysisContext context)
206206
.Compilation
207207
.GetTypeByMetadataName(
208208
"System.Collections.Immutable.ImmutableArray`1");
209-
var symbolInfo = context.SemanticModel.GetSymbolInfo(objectCreation.Type) as
209+
var symbolInfo = context.SemanticModel.GetSymbolInfo(objectCreation.Type).Symbol as
210210
INamedTypeSymbol;
211211
if (symbolInfo != null &&
212212
symbolInfo.ConstructedFrom.Equals(immutableArrayOfTType))
@@ -326,4 +326,4 @@ You can see all the finished code [here](https://github.com/DustinCampbell/CoreF
326326
* [Completed code on GitHub](https://github.com/DustinCampbell/CoreFxAnalyzers/tree/master/Source/CoreFxAnalyzers)
327327
* [Several examples on GitHub, grouped into three kinds of analyzers](https://github.com/dotnet/roslyn/blob/master/docs/analyzers/Analyzer%20Samples.md)
328328
* [Other docs on the GitHub OSS site](https://github.com/dotnet/roslyn/tree/master/docs/analyzers)
329-
* [FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Diagnostics/FxCop)
329+
* [FxCop rules implemented with Roslyn analyzers on GitHub](https://github.com/dotnet/roslyn/tree/master/src/Diagnostics/FxCop)

0 commit comments

Comments
 (0)