What if I don't know how long it will take? Trying to figure that out is a quite a bit for me, I have to stop and process what I already completed, what's going on now, and what is left to do. A lot of these commenters are speaking as if the knowledge is being withheld from them, not as though they're making an inquiry of someone who is already working on getting the job done and didn't start with some previously defined end-time that they're winding down to.
It's not funny anymore...
I won't be voting "blue no matter who", again. We can all now plainly see that the accumulation of lessor evil is, in fact the greater evil.
No books either, for many.
They show up to vote for what they want, the left isn't being offered anything to vote for. The Dems screwed over leftists at every opportunity, I want my 2016 and 2020 and 2024 primaries back.
And the majority won't believe it until it happens to them and by the time it's happening to the majority it'll be too late for the level of resistance they'll be willing to put up to be effective.
hate hats
You dropped a word, here you go.
He either he hates Ukraine or the Ukrainian people. "The Ukraine" is how Russia refers to the region
Having been on a small town board, the truth is roads are funded at the state level (may vary by state) with funds distributed to the county governments, who maintain the county highways. The towns and cities get some amount from the county and more from the state to be used for anything highway related.
If this were not the case, and all else being equal many rural towns would go under. Private transportation is currently being subsidized at rates sometimes much higher than the property tax income the towns bring in. It's unsustainable and barely working like everything else, it's like long term vision is irrelevant and only short term gains are even considered....
Isn't the article trying to raise the issue of Republicans being accessories to the the slaughter of innocent Ukrainian people?
Well, I guess that about sums up our requisite response.
Non-normality confirmed, again...
I've been using Visual Studio for almost 20 years as my primary code editor /project manager and for all that time it's been solid. If there were errors it told you and highlighted/underlined them before you tried to build no matter where the error was in the entire solution.
I am willing to accept a slight decrease that solidness in order to gain the extra flexibility provided by dotnet core over framework. However...
My experience with the recent updates to Visual Studio have culminated into a state where errors that exists are not detected, or if they are (ex. on rebuild) they are only reported, not underlined. Once I find and fix the error it remains in the list until I rebuild, if there are other errors it will remain until I find and fix each of them (which themselves will remain in the error list...) and finally rebuild.
I've adjusted options, to no avail. Sometimes restarting VS helps for a few minutes sometimes deleting the .vs folder will help for a few more...I feel like It used to be a lot nicer.
Today I'm seriously considering moving to a plain code editor and using the donet cli for build/test/publish.
Is anyone else experiencing problems like this?
A collection of tools for dealing with nulls, failures and the generic type issues that arise in this domain.
https://github.com/Andy3432344/SafeResults
I'm the author, let me know what you think!
*Edit: updated to show GitHub link, sorry!
I have an active post in vscode right now, which I made in browser, but cannot see anything when viewing the community with Connect. Any ideas?
Hi everyone, I'm trying to try out F# via FSI in VS Code (Windows 10)
I have Ionide for F# installed, and have used it before, but now every time I try to start it I get a message "FSI :Start resulted in an error", it goes on to helpfully report "the option has no value".
dotnet is in path, dotnet works great. FSI? nothing.
I also have the .net workload installed for visual studio 2022 (if that matters).
I started up my Linux VM (KDE Neon) fired up vs codium and tried FSI Start...same error! So no tinkering in f# for me tonight. Does anyone have an idea what's happening, across two environments? Google is no help...
view more:
next ›