* Introduce 'NoFramework' switch
This enables building via cake on linux without requiring adjustments on
other platforms, fixes#1745
* Revert hardcoding NoFramework in build.sh
* Skip GitVersion query for NoFramework build
This implies that NoFramework is intended for local use only
Accordingly a warning message has been set up in the Lifetime of the Build
* Rename NoFramework switch to CoreOnly
* Skip tool installation and formatting step for CoreOnly builds
* Default CoreOnly to false on windows and true otherwise
* Add CoreOnly switch to build variable output
* Fix 'native' msbuild on windows for both platforms
'native' msbuild invocations do not automatically set CoreOnly according to the platform
they are running on. As such we set CoreOnly to False on Windows, unless CoreOnly has been
specified already.
* Update README and shipping-releases as they are a bit out of date
* Update year/copyright info
* Update cake.frosting to latest for newest dotnet tooling support, and adjust builds for new configuration parameters
* update xunit packages so codelens works for nested test classes (VS2017 15.3 update is also required)
* Fixup VS version and remove win debugging tools
* Dont hardcode linksources for linux builds
* split ConventionTests into their own build task, since this is how it was in FAKE previously
* update contributing doc after change to CAKE
* minor doc updates
* fix bash linksources argument
* remove all these old packages files
* use forward slashes when referring to bash script
* use Target parameter name for the PowerShell build script
* be consistent when referring to PowerShell build script
* Be even moar consistent
* convert to VS2017
* rework cake.frosting build to latest cake vs2017 "template" example
* fix clean task and version suffix
* add arg to DotNetCorePack so it uses the correct version
* fix appveyor
* is there an easier way to test appveyor?
* ok travis, let's do this
* after reading the travis repo, this seems to be the version we want for vs201/csproj tool support
* msbuild complaining about arguments - we can use defaults anyhow so remove $@ from build.sh script
* add workaround for msbuild/travis, as mentioned on aspnet Mvc repo
* cmon travis
* perhaps tee isnt needed afterall
* travis permission denied when trying to install tools in build script... i feel dirty but need to see if sudo will fix it!
* could it be folder permissions of /build ?
* Try 777 for NuGet.exe permissions rather than 644
* remove windows platform restriction on GitVersion call
* Add a wrapper script for GitVersion on non windows
* fix wrapper script name
* add debug
* let's see if we are running the script at all!
* run mono gitversion direclty from travis.yml, for science
* see if we can run bin/sh and prepend an argument to our shell script
* remove echos from wrapper script
* Ensure full git repo include more than 50 commits and all tags are fetched, as GitVersion was failing on TravisCI
* only build netstandard framework on non windows
* revert overriding the target framework when building the solution
* Unix being case-sensitive, adjust app.config file name in csproj files
* set FrameworkPathOverride to point to different folders on macOS and Linux
* Remove NuGet.exe from the repo.
On Windows, it will be installed by the Frosting bootstrapper script.
On Unix/macOS, cake has smarts to look for mono- and Linux-specific executables
* tidy up GitVersion logic into a GitVersionRunner class
* apply workaround for osx dotnet restore "too many open files" errors
* update test project references to latest official versions
* doesnt seem to be a reason for overriding the implicit reference
* remove extra whitespace and unused namespace
* add a build task to run LINQPad samples
* make modifications to the validation of LINQPad samples
* rename the CAKE task to its original name ValidateLINQPadSamples
* rename the LINQPad samples file so they get executed in ordinal order (1, 2, ..., 10 and not 1, 10, 2, ...)
* remove openssl linking in TravisCI when on macOS
