DrDeadCrash

joined 2 years ago
[–] [email protected] 1 points 11 hours ago
[–] [email protected] 19 points 21 hours ago (2 children)

MAGA is the enemy.

[–] [email protected] 3 points 1 day ago

Cool, I'll throw it on my pi4. Thanks!

[–] [email protected] 2 points 1 day ago (2 children)

I'm interested in doing this also. Is there a guide you're following, or would recommend?

[–] [email protected] 17 points 2 days ago

That's 'truthy'

[–] [email protected] 1 points 3 days ago (1 children)

Bernie is a self avowed Socialist

[–] [email protected] 1 points 6 days ago (1 children)

IIRC...Creators say it doesn't matter, either pronunciation is fine.

[–] [email protected] 19 points 1 week ago* (last edited 1 week ago) (10 children)

Your mode of conversation is quite odd.

[–] [email protected] 2 points 1 week ago (1 children)

No, they salivate in anticipation.

 

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?

1
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
 

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!

1
FSI Start (programming.dev)
 

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 ›