-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgraded to C# 6 language features #70
Conversation
I've never been quite sure whether to use these features yet. What demands does it put on the project? Does it require a minimum version of VS or .NET to compile? I'm guessing this might be why the build has failed. |
C# 6 was released in 2014 so I would consider it good for use. The string interpolation & propagation features make no difference once compiled, they just make the source code more concise and cleaner. Yes it looks as though the build is targeting C# 5 as the |
The targeted version of .net is not affected. The syntax is compatible with 2013, using a NuGet package, but VS2015 has support out of the box. There is no specific benefit to merging but if you decide to the AppVeyor build config will need to be updated, which can either be done through the web UI or the appveyor.yml file... |
I read a blog post about building C#6 code with AppVeyor, turns out that it's the VS solution file that needs updating; from...
to...
(or later version - ultimately so it's at least VS2015 RTM or above) @mattbrailsford I think we should do this across all the UMCO packages, in due course. |
Need to add:
as the first line in appveyor.yml |
Also I would recommend that you change the |
I think ToolsVersion should be updated to 14 or totally removed from https://github.com/umco/umbraco-vorto/blob/master/build/package.proj#L2 |
Darn BCL issue, I'll clone your fork, expect a PR for your PR :) |
@anth12 need to update build-appveyor.cmd and it should build
|
Thanks for the help @Jeavon, not used AppVeyor before. |
@leekelleher 👌:sparkles: |
No description provided.