Suggestion: For the VB version of the article, add a note that the type is unusable

Open Beginner friendly
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
63/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
visualbasic
Domain
documentation

Research direction

Start with the linked introduction and the source at trace-processor-reference-docs/xml/Microsoft.Windows.EventTracing/EventContext.xml, then compare the C#, VB, and F# views. Add a VB-specific note explaining that EventContext cannot be used and reference compiler error BC30668; the documentation should make clear that no replacement is available.

Written by the indexing model from the issue text.

Description

This introduction makes use of the EventContext type. I was trying to make the code run in Visual Basic. Whenever using the EventContext type, I get compilation error BC30668. It says that the type EventContext is obsolete. As a consequence, I was unnecessarily trying to figure out what the replacement for the EventContext type is. In the end, I found out that there is no replacement, and the hint about being obsolete was misleading.
Here, I do not challenge the compile error, however, as we can select the language (C#, VB, F#) at the top of the article, the VB version should contain a hint about this circumstance, maybe also referring to the specific compile error so that it is directly clear for other users that this is the issue they are dealing with.
Thx.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Dominant language
No language data
Stars
3
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftDocs/trace-processor-reference-docs

All issues in MicrosoftDocs/trace-processor-reference-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.