Topic: VS 2015 is da bomb!

[MexicanCustard]

Switched to 2015 yesterday and I have to say, I love the new coding improvements in C#.

The new Auto Property Expression body is great.  I have to say code just looks a lot simpler this way.

Code - C#: [Select]

1. private string _myString = "Some String";
2.  
3. public string MyString
4. {
5.     get { return _myString; }
6.     set { _myString = value; }
7. }

Turns into

Code - C#: [Select]

1. public string MyString { get; set; } = "Some String";

My "mostest" favorite is the new null propagation.  I'm constantly using this feature.

Code - C#: [Select]

1. if (myObject != null)
2.     myObject.DoSomething()

Turns into

Code - C#: [Select]

1. myObject?.DoSomething()

For those of you who haven't switched.  These two features alone are worth switching.  I had thought these new features were only going to be in .NET 6 but these new feature are compiler (Roslyn) features that work in .NET 4.5 and .NET 4.5.1.  I don't have anything older than that to test it on but I don't see why they wouldn't work on older versions too.

[Bryco]

Looks great tx for the info

[BlackBox]

From a while ago, but may have some additional info:

http://www.theswamp.org/index.php?topic=47840.0

[nobody]

same i love it

[CADbloke]

My "mostest" favorite is the new null propagation.  I'm constantly using this feature.

Code - C#: [Select]

1. if (myObject != null)
2.     myObject.DoSomething()

Turns into

Code - C#: [Select]

1. myObject?.DoSomething()

Same here, particularly because you can chain the Null Propagation operator. A good example here: http://davefancher.com/2014/08/14/c-6-0-null-propagation-operator/

I've only used it for a few days but it seems faster and more responsive once the IDE is up. Also, CodeLens is brilliant - especially if you use Git.

VS 2015 handles V2013 projects seamlessly, as you would expect. Resharper seems to work faster too and all my settings from there migrated. Exporting the settings from VS 2013 into VS 2015 didn't break anything.

[Kerry]

< .. >

VS 2015 handles V2013 projects seamlessly, as you would expect. Resharper seems to work faster too and all my settings from there migrated. Exporting the settings from VS 2013 into VS 2015 didn't break anything.

I found the same.

My only concern is with writing code plugins for the  Unity3D game engine .. there are some restrictions with the.NET language version features I believe ( haven't investigated yet. )

For anyone using a DOtNet Wizard for AutoCad ... the wizard build for VS2015 has not yet been released.
If you 'need' it, email   virupaksha  aithal @ autodesk com ( fix the syntax first ) with an update request.

[Kerry]

We will have .NET wizard for VS 2015,

We are targeting the to finish this work by September end.

I'm sure most people could wean themselves off the wizard in that 9 weeks
Not that there's much of an alternative.

< > Don't kick me, I'm just the messenger </>

[BlackBox]

We will have .NET wizard for VS 2015,

We are targeting the to finish this work by September end.

I'm sure most people could wean themselves off the wizard in that 9 weeks
Not that there's much of an alternative.

< > Don't kick me, I'm just the messenger </>

Not that surprising given that they're only in Alpha now, if not what happened with RTM AutoCAD 2015 .NET Wizard + VS 2013 (linky); I'll see if they'll entertain the idea of expediting the Wizard for this cycle... If not, I'll at least reiterate the request 'elsewhere'.

Cheers

[Jeff H]

Its actually pronounced "da bomb".

[MexicanCustard]

Its actually pronounced "da bomb".

Fixed.