-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Updating to 1.4.0 from 1.3.0 fails with with Unity 2020.1.17 #12
Comments
@KuraiAndras Solution 1:
Solution 2:
|
To be precise, we have multiple projects, and they are not located in the packages folder. The structure is like:
In this context what does the Packages folder refer to? [UnityProject]/Packages or [UnityProject]/Library/PackageCache or just whatever folder the UPM resolves when reading the mainfest? Also why is the Packages folder excluded by default? |
Check For example:
and
This is to prevent unintended compiler changes and to minimize the impact of compiler changes. |
I'll try this and get back to you soon |
Yupp, the project wors, after including the assemblies like : Packages/package.name.etc . Also could you provide some documentation on this in the readme? |
👍
Sure. |
Describe the bug
Updated my project from 1.3.0 to 1.4.0 with Unity 2020.1.17 and not all of my sources are compiled
To Reproduce
Can't really
Expected behavior
All sources compile
Screenshots
Environment (please complete the following information):
Additional context
The problem might come from the fact that we are using external .cs files added as unity packages. We have several projects included like:
These point to folders with .net standard 2.0 projects (which are using C#9.0) (also the bin and obj folders are renamed to .bin and .obj so unity will not try to use the dlls inside them). The errors seem to only come from one project where c# 9 and 8 are used, and not from the unity project.
Should I include another folder for assemblies in the settings?
The text was updated successfully, but these errors were encountered: