The projects that VSTU generates were never meant to be compiled as a standalone DLL. If you want to modify the generated project files each time Unity needs to regenerate them, you can do it by participating in our project generation using our API: Open the csproj, and comment the line with. Then you just need to treat those projects as an actual class libraries and not as a VSTU project. Now, if I understand correctly, you have a slightly different use case where you take the generated projects, copy them somewhere, and use that to create a class library. Therefore, we're preventing users to modify the project properties for VSTU generated projects. With Unity, you need to drop the class library in the Assets folder, that's the only to get Unity to reference a class library.
You can't for instance add a new reference to a VSTU project like you do for a standard class library project. They represent the state of Unity's compilation pipeline, and if you modify them from VS, the next time something changes in Unity the changes will be overwritten.
#Microsoft visual studio tools for unity update
So much for an update with just "bug fixes", all it did was remove functionality from the user in order to "hand hold" the developer through the visual studio process.ġ) Can I get a link to VSTU 2.1 without this bug that you think is a feature?Ģ) Can you make the project/solution locking or whatever is happening a toggle instead of forcing a leash on every developer?Ĭlick to expand.The projects that VSTU generates were never meant to be compiled as a standalone DLL. Since I can't seem to revert to the older plugin, I'm faced with rewriting huge portions of our pipeline. The worst part, is I can't seem to find a link anywhere to VSTU 2.1 which did not have this issue.
sln created by Unity and VSTU in Visual Studio, it doesn't recognize it as a C# project, I can't open the properties view for the any of the project files, and I cant add a reference to any external DLLs. csproj files that were generated, and adding references to a few external DLLs. Part of this workflow included editing the.
#Microsoft visual studio tools for unity code
csproj files for modules of code that we would then compile into DLLs. We were using Unity, VSTU, and Visual studio to generate. Click to expand.I am having this same problem and it sunk a whole day of development time for me.