fix #2103 - allow unsafe code

[david-c-kline]

Add csc.* to fix Unity not enabling Allow Unsafe Code in the generated projects when building for the .NET Backend.

Tested on Unity versions:

• 2017.1.3p4
• 2017.2.1p2
• 2017.4.3f1

Fixes: #2103

[keveleigh]

We may need to use both. Does this work with IL2CPP?

[david-c-kline]

@keveleigh, good question. i'll give it a try

[david-c-kline]

verified that with BOTH files present, Unity successfully compiles the dll with IL2CPP.

[david-c-kline]

Updated PR description to match the current contents.

[StephenHodgson]

Do we also need to make sure this file gets included into the asset package?

What happens if someone has a file like this already declared?

[david-c-kline]

@StephenHodgson,

I will be adding these files to the asset package for the May release. If the user has one, the package importer should show it as already there (and not override)

[StephenHodgson]

the package importer should show it as already there (and not override)

that's not exactly how it works. It'll only override if the meta file id is the same.

[david-c-kline]

We had been shipping .rsp files in earlier releases. Is the concern that ours may overwrite an existing rsp?

[StephenHodgson]

no, mostly if they collide, but then again, if people are using this file they most likely know how to handle conflicts with it.