![visual studio tools for unity 2.1 visual studio tools for unity 2.1](https://venturebeat.com/wp-content/uploads/2019/11/sirired.jpg)
- #Visual studio tools for unity 2.1 update#
- #Visual studio tools for unity 2.1 code#
- #Visual studio tools for unity 2.1 crack#
The reason i wanted to update was because unity and vs both lock up *STILL* to this day when debugging on VSTU 2.1. I read the changelog before i updated, it said nothing about that little 'fix'. As developers, it's what we're supposed to do.
#Visual studio tools for unity 2.1 crack#
I have been using VSTU since it was UnityVS and had paid seats for developers, so a drastic change like this really rocked me.Ĭlick to expand.Then have them crack a damn book or google or RTFM. I'm pretty frustrated since I wasted so much time today trying to decipher what happened to our pipeline, so bear with me. Instead of making this assumption and blocking the editing of files, this should be a toggle in the VSTU options or at least explicitly stated. These are issues I've seen and already made adjustments to in my system, so removing access to this options doesn't "fix" any problems, it just breaks them. cs files automatically (not really difficult to do, not sure why unity doesn't just do this by default). csproj files to find and include the needed. I understand the csproj files are not updated when things change in Unity I make edits to the. I understand that not everyone using your tool is familiar with or comfortable using Visual Studio, but maybe there should be an "advanced mode" which lets you edit project files. We are a large team that needs to manage our assets differently than a single unity developer working on a project with one collection of scripts. Not everyone uses visual studio, scripts, and DLLs in the same way so its frustrating that you assume so, and assume there are no use cases for build pipelines that are not the norm. However if I am understanding correctly, you are assuming everyone using your tool does not grasp the inner-workings of Visual Studio, so you intentionally block functionality which is frustrating to not only me, but most likely many others since more than one person has ran into this issue in the week since the update. 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.Ĭlick to expand.I will look into modifying the generated project like you said. 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.
![visual studio tools for unity 2.1 visual studio tools for unity 2.1](https://cdn-screenshots.comidoc.net/1178124_2.png)
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.
![visual studio tools for unity 2.1 visual studio tools for unity 2.1](https://imag.malavida.com/mvimgbig/download-fs/microsoft-expression-blend-4430-3.jpg)
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.
#Visual studio tools for unity 2.1 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.