- #Visual studio for mac open 2 projects at the same time how to
- #Visual studio for mac open 2 projects at the same time code
- #Visual studio for mac open 2 projects at the same time Pc
#Visual studio for mac open 2 projects at the same time code
Getting package source code in VS, for instance, has been a game-changer for playing around with DOTS.If you’re new to Visual Studio Code, the Command Palette will become a familiar part of the user interface. It's a shame, because VS is by far my favorite IDE, and I've been very happy with many of the new features. This is particularly frustrating when you need to debug something that has long load times. Lately, it's been an exercise in restarting both the editor and VS to see if that fixes the issues. Sometimes I attach VS to Unity, but then I can't interact with Unity anymore (Unity is frozen, I can't hit play).Īttaching and debugging with VS worked 98-100% of the time for me before. Sometimes I need to delete all breakpoints before I can manage to attach VS to Unity. Other times I seemingly manage to attach VS to Unity, but breakpoints are never triggered. Usually, it ends up with me trying to attach the debugger, Unity goes busy for a while (I usually assume that Unity is frozen after about 30 seconds, then restart both the Unity editor and VS), then *maybe* I get to debug. Lately, I've had lots of issues attaching the debugger in a timely manner. In addition, debugger attaching has become less robust, I fight this more than ever before. Basically the issues started the moment VS integration from Unity moved into package, it worked pretty fine right before that. What I usually just do now when I see this dialog is that I just open task manager and force kill VS as it's simply the fastest way to get this thing responding again.Īll in all, I'm a long time fan of VS but current experience with Unity is just horrible. This usually just freezes VS fully for like 10-30 seconds (I'm on a really high end rig here with fast nvme etc). VS solution gets constantly redone for whatever reasons and VS prompts if I want to reload or ignore this. double clicking a file from unity's project tab or error message from console doesn't open the whole solution in VS, instead more often it just opens single file in new VS instance (sometimes even when the solution is open in other instance of VS.
#Visual studio for mac open 2 projects at the same time how to
I also don't know quite how to report bugs like this and therefore I haven't reported any of it.Ĭlick to expand.My two main annoyances that make using VS pain with Unity are: I find it odd that no one else has mentioned this. I don't know if it has something to do with me using a preview version of Visual Studio 2019 but it works fine in older Unity versions like 2019.1.
#Visual studio for mac open 2 projects at the same time Pc
I have to restart my PC every time I do it which I'm not quite fond of. This also stops me from reporting bugs because the bug reporter also has a problem with it. I can't delete it normally and has to resort to programs like Unlocker sometimes, BUT EVEN THAT can fail.
In there, in the package cache, that package has a "vswhere.exe" file that is ALWAYS locked somehow.
Since I've been encountering other bugs I've been deleting the Library folder quite often. The Visual Studio integration package is one massive thorn in my side. Lastly, a problem that I don't know if it's directly related to Unity + VS but I thought I should just mentioned it anyway.
All my connected assembly definitions are lost and I have to restart Visual Studio to get it back. I can create a script, edit it, and all that, but as soon as I go into Unity and it does it's thing, Visual Studio seemingly loses all references. So I have to create the script then go to Visual Studio and fish it out of my project browser.Ĭreating a script inside Visual Studio though breaks it even more. If I get an error in the console I can't click on it because it will open up in my default text editor instead and Visual Studio will be prompted to reload the project several times.Ĭreating a new script in Unity prompts VS to reload again, but even after reloading it feels like a 50/50 chance it will open in VS or the default text editor if I click on it inside Unity. To start, clicking ANY Debug.Log message fails 99% of the time. Am I the only one with these problems? I would've thought someone else would've posted it by now, but I guess not. I've been working with the alpha for some time now and pretty much through the entirety of that time, Visual Studio and Unity has not been working nice together at all.
0 kommentar(er)
