Dean Ashton

For now, I only use this site to communicate with companies that don't use "less terrible" social media networks, or who simply don't provide any other way to contact them. Anyway, this place is a hellhole.. and you know what I think about hellholes..

@mkristensen Looks great, but I'd like to be able to convert from old-style to SDK-style without any agentic-based workflow, as I'm unable to use that kind of "stuff" on the work I'm targetting right now. Will that be possible? Or is a manual migration the only way..?

SDK-style support for VSSDK extension projects is now officially supported. Fellow extension authors, read this: devblogs.microsoft.com/visualstudio/s…

@thecpppm @mkristensen Glad to see this fix is now released in 18.5.2. I mean, I'm less happy that there seems to be a great deal of friction in getting bug fixes for regressions out to people that - in my opinion - should result in some sort of process review. But a fix is a fix.. so thank you.

@educatedpork @mkristensen I've requested a backport for the fix. It will be in the next servicing release in v14.50

@mkristensen, I like the VS Community site for reporting things, but I don't much care for the lack of detail on issues that have been stuck in a 'Fixed: Pending Release' mode since November. Could this be improved? Like, detail which release? eg: developercommunity.visualstudio.com/t/C-Bad-codege…

@mkristensen @thecpppm Latest update (well, one of the *only* updates from MSFT) on the community post indicates that a real (ie. non-preview) release of the fix may not be until November 2026 (contradicting the lifecycle schedule). So that's *a full year wait for a serious bug fix*. Just awful.

@mkristensen @thecpppm And *still not fixed* in the March Feature Update (18.4.0). 4 months.. super disappointing. :-( I don't know if it's addressed in the MSVC Preview Release but as I can't actually ship using that, it's pretty useless if it's the only place where it's actually been resolved.