I will probably give Rider and Visual Studio Mac a look to see whether they fare better on the above the points as I don't think VS Code will work for me. That plus the recent announcements that Unity will stop shipping MD with 2018 led me to try VS Code. Clearly some memory leak issues that were never addressed. Hated than MD crashed at least twice a day on OSX.I do like the code outline that displays in the right rail.Visual Studio will prompt you to reload the project, optionally rebuild your entire solution in VS and restart both Unity and VS. The MD cmd+b first pass build was really nice for refactoring because it would immediately show you all issues in a search results window. Also make sure that Visual Studio is set under external tools, as well as all the Unity dependencies are correctly installed via the Visual Studio installer.Probably there is a setting to turn this off but I don't see it. Clicking on a search result for a line in a file that is already opened seems to open a new instance of the file rather than moving the pointer in the currently opened one.The formatting of the results is also very odd. I actually prefer the results on the bottom as MD did it because I generally use Split editing.
If someone knows an extension that fixes this let me know Pressing enter in a statement doesn't auto indent. code formatting/beautify is terrible on VSCode.Just switched from MonoDevelop to VS Code on OSX and here are my thoughts so far: Unity automatically uses Visual Studio as its default script editor if Visual Studio is installed when you install Unity, or if you install Visual Studio as.
0 kommentar(er)
