Search Issue Tracker

Won't Fix

Votes

1

Found in

2017.1.0b5

Issue ID

912636

Regression

No

Recompiling removes previously added references in VS17 solution

CodeEditors

-

Steps to reproduce:
1. Open attached project
2. Open .sln file with Visual Studio 17 in the project directory
3. In solution explorer right click on References
4. Select 'Add Reference'
5. Add 'System.ComponentModel.Composition' library
6. Open "testScripts.cs" (in the solution) - no errors appear
7. Close VS solution (save the changes you've made)
8. Create a new c# script in the Editor to trigger recompilation
9. Open .sln file with Visual Studio 17 in the project directory

Expected behavior: previously added 'System.ComponentModel.Composition' reference is saved and doesn't get removed after recompilation
Actual result: 'System.ComponentModel.Composition' reference is gone and needs to be added once again

Reproducible with: 2017.1.0b6

  1. Resolution Note:

    This is an issue with Visual Studio / Visual Studio Tools for Unity (VSTU). Please report the bug to VSTU team at vstusp@microsoft.com
    It's actually not reproducible anymore in Unity 2019.1.0a3 and VSTU 3.8.0.7

Log in to vote on this issue

Comments (4)

  1. LordDarkon76

    Nov 03, 2017 21:51

    This regard my last comment. Adding a file named mcs.rsp with "-r:System.ComponentModel.Composition" (dont put the quotes) at the asset folder allow to use system.componentmodel.composition and maybe other.

  2. LordDarkon76

    Nov 03, 2017 21:34

    Adding the System.ComponentModel.Composition. To the asset folder allow compilation at the editor, but it fails to load the dll at build.

  3. FMark92

    May 26, 2017 12:13

    I would like to add that this also happens with all System.Threading .dlls and System.Windows.Forms.dll.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues