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

[may18] "allow unsafe code" not auto-checked via mcs.rsp #2103

Closed
david-c-kline opened this issue May 15, 2018 · 3 comments
Closed

[may18] "allow unsafe code" not auto-checked via mcs.rsp #2103

david-c-kline opened this issue May 15, 2018 · 3 comments
Assignees

Comments

@david-c-kline
Copy link

With the addition of Spectator View, projects including the folder in their project must tell Unity (and Visual Studio) that unsafe code is allowed.

Unity should read the mcs.rsp file (included in the MRTK) and set the checkbox in the Visual Studio project.

This appears to not be happening.

The current workarounds are:

  • Manually check "Allow Unsafe Code" each time the solution is built from Unity
  • Do not generate C# projects when building in Unity (let Unity generate the assemblies).

This may be that the MRTK does not have the correct rsp file for the specific version of Unity or it may be a Unity issue.

@StephenHodgson
Copy link
Contributor

Custom assembly definitions will help with this.

@david-c-kline
Copy link
Author

Unfortunately, we don't have those for master branch releases :\

@david-c-kline
Copy link
Author

This was released in the 2017.4.0.0 release candidate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants