Skip to content
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

"You must provide assembly output path" error on netcore sdk 2.1.600+ #1053

Closed
Jand42 opened this issue Apr 2, 2019 · 5 comments
Closed

Comments

@Jand42
Copy link
Member

Jand42 commented Apr 2, 2019

Trying to compile netcore templates with sdk version 2.1.600 or later results in
FSC : WebSharper error FS9001: You must provide assembly output path.

Workaround: set sdk version by adding a global.json

{
  "sdk": {
    "version": "2.1.100"
  }
}

(or other version, up to 2.1.505)

@Jand42 Jand42 added the bug label Apr 2, 2019
@ajuch
Copy link

ajuch commented Apr 9, 2019

I'm currently affected by this issue too. Until a week ago I had no problems building with the docker dotnet sdk 2.2. I'm puzzled how my build can break since I'm having my websharper dependencies frozen because of #1044. The only thing I can imagine is that a newer minor version of the 2.2 sdk docker image was accidentially pulled, but that is in contradiction to your statement that all versions up to 2.1.505 are faulty...

Can you help me understand that?

@Jand42
Copy link
Member Author

Jand42 commented Apr 9, 2019

@ajuch Sorry, took me some time to realize that the arguments temp file that was passed in was not loaded correctly because newer FSharp.Build also passes the path to fsc.exe as the first argument. Have a small fix that works, releasing it with a newer FCS included that might hopefully resolve other build issues with later netcore.

@Jand42
Copy link
Member Author

Jand42 commented Apr 10, 2019

@Jand42 Jand42 closed this as completed Apr 10, 2019
@ajuch
Copy link

ajuch commented Apr 11, 2019

Thank you, the fix works!

@Gastove
Copy link

Gastove commented Aug 29, 2019

Hello! Just to keep everyone on their toes: I'm hitting this now. I'm on a newer version than the one listed in the patch above: WebSharper - 4.5.16.344. And: the same fix described by the OP is working for me, albeit with a 2.2 SDK version:

// Global.json
{
    "sdk": {
        "version": "2.2.401"
    }
}

Can anyone provide any guidance? What other information can I provide?

Gastove added a commit to Gastove/cookbook that referenced this issue Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants