question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compilation failure after fresh install (F#)

See original GitHub issue

Steps to reproduce

In a new directory, follow these commads: dotnet new -l F# dotnet restore

Expected behavior

Running dotnet run or dotnet build works like in a C# .NET Core project.

Actual behavior

When doing dotnet run or dotnet build, you’ll get a compilation error, even though the installation is clean, all configs are default.

Environment data

dotnet --info output: .NET Command Line Tools (1.0.0-preview2-1-003177)

Product Information: Version: 1.0.0-preview2-1-003177 Commit SHA-1 hash: a2df9c2576

Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64

(I also have 1.1.0 current installed)

Full error produced

Compiling Library for .NETStandard,Version=v1.6

The specified framework 'Microsoft.NETCore.App', version '1.0.0' was not found.

- Check application dependencies and target a framework version installed at:

      C:\Program Files\dotnet\shared\Microsoft.NETCore.App

  - The following versions are installed:

      1.1.0

  - Alternatively, install the framework version '1.0.0'.

I also tried…

  • uninstalling & reinstalling all of .NET Core
  • doing this on a clean windows VM (same error)

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:3
  • Comments:25 (14 by maintainers)

github_iconTop GitHub Comments

3reactions
enricosadacommented, Nov 22, 2016

@battisti thx for testing! i tried locally and require a new release of dotnet-compile-fsc (dunno why in my previous local tests was working ok before, probably i mixed cli version) with correct deps. i’ll publish that tomorrow.

And yes @piotrpMSFT the tests for templates are my next todo (preview2.1, preview4). At least i just enabled full ci for all os! in https://github.com/dotnet/netcorecli-fsc/pull/45 (dotnet-ci is really fast). But i really want remote templates 😭😭😭

2reactions
enricosadacommented, Nov 22, 2016

@ondrejgr yes the issue is with dotnet-compile-fsc, not with dotnet-new template. the preview2.1 require a different version of dotnet-compile-fsc than preview2. i’ll publish that soon

Read more comments on GitHub >

github_iconTop Results From Across the Web

Maven : mvn install results to Compilation failure
You are missing some Java EE dependencies, try adding the following dependency to your pom.xml (you probably need more):
Read more >
mvn clean install - a short guide to Maven
You can use this guide to understand what a 'mvn clean install' really does. Also: A crash-course on Maven and workarounds for its...
Read more >
Compilation failure when run mvn clean package
I switch java version 1.8 and after run mvn clean package it successful run after that i run mvn clean install in that...
Read more >
Common issues and workarounds in Visual Studio setup
This article describes common issues during Visual Studio installation and provides suggested workarounds.
Read more >
20+ Maven Commands and Options (Cheat Sheet)
Notice the package goal executes compile , testCompile , and test goals before packaging the build. mvn install. This command builds the Maven ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found