Not cool: the Visual Studio Code setting to enable automatic XML documentation expansion is under the very generic "Format On Type".

Not intuitive so it was hard to find.

Thanks @hereispascal for explaining the setting in stackoverflow.com/a/65716253/292…
@hereispascal That way, the `ms-dotnettools.csharp` extension "C# for Visual Studio Code (powered by OmniSharp)" picks it up and pushes it down to the OmniSharp engine which gets it from Roslyn (which shortly before exposed the underlying API).

marketplace.visualstudio.com/items?itemName…
@hereispascal Wish the correlation between the extension and repository were made more clear from the repository side (github.com/OmniSharp/omni… does not point back nor mentions `ms-dotnettools.csharp`) and has a different name "Official C# support for Visual Studio Code (powered by OmniSharp)".
@hereispascal Also wish the @omnisharp team was more strict on naming, as the only way to find it there in github.com/OmniSharp/omni… was to search for `comment` (as `documentation` got abbreviated to `doc` and no mentioning of XML).

I know: all volunteers, and yes: grateful for their efforts.
Eventually a blog post on this will follow someday (:

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jeroen Wiert Pluimers

Jeroen Wiert Pluimers Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jpluimers

Sep 19
De balkonscène.

Van harte gefeliciteerd @NvCronenburg dat we al 20 jaar getrouwd zijn met toen een toepasselijke trouwerij in "de Woelige Baren": we zijn er beide, niet geheel verwacht, nog steeds.

Het Stadhouderlijk Hof, Leeuwarden.

Dank @fletcherhotels voor het fotograferen. ImageBalkonscène 2: de zoen. Balkonscène 3: de zoen.
Nicolette heeft voor het verblijf hier echt een prachtige suite uitgezocht. Zelfs het weer werkt mee. Beide kan ik aanraden.

Hier wat foto's. ImageImageImageImage
ImageImageImage
Read 6 tweets
Aug 20
Tip voor #MeerOverMedisch (ik hoop dat @ReneSteenhorst dit kan laten fiksen): zorg dat je behalve meerovermedisch.nl/columntypes/ga… ook per columnist de columns van individuele columnisten makkelijk terug kunt vinden.

Bijvoorbeeld de geweldige columns van @IvanWolffers.
@ReneSteenhorst @IvanWolffers Die kun je nu wel terugvinden via de omweg google.com/search?q=site%… maar een leesbaarder lijst zou een mooie ode zijn nu Ivan er nog heel even is.
@ReneSteenhorst @IvanWolffers Ik kwam er weer op omdat ik herinnerd werd aan waar @Liz_ORiordan een mooi statement maakte tegen de oorlogsterminologie rondom kanker.
Read 5 tweets
Aug 2
Similar for editing individual calendar.google.com entries.

However, there element class names have semi-random names, in this case `.kVw1pb`.

How rude is that @googlecalendar!

I tested this to work on monitor widths from 1024 to 3840px: Google calendar event details use half the Window width whicSemi-random element class names
One can figure out the class name of the `div` encompassing both the calendar item title and "Save" button, then setting `width` from `calc(578px + 56px + (100% - 1049px)*0.16666667)` to `calc(max(65%, 578px + 56px + (100% - 1049px)*0.16666667))` When making the width too wide, other elements get truncated
Anything wider (even like `calc(max(70%, 578px + 56px + (100% - 1049px)*0.16666667))`) makes the "More actions" dropdown going to be too narrow (despite there being enough screen estate). Probably fixable too, but too little energy for that right now. Too wide? Bye bye drop down content.
Read 5 tweets
Jul 31
Brand achter de zuidkant van @PL_Stadion #L1 #112 Image
Brandweer komt net aan.
Brandweer ontruimt zuidtribune

CC @1Limburg
Read 25 tweets
Jul 30
Wat weinig @WMC_Kerkrade tweets van me vandaag, want darmen roepen op heel zorgvuldig met mijn energie om te gaan.

Gelukkig nog het staartje van @advendosneek kunnen zien (sorry @locuta, meer zater er niet in) met het fenomenale vocale 99 Luftballons.

Image
Het einde met uitgevouwde vlag kon ik half zien maar niet goed genoeg voor een foto.

Wel een zitplak in de schaduw. Fijn!
De @FloraBand was mooi midden in hun comfort zone. Hopelijk genoeg punten, want "oeps" in de laatste trompetsolo. ImageImageImage
Read 9 tweets
Jul 25
Had some TEAC CA-200 lying around (which are Dell OEM multi-card readers). They have USB motherboard connector that has different connector locking than normal motherboards. So I cut those away and now they fit in a regular motherboard.
They also use a non-standard orange color. TEAC CA-200 with connectors on top sideTEAC CA-200 with connectors on bottom sideDetail of the OEM Dell USB connectors used with the TEAC CA-Detail of the OEM Dell USB connectors used with the TEAC CA-
Some references:

Standard pinouts and wire colors

en.wikipedia.org/wiki/USB_hardw…
Motherboard connector for dual USB 2.0

electronics.stackexchange.com/questions/9139…

Dell colours:

1. +5V Blue (should be red as blue is for ground)
2. +5V Red (OK)
3. P0- none
4. P1- White (OK)
5. P0+ none
6. P1+ Green (OK
7. GND none
8. GND Black (OK)
9. Key
10. NC Orange (should have no wire)
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(