|
They're cool, aren't they? I like'em too, in addition to the new async return type. I do not like the local functions feature though, can't see why they made it so.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
|
|
Its hard to fix things that aren't broken...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
abmv wrote: Its hard to fix things that aren't broken...
What's broken is we're all using VS 2015 but the remote build process is still building with C# 4. So, if you don't remember to set the "use C# version" under build -> advanced to 4.0, it's easy to write a lot of code using C# 5 or 6 features, only to discover the remote build fails.
Or worse, as in my case, you find a snazzy open source package that uses C# 6.0 syntax.
|
|
|
|
|
Well its a matter team consensus..its better to get to C# latest when their is time than later brood over it.
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Our build server is set up for C#5, but I just include the latest Microsoft.Net.Compilers nuget package into my project and the build server uses that version to build my code. So, I have never had to change the build server and can always use the latest version of C#.
|
|
|
|
|
Member 12512543 wrote: Our build server is set up for C#5, but I just include the latest Microsoft.Net.Compilers nuget package into my project and the build server uses that version to build my code.
That's sneaky. I will have to try that. 
|
|
|
|
|
c# 4, 5 and 6. We are not using 7 yet
|
|
|
|
|
4.5.1 though the next project will be .Net Core 2. Oh joy.
|
|
|
|
|
R. Giskard Reventlov wrote: next project will be .Net Core 2
Writing for Linux, Android, iOS, or MacOS? Otherwise, there is no reason to specify .NET Core 2.0 or NET Standard 2.0. If the program runs on Windows only, then the full .NET Framework is the best choice.
That said, I use .NET Standard 2.0 for my new library projects, so they are portable to other OSs, since I am associated with projects for iOS, Android, and Linux.
|
|
|
|
|
Hey! it's bright and shiney and new - don't need any other reason to use it! 
|
|
|
|
|
The latest build of C#. VS 2017.
|
|
|
|
|
Marc Clifton wrote: ![Elephant | [mastadon]](https://codeproject.freetls.fastly.net/script/Forums/Images/elephant.gif) 'ing archaic.
A new emoji! 
Jeremy Falcon
|
|
|
|
|
It's a few weeks old now. Can't believe you did not notice.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
Been here off and on. A new icon looks good on CP. 
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: A new emoji!
Enjoying the ![Sunshine | [little ray of sunshine]](https://codeproject.freetls.fastly.net/script/Forums/Images/sunshine.gif) too much? 
|
|
|
|
|
Hah. Actually yeah. As I get older I realized living too much behind a computer makes your life worse not better. Well, that and I'm looking for a job... again. Because my last contract crapped out. So when in job hunt mode I tend not to do stuff like visit CP.
I like the !
Jeremy Falcon
|
|
|
|
|
I freelance, so I'm using 7.1
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself."
—Aleister Crowley
|
|
|
|
|
Brady Kelly wrote: I freelance, so I'm using 7.1
Aye, as do I with my side-freelance projects.
|
|
|
|
|
2017/7
I like the ValueTuple struct facility, and am enjoying exploring the other features the way a one-eyed cat looks in a seafood store :
«While I complain of being able to see only a shadow of the past, I may be insensitive to reality as it is now, since I'm not at a stage of development where I'm capable of seeing it. A few hundred years later another traveler despairing as myself, may mourn the disappearance of what I may have seen, but failed to see.» Claude Levi-Strauss (Tristes Tropiques, 1955)
|
|
|
|
|
You think you have it rough, try using C# 7 while your projects target .NET Framework 2.0 or 3.0 ...
|
|
|
|
|
Mario Z wrote: You think you have it rough, try using C# 7 while your projects target .NET Framework 2.0 or 3.0 ...
Ugh. 
|
|
|
|
|
I am still using the version of C# that is installed with Visual Studio 2015/SP3 for my military simulation development.
For all intents and purposes, whether it is for business, game development, serious simulations, or scientifics, and internals, there is nothing really critically important in any of the new C# versions coming out. Most new features are either different ways of doing the same things that were being done previously or some fine-tuned optimizations, few of which will be really noticeable.
That being said, if a new version of C# is released with a feature that is sorely needed for a specific requirement than an upgrade should be considered.
Other than that, upgrading simply allows the developer to say he or she is using the latest version...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
Steve Naidamast wrote: here is nothing really critically important in any of the new C# versions coming out.
Well, I'm noticing some open source projects that specifically target C# 7, like MoreLinq, though I suppose NuGet would resolve that, but I like to be able to build the latest OS code.
Steve Naidamast wrote: or my military simulation development
Then again, the military probably frowns on using open source packages?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
