You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
I have unity installed in the default location, but when I open the test project and build it I get these errors.
I'm also curious how the UWP app can access the class from the Unity project without them being connected? Do you need to include the Unity project in the same directory as the UWP one?
Looks strange. You will need to set up the Unity project on your local machine (do you see the weather spheres and so on when you press Play in Unity? You can use Scene view to navigate), and then do an export on the same directory. The scripts and assets for the Unity project are build with the project content so they can be called as normal classes (in this case they are static) in the solution.
If this does not work, try to export to a new blank folder to see if it compiles, then you can copy the XAML and C# over to this project (just replace the files) and see if you can get that to build. This should not be necessary though..
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have unity installed in the default location, but when I open the test project and build it I get these errors.
I'm also curious how the UWP app can access the class from the Unity project without them being connected? Do you need to include the Unity project in the same directory as the UWP one?
@petriw
The text was updated successfully, but these errors were encountered: