|
So, we went from DLL Hell, to IDE Hell, to IDE+C# Version Hell...
Since the first one affected USERS, it had to be fixed.
But I cringe at the versioning going on with .NET and C# versions.
And how old projects never recompile cleanly on a new VS version.
Thankfully we have VMs.
But I totally understand managing the build cycles and defining how/what we support.
Otherwise you get a mismatch of requirements for the products across the enterprise.
So much complexity...
|
|
|
|
|
Honestly, C# isn't that bad. My biggest headaches were trying to staff a Java project where the client mandated all components were versions 3 to 6 years old. Kept finding good people who had no interest in working with old technology.
As both a consultant and an FTE, I agree with that. We need to focus on building and maintaining our resume so that we remain marketable. Working in "ancient" technology doesn't often help in finding that next contract/job.
|
|
|
|
|
|
Visual Studio 2008 C#, .NET Framework 3.5 SP1. We bought VS2015 two years ago, but never managed to budget the time for the update and the required regression testing .
Software Zen: delete this;
|
|
|
|
|
C# 6.0 with VS 2015.
I am quite happy with these versions and currently see no need to go to either C# 7+ or VS 2017 based on the projects we are currently doing.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
|
I am currently using C#7 for my project. Though the "cool" features don't come in play much. Also, with a newer tech. people look for excuses to use the newer feature even when a more familiar way would have sufficed.
|
|
|
|
|
GKP1992 wrote: Though the "cool" features don't come in play much.
My favorites are the null continuation and tuple features.
|
|
|
|
|
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: '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 too much?
|
|
|
|