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

C# 3.0.3 failed to build GodotSharp solution #19564

Closed
aistrych opened this issue Jun 14, 2018 · 5 comments
Closed

C# 3.0.3 failed to build GodotSharp solution #19564

aistrych opened this issue Jun 14, 2018 · 5 comments

Comments

@aistrych
Copy link

Godot version: 3.0.3-mono

OS/device including version: Windows 10

Issue description: Clicking on "Create C# solution" (with VS Build Tools) lead to the fallowing errors:
failed to build GodotSharp solution
CSC(0,0): Invalid option 'portable' for /debug; must be full or pbonly

Steps to reproduce:
In Editor Settings -> Mono -> Builds set -> Build Tool: select "MS Build (VS Build Tools)".
Click "Create C# solution".

Creating solution with MS Build (Mono) works as expected.

@akien-mga akien-mga added this to the 3.0 milestone Jun 14, 2018
@akien-mga
Copy link
Member

The error sounds like it might be related to #18949, and #14822 where @neikeq commented:

For existing projects, you need to manually rename all <DebugType>full</DebugType> occurrences in your csproj file to <DebugType>portable</DebugType>.

@hpvb This should likely be mentioned in the 3.0.3 release notes.

@akien-mga
Copy link
Member

Though wait before mentioning it in the release notes, it seems like the issue is the other way around here (portable used by only full supported?).

@neikeq
Copy link
Contributor

neikeq commented Jun 14, 2018

What's the version of MSBuild and csc?

@DevMagicLord
Copy link

I got same issue on Windows, last mono is installed but Godot is unable to locate it and compile.

@aistrych
Copy link
Author

It was my mistake. I've installed Microsoft Build Tools 2015 version 14.0.23107.10. It's a very old version I think. Installed newest one and it works like a charm. So I think I will close that issue :)

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

4 participants