@bradwilson@mastodon.social
@bradwilson@mastodon.social avatar

bradwilson

@bradwilson@mastodon.social

#Code #Motorcycles #Music #BoardGames #VideoGames #Photography #AntiFascist #AntiRacist #PostTheist #Feminist #EV #GreenEnergy #BlackLivesMatter | https://dotnet.social/@xunit's caretaker | He/him | 0.00115 miles tall

Previously: GitHub, Microsoft, and others.
Now: Living that retired life.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

bradwilson, to LEGO
@bradwilson@mastodon.social avatar

A little more than halfway through and it's starting to take shape.

bradwilson, to vscode
@bradwilson@mastodon.social avatar

Does anybody know if there's a way in VS Code to tell the HTML and Markdown editors what the "root" of the site is?

I have a project where the web root lives under /site rather than / in the project, but the HTML and Markdown editors assume the root of the project == the root of the site. Short of opening just the site folder, is there a way to tell the editors where to look when doing Intellisense for links and to resolve static content in the Markdown preview?

bradwilson, to dotnet
@bradwilson@mastodon.social avatar

Anybody know when we get the 4.10 NuGet packages (like Microsoft.CodeAnalysis)?

I'm assuming they're going to follow the "even" pattern and declare 17.10 as LTSC, which means I will want to officially support Roslyn 4.10. Both of these pages are currently out of date:

https://learn.microsoft.com/en-us/visualstudio/productinfo/vs-servicing

https://learn.microsoft.com/en-us/visualstudio/extensibility/roslyn-version-support?view=vs-2022

bradwilson,
@bradwilson@mastodon.social avatar

@khalidabuhakmeh I know, but I'm not shipping @xunit analyzers linked against a pre-release library.

bradwilson, to random
@bradwilson@mastodon.social avatar

One thing that never occurred to me until retirement is how much my awareness of holidays was driven by my work schedule. Last night my sister asked me what I was doing for Memorial Day and of course I had totally forgotten it was coming up. That never happened when it was also tied to the all important bonus day off. 😂

bradwilson, to random
@bradwilson@mastodon.social avatar
bradwilson, to random
@bradwilson@mastodon.social avatar

Pretty sure I'm not old enough to forget my birthday yet.

bradwilson, to dotnet
@bradwilson@mastodon.social avatar

I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.

A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.

So, back to raw SSD and (sigh) NTFS for now.

bradwilson,
@bradwilson@mastodon.social avatar

@rockylhotka I was using a physical partition.

bradwilson,
@bradwilson@mastodon.social avatar
bradwilson,
@bradwilson@mastodon.social avatar

@SmartmanApps @maartenballiauw These were the numbers I got for building xUnit.net. https://mastodon.social/@bradwilson/111350356901810814

bradwilson,
@bradwilson@mastodon.social avatar

@maartenballiauw @SmartmanApps I always exclude my source folder from Defender.

bradwilson, to random
@bradwilson@mastodon.social avatar

Oh no, it seems like the analyzer support in Visual Studio 2022 17.10 is broken.

Previously when you changed the target selector in the drop-down (see the screenshot), the analyzers would only show issues related to that target. Now it's showing all analyzer issues related to all targets, all the time.

This makes it almost impossible for me to interactively test how my analyzers work for a given target.

Hope there's a way for me to undo this somehow.

bradwilson, to github
@bradwilson@mastodon.social avatar

How do I remove the button from 2022 17.10 menu bar?

bradwilson,
@bradwilson@mastodon.social avatar

@ythos Your settings window looks very different, visually, from mine.

khalidabuhakmeh, to dotnet
@khalidabuhakmeh@mastodon.social avatar

Should the community read this list in an order of priority?

bradwilson,
@bradwilson@mastodon.social avatar

@khalidabuhakmeh Investment in AI just makes me fume. Where Microsoft is going, I don't want to follow.

bradwilson,
@bradwilson@mastodon.social avatar

@khalidabuhakmeh @elan @KirillOsenkov The real problem is that Microsoft tries a lot in the developer UX space that ends up abandoned. Being wary of MAUI is smart, given how many false starts they've had trying to replace WinForms. Aspire is too new to know if it'll stick. I'm just glad I don't have to think about web development ever again. 😂

bradwilson, (edited ) to random
@bradwilson@mastodon.social avatar

I don't understand why @bot exists when you can subscribe to hashtags. What's the value-add?

bradwilson,
@bradwilson@mastodon.social avatar

@matt @dotnetbot I guess you're assuming that all the hashtags would end up on dotnet.social, which isn't necessarily true either, but probably more true for your small instance. So you're still not getting everything... just more.

Reasonable use case then, I guess, but it sort of suggests that such bots should be on the biggest possible server.

bradwilson, to random
@bradwilson@mastodon.social avatar

I love TDD but sometimes I hate following the hashtag (purposefully not linked here) because of the posts by Scrum Shills. (Apologies if you're really into Scrum, but from my perspective it's nothing but Agile Amway.)

bradwilson,
@bradwilson@mastodon.social avatar

Hmm, maybe I should just filter Scrum.

bradwilson,
@bradwilson@mastodon.social avatar

😂

bradwilson, to dotnet
@bradwilson@mastodon.social avatar

Pro-tip for the day:

dotnet does not appear to require a trailing backslash when you define a custom NuGet package cache path via env var NUGET_PACKAGES but Visual Studio does.

Good:
NUGET_PACKAGES=X:.nuget\packages\

Bad:
NUGET_PACKAGES=X:.nuget\packages

bradwilson,
@bradwilson@mastodon.social avatar

@SmartmanApps The worst part is there's a perfectly good API (Path.Combine) that would let them ignore the problem wholesale.

bradwilson,
@bradwilson@mastodon.social avatar

@jaredpar I assume the answer is replacing string-concatenated paths with Path.Combine. More typing for more safety. MSBuild files tend to be all about the string concatenated paths. 😔

StevenJV, to dotnet
@StevenJV@curmudgeon.cafe avatar

Am I the only one who wants dotnet format to be usable against just a single file, rather than [<PROJECT | SOLUTION>] ? I'm only working in one file, I really don't want 732 files changed in this commit. We'll get to them when we get to them.

bradwilson,
@bradwilson@mastodon.social avatar

@JoeyRobichaud @StevenJV Just FYI, dotnet format does not support --folder, that's the older dotnet-format.

The performance difference between the two is staggering to the point of dotnet format being unusable.

bradwilson,
@bradwilson@mastodon.social avatar

@KirillOsenkov @JoeyRobichaud @StevenJV Seems like I should investigate using CSharpier... Thanks!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • rosin
  • ngwrru68w68
  • osvaldo12
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • thenastyranch
  • Youngstown
  • khanakhh
  • everett
  • slotface
  • tacticalgear
  • kavyap
  • JUstTest
  • cubers
  • normalnudes
  • modclub
  • ethstaker
  • InstantRegret
  • GTA5RPClips
  • cisconetworking
  • Durango
  • Leos
  • provamag3
  • tester
  • anitta
  • lostlight
  • All magazines