Using C# 6

37 views
Skip to first unread message

Shay Rojansky

unread,
Dec 5, 2014, 6:52:40 AM12/5/14
to npgsq...@googlegroups.com
Am hacking away at version 3.0, and I had a thought. I already have the Visual Studio 2015 preview, which supports C# 6.0. Things seem 95% nailed down with the language improvements, and I thought I'd start using them in the 3.0 branch of Npgsql. We'd still be targetting .NET 4.0 and 4.5 (although I might add 4.6 in addition), and I'll make sure mono compiles the language features.

Does that seem like a problem to anyone? The new features could really help cleaning up some parts of the code base etc...

Francisco Figueiredo Jr.

unread,
Dec 9, 2014, 12:24:36 PM12/9/14
to Shay Rojansky, npgsq...@googlegroups.com

Hi, Shay! Sorry for late reply....

I'm still in the process of installing vs2015. (I just installed the 2013 community edition).

By using c# 6.0, would it mean we would remove support to compile the project with vs2010, 2012 and 2013?
If so, I think this would be a very drastic move and we would need to think more about it. Although the language benefits are very good, I think it wouldn't be very good to remove support for those IDE versions yet. I think there is a lot of developers who contribute to Npgsql which still aren't using 2015 and won't be able to use it in the future.

On the other side, I know that the moment to create the biggest backward compatibility breaks is with 3.0. so your proposal is a very good one.


I'm more inclined to not drop support for vs2010, 2012 and 2013 for now.

+1 if we could keep vs2010, 2012 and 2013 support.

 



On Fri, Dec 5, 2014 at 9:52 AM, Shay Rojansky <ro...@roji.org> wrote:
Am hacking away at version 3.0, and I had a thought. I already have the Visual Studio 2015 preview, which supports C# 6.0. Things seem 95% nailed down with the language improvements, and I thought I'd start using them in the 3.0 branch of Npgsql. We'd still be targetting .NET 4.0 and 4.5 (although I might add 4.6 in addition), and I'll make sure mono compiles the language features.

Does that seem like a problem to anyone? The new features could really help cleaning up some parts of the code base etc...

--
You received this message because you are subscribed to the Google Groups "Npgsql Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to npgsql-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Shay Rojansky

unread,
Dec 10, 2014, 3:11:38 AM12/10/14
to npgsq...@googlegroups.com, ro...@roji.org, fran...@npgsql.org
Hey Francisco.

In the meantime, I've transitioned to C# 6.0 on another project and it seems better to wait until the official release. Some language features aren't totally finalized yet, it's probably not worth jumping the gun on this.

However, once the 2015 release is really out, if we do transition to C# 6.0 I'm 99% sure it won't be possible to maintain compatibility for old versions of VS. On the other hand, now that Microsoft releases VS community for free, I wonder if the need to support older versions of VS is that urgent. On the non-Microsoft side I've done several checks and at least on the mono level the C# 6.0 features seem supported well (not sure about the level of support in monodevelop though).

So I guess we can wait with this discussion until the actual release...

Shay


On Tuesday, December 9, 2014 7:24:36 PM UTC+2, Francisco Figueiredo Jr. wrote:

Hi, Shay! Sorry for late reply....

I'm still in the process of installing vs2015. (I just installed the 2013 community edition).

By using c# 6.0, would it mean we would remove support to compile the project with vs2010, 2012 and 2013?
If so, I think this would be a very drastic move and we would need to think more about it. Although the language benefits are very good, I think it wouldn't be very good to remove support for those IDE versions yet. I think there is a lot of developers who contribute to Npgsql which still aren't using 2015 and won't be able to use it in the future.

On the other side, I know that the moment to create the biggest backward compatibility breaks is with 3.0. so your proposal is a very good one.


I'm more inclined to not drop support for vs2010, 2012 and 2013 for now.

+1 if we could keep vs2010, 2012 and 2013 support.

 


On Fri, Dec 5, 2014 at 9:52 AM, Shay Rojansky <ro...@roji.org> wrote:
Am hacking away at version 3.0, and I had a thought. I already have the Visual Studio 2015 preview, which supports C# 6.0. Things seem 95% nailed down with the language improvements, and I thought I'd start using them in the 3.0 branch of Npgsql. We'd still be targetting .NET 4.0 and 4.5 (although I might add 4.6 in addition), and I'll make sure mono compiles the language features.

Does that seem like a problem to anyone? The new features could really help cleaning up some parts of the code base etc...

--
You received this message because you are subscribed to the Google Groups "Npgsql Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to npgsql-dev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Francisco Figueiredo Jr.

unread,
Dec 10, 2014, 8:44:43 AM12/10/14
to Shay Rojansky, npgsq...@googlegroups.com


Em 10/12/2014 06:11, "Shay Rojansky" <ro...@roji.org> escreveu:
>
> Hey Francisco.
>

Hey, Shay!

> In the meantime, I've transitioned to C# 6.0 on another project and it seems better to wait until the official release. Some language features aren't totally finalized yet, it's probably not worth jumping the gun on this.
>

OK.  +1

> However, once the 2015 release is really out, if we do transition to C# 6.0 I'm 99% sure it won't be possible to maintain compatibility for old versions of VS. On the other hand, now that Microsoft releases VS community for free, I wonder if the need to support older versions of VS is that urgent. On the non-Microsoft side I've done several checks and at least on the mono level the C# 6.0 features seem supported well (not sure about the level of support in monodevelop though).
>

Excellent! Nice to know mono support is OK and the tendency is to only get better with time.  This way when we do the transition the support will be even better.
I'll make some tests on mono develop , but I think it will be the same as mono develop uses the mono compiler in the backend. 

And I agree with you that with the community release,  we could think about supporting only the most recent versions of vs. After all, I think that as Microsoft  releases new versions of vs and make them free, less people will keep using previous versions of vs.

> So I guess we can wait with this discussion until the actual release...
>

Agreed!

Thanks, Shay!

> Shay
>
>
> On Tuesday, December 9, 2014 7:24:36 PM UTC+2, Francisco Figueiredo Jr. wrote:
>>
>>
>> Hi, Shay! Sorry for late reply....
>>
>> I'm still in the process of installing vs2015. (I just installed the 2013 community edition).
>>
>> By using c# 6.0, would it mean we would remove support to compile the project with vs2010, 2012 and 2013?
>> If so, I think this would be a very drastic move and we would need to think more about it. Although the language benefits are very good, I think it wouldn't be very good to remove support for those IDE versions yet. I think there is a lot of developers who contribute to Npgsql which still aren't using 2015 and won't be able to use it in the future.
>>
>> On the other side, I know that the moment to create the biggest backward compatibility breaks is with 3.0. so your proposal is a very good one.
>>
>>
>> I'm more inclined to not drop support for vs2010, 2012 and 2013 for now.
>>
>> +1 if we could keep vs2010, 2012 and 2013 support.
>>
>>  
>>
>>
>>
>> On Fri, Dec 5, 2014 at 9:52 AM, Shay Rojansky <ro...@roji.org> wrote:
>>>
>>> Am hacking away at version 3.0, and I had a thought. I already have the Visual Studio 2015 preview, which supports C# 6.0. Things seem 95% nailed down with the language improvements, and I thought I'd start using them in the 3.0 branch of Npgsql. We'd still be targetting .NET 4.0 and 4.5 (although I might add 4.6 in addition), and I'll make sure mono compiles the language features.
>>>
>>> Does that seem like a problem to anyone? The new features could really help cleaning up some parts of the code base etc...
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "Npgsql Dev" group.

>>> To unsubscribe from this group and stop receiving emails from it, send an email to npgsql-dev+...@googlegroups.com.


>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> Regards,
>>
>> Francisco Figueiredo Jr.
>> Npgsql Lead Developer
>> http://www.npgsql.org
>> http://gplus.to/franciscojunior
>> http://fxjr.blogspot.com
>> http://twitter.com/franciscojunior
>

> --
> You received this message because you are subscribed to the Google Groups "Npgsql Dev" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to npgsql-dev+...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages