Feature/travis

[arfbtwn]

Hey @Carbenium, this is from #12 updated for current master (sorry about the Notifications reference in B.SoundMenu!) and massaged a little bit - figured we'll get the required project file changes in first and then get the travis configuration with some solution file updates in on the last one as a single unit - helps make the other patches transportable.

The only commit I left out of this one is the one where you disabled the B.SqlDebugConsole extension in release mode, does the extension not work in release mode?

[Carbenium]

Looks good to me 👍

Regarding the B.SqlDebugConsole extension: It just compiles fine in both configurations. My thought was not to include it in a distributable release build. But that's probably a separate step.
It definitely should compile fine in both modes. So just a wrong conclusion on my side.

[arfbtwn]

Cool - I wasn't sure if it had a bunch of #if DEBUG blocks in it or something. I don't think I've ever built it or even looked at the stuff in there.

I did a bit of testing with this branch today but I can't build the B.SoundMenu extension through the project file. I don't have msbuild on my system although I imagine an ebuild in portage won't be far off since the release notes for mono 5.x say xbuild is deprecated.

That said, it looks like the command line version on the CI host is a Xamarin package (from the last Travis build log of #12, in the host setup section where it installs all the pre-requisite and build system packages) so I'm worried about how many users will be able to build.

Do you mind if we go back to a 14.x build tools style for the nuget package imports? (it's those that need msbuild 15.x, or a posh IDE ;))

FYI - somewhat related; I prepared a branch, feature/csharp4, after having a little difficulty helping a guy on the mailing list (running a Zesty *buntu variant, his mono version doesn't seem to support it - I thought it was pretty odd though) so I'm thinking we might avoid C#6 syntax too.

[Carbenium]

I'm actually more in favor of drawing somewhere a line regarding backwards compatibility. Since Xamarin publishes packages for all major distributions we could expect from the developers to use those (users won't be affected by this).
Since we are more or less in a process of reviving Banshee it might be the appropriate moment to do this, in my opinion.

What do you say? 😉

[arfbtwn]

I'm worried about IDE support - I took a look at the Monodevelop/Xamarin studio logs (for Monodevelop v4 and above it's the same log) and I couldn't see 15.x build tools support in the last Xamarin studio release before the log ended with a reference to using VS on mac.

Do you know of any free open source environments that have support?