Build instructions don't work. about altcover HOT 12 CLOSED

The F# 4.3.4 NuGet package is used purely as a convenience for Mono/Linux builds.

The build works with an out-of-the-box AppVeyor build machine with the Visual Studio 2017 profile, so checking what's actually in the box, I realise that it also comes with Visual F# Tools 4.0 RTM, as well as, presumably, both the F# components checked in the VS2017 install.

That may well be the missing ingredient I'd not previously noticed.

from altcover.

Having recently repaved one of my old machines I took the opportunity to install the Visual F# Tools 4.0 RTM, and it installs the necessary .net 2.0 support under C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp\

I've updated/overhauled the build section of README.md as a result.

from altcover.

Still not working. I have installed the "Visual F# Tools 4.0 RTM" package but I am still getting errors. Attaching the full build log starting with the git clone and going trought the restore/setup/build cycle.
Please note that this is the same VM that I used to run the previous build attempt.
fullbuildlog.txt

from altcover.

So, it's failed while running FSharpLint over the code; I have seen intermittent failures from that package before now. What happens when you try again?

from altcover.

What you are seeing looks like FSharpLint issue 250, only not in a .net core context.

from altcover.

It's sistematic with 100% occurence rate. It should be easy to reproduce: I am using a DS1 Azure Lab instance ( 1 CPU, 3,5 Gb of RAM ) with the latest VS 2017 and Visual F# Tools 4.0 RTM. Could you please document also this error and how to address it ( for example by removing the FS#Lint target )?

from altcover.

Pull requests will be accepted.

from altcover.

I have made a speculative change to address the issue in commit 94beb84ba6; if that doesn't resolve the issue directly, then setting

$env:FSharpLintEnabled="false"

should suppress that step

from altcover.

Confirmed that it works by excluding the FSLint step. I am closing the issue.
P.S: I would like to contribute to the project what is there to be done and how to get in touch?

from altcover.

New issue after downloading latest master. Build log attached
buildlog newissue.txt

from altcover.

A new Fake RC came out with another breaking API change. The fix is in the feature/staging branch, just not yet in master.

from altcover.

Merged into master.

from altcover.