|
As you were tying that i did some research to find out which C# versions ship with which MS devstudio targeting packs.
And you're right, but i don't have those installed. Remedying now.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
If you are using VS 2017, you can add named tuples via nuget: NuGet Gallery | System.ValueTuple 4.5.0[^]
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
it doesn't let the C# compiler use implicit naming though does it? that's a *language* feature that came AFTER c# 7.0. It's not a framework feature, although the ValueTuple type framework feature is usd by the compiler to support this.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Not sure - I'm using 2019 at the moment (I removed 2015 and 2017 when I installed the latest, just keeping 2013 in case ...)
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I'm still on 2017, as i like to wait until many other devs have updated before i do.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I have to say it's been pretty stable so far - I've had fewer problems with it than with 2017 (which is why I didn't move to that or 2015). It's slower than 2013 to compile, but seems to load slightly faster.
And I like some of the UI addins such as "always visible" reference counts - even if some of the "improvements" it suggests are contradictory. Fuzzy searches are handy as well, as is Intellicode, when you get used to it (Intellisense on steroids).
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I get refcounts in VS2017. The rest is new i think.
the reason i don't switch is it's harder for me to share code. not really a stability thing. A lot of devs are somewhat conservative about updating, so i try to hold off a little myself, so that we can exchange project files, like I can post them here and more people can use them without having to fiddle with recreating an older project file from the source code.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I know how you feel - I tend to wait as well, but 15 was so poor, and 17 was flaky - so I figured that I'd have to bite the bullet and move to 19. Not regretted it yet!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That's good to know. I've had luck with VS2017 for everything but VSIX projects. It stopped working after the first one i created so now if i want to make integrated "custom tools" i have to add them to that first VSIX i made!
i get some E_INVALIDARG message when I try to create a VSIX package anymore.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
You can install 17 and 19 side by side on the same machine (provided 17 goes on first) so you could check if VSIX is working?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I could but frankly, i'm not into downloading all that right now.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
adding, I keep VS2008 around for building VSTs. LOL. The newer c++ compilers do not like the old steinberg header code.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
If you can't upgrade your project to .NET 4.7.2, you'll need to add a reference to the System.ValueTuple package:
NuGet Gallery | System.ValueTuple[^]
Looking at the dependencies, it claims to work as far back as .NET 4.5.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
interesting, but i think this is a C# language feature. I need to use 7.1 or maybe 7.2
I was using nameless tuples before - using that reference you pointed out (already ships with .NET core 2.1)
It compiled fine.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
|
My C# compiler insists otherwise
EDIT: Misread you. I am using implicitly named tuples
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
For VS2017, you'll need to change the language version under Properties ⇒ Build ⇒ Advanced.
If you upgrade to VS2019, it should automatically be set to use "latest minor", so you shouldn't need to do anything unless you're sharing the project with VS2017 users.
Select the C# language version - C# Guide | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Fair enough. I'm not gonna do that though. Too much churn for others to build my code.
I think i might rewrite, as i ran into another problem too.
.NET Core's dictionary supports new Dictionary<tkey,tvalue>(new KeyValuePair<tkey,tvalue>[] {});
the others don't, which is ASININE.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
|
I already wrote all of my code generation around this constructor LOL
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Adding, I'm actually excited about .NET 5 - since it represents the merger of all these now disparate .NET technologies. I'm getting version fatigue
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
codewitch honey crisis wrote: so I took someone's advice here about the way i declare tuples.
Never take advice from strangers on the internet 
|
|
|
|
|
1999: "Never get into cars with strangers"
2009: "Never meet a stranger from online"
2019: "Literally just flag a stranger down on the internet, summon them to your home and then get in their car"
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Well.. now sometimes it seems to work for a (short) while...
I guess this is progress, right?! 
Vector Eraser
I think I understand the nature of the (occasional) bug / numerical rounding issue.. I just seem to miss it sometimes..
(I already work around it when I detect it which made my thing go from immediately broken to.. wait for it! )
Well... I am closer than ever at any rate! 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
