The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I was under the impression that Microsoft had listened to the pitchfork wielding masses and stopped the practice of rebooting your machine without warning. I honestly had.
Whatever possessed you to come to that conclusion? As far as I'm concerned, it's getting worse - not better.
A few months ago I was commiserating right here in the lounge about that fact that I had finally abandoned the idea of developing on Windows clients altogether, and using server versions instead to run my dev tools, strictly for the reason that traditionally, Windows Server versions never rebooted on their own. Only to be proven wrong on the very first Patch Tuesday cycle following my clean install of Server 2019.
Previous versions (2016? 2012 R2? Older still?) would never complain, even if you made them wait, quite literally, for months.
I just made this post on the Rust section of Reddit and it got removed as offensive or abusive:
"The whole variable shadowing thing is just a ridiculously bad idea. I cannot believe that a language so anal retentive about safety would allow such a thing. If there's not an option to have the compiler warning about it, there should be."
I mean that's just Rust fan boys suppressing anything that questions the sanctity of Rust.
As far as I'm concerned...the C++ fanbois at least have decades worth of real-world projects they can use to support whatever claims they want to make. Rust right now is being described by Wikipedia as having appeared less than a decade ago. Remove from that whatever amount of time it takes for any language to see some real-world use.
Is it fair to draw any conclusion from that? Whether that's even a valid metric to use, that's not for me to decide, but it is what first came to mind...
Sorry to post here, but I kept getting an error when posting a Question...
I need a tool that can examine a Visual Studio project, and then spit out metadata - things like:
- version of MS Build
- Target .NET version
- list of packages/dependencies/etc.
I can build this, but if something already exists that would be preferable.
Ideally it can scan projects in an Organization's Azure DevOps repositories to build up a report.
I have a client with literally 100s (perhaps 1000s) of such projects, and they need to catalog what tools/components/libraries/etc. they are using. Primarily so they can track EOL (end of life) and be less reactive to upgrades and such.
For that, the NuGet package references can either be stored in a packages.config file, or as <PackageReference> elements in the project file.
They'll also be listed as <Reference> elements within the project file. And you'll have a reference for the complete dependency tree of NuGet packages which the referenced packages depend on.
Then there's the "SDK-style" project:
That should always have NuGet package references stored in the project file. It will only have references for the packages which the project directly depends on; any dependencies of those packages will not be listed.
Exactly. If everything was built using (pretty much) the same tools, then great, otherwise...there's always going to be some hole and the assessment is always going to remain incomplete. What impact that has on the answer it'll find for you depends on the question being asked.