-
Notifications
You must be signed in to change notification settings - Fork 585
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
Release 5.2 #2011
Release 5.2 #2011
Conversation
…ctories, per the documentation at https://docs.microsoft.com/en-us/dotnet/core/tools/global-json
For SQL Server 2017, we need to use the 140 (14.0) version of SqlPackage.exe, which can be installed with VS 2017. However, VS 2017 has changed the path pattern from ...\Visual Studio 14.0\... to ...\VisualStudio\2017\... . Hence this addition to the path search.
The only places where tracing is typically done is when shelling out to other applications. AssemblyInfoFile is completely within FAKE so it seems weird to trace these tasks as standard. Is someone requires tracing, they can wrap the call to these functions themselves
Fix an ambiguity in Octokit.fsx
expand passed-in path in order to workaround a dotnet cli bug
Enhancements to Fake.Core.Xml
Tracing Updates
But maintain non breaking change for all other tag tracing
@BlythMeister told me on gitter that there is a problem with this: If we update our packages to FSCore 4.5 old runners will choke after updating (because of #2001). Therefore the logical thing would be to leave the packages on the current FSharp.Core and only update the runner. But this is a bit hard to do with Paket (@forki for awareness) :(. Let's see... |
Fixes To Target Traces
The fsharp.core issue could be fixed with a binding redirect? |
sadly it's not so simple... |
😪 of course it's not... |
No description provided.