A new version of the Unity Debugger Extension for Visual Studio Code is being released here for early testing and feedback. The debugger extension has been upgraded to the latest debugger libraries to provide a better debugging experience and try to address some of the issues found by users. The main issue this new release addresses is support for the new.NET 4.x Mono runtime in Unity. Please report any kind of feedback in this thread and help us track issues by reporting them on the GitHub repo: Download • If you need to download an earlier release please visit the GitHub page and download them from the release page. This link will be kept up-to date with the latest version at all times. Installation Warning: Installing this version will override your existing Unity Debugger extension. The provided.vsix file can be manually installed from inside VS Code by following these instructions: • Open your workspace, in the extension tab in the left menu. • Here you can open settings on the three dots in the bar with the name Extensions. • Click install from VSIX How to uninstall • Go to the extension tab. • Click on the cogwheel next to the Debugger for Unity 2.0.0 under installed. • Choose to uninstall. How can the answer be improved? Release notes ===2.6.6=== • • Updated attaching to standalone players ===2.5.0=== • • New logo that supports dark and light theme ===2.4.2=== • • Command 'Unity Attach Debugger' • Automatic detection using `Library/EditorInstance.json` • Setting a breakpoint has been refactored. ===2.3.0=== • ===2.2.0=== • ===2.1.0=== • ===2.0.0=== • Updated debugger libraries to support.NET 4.6 runtime in Unity. • Fix issue with being able to detach from Unity, which would cause the Unity Editor to hang. • Various instabilities fixes, such as LINQ debugging for.NET 4.6 runtime, hovering variables, complex class debugging etc. Minimum Requirements. New 2.1.0 release of the Debugger Extension is out. This version should make it possible to see strings longer than 100 characters. The way to do that is by evaluating the string in the debugger console or to add it to a watch field. This is a work around, due to how debugger extensions are done in VS Code, maybe a cleaner fix can be found going forward. However this makes sure that it is possible to see the string variable. As an after thought it is also possible to move the ellipsing of the string to 1000 characters if that would be of any use? Then the truncation would happen on much longer strings, but still not pollute the variables view. ![]() ![]() What do you think? Click to expand.It works really well right now! Visual studio for mac subscribe to eventhandler trigger. It catches every breakpoint, and skip all removed BPs. I found two more issues: 1. If you put breakpoints before attaching debugger, they will be 'grayed' and debugger will skip them during execution. Once you put another breakpoint or remove one of the 'grayed' breakpoints, they become active. I found the way to freeze editor. Here is procedure to reproduce this issue: • Open project • Press play button • After few seconds press it again (turn off the game) • Go to vscode, then attach and detach debugger few times (press F5, then immediately Shift+F5, and repeat it 5-10 times) • Go to unity and press play button again • At this point editor is not responding to any command and I have to kill it. Hi there, Thank you for your work on the extension. Mar 07, 2017 Now we have two Visual Studio versions (Visual Studio for Mac, Visual Studio Code) that can directly install on the Mac (macOS), refer to your description, it looks like you installed the Visual Studio for Mac, it is a developer environment optimized for building mobile and cloud apps with Xamarin and.NET. How to use visual studio for c on mac. Visual Studio Best ExtensionsVS Code is definitely my favorite editor to use, however I still often have to switch to Visual Studio when I want to be efficient at debugging because of a few issues. Click to expand.- I am trying to find a reproducable project where the debugger hangs my game, but have yet to find something that I can solidly rely on to help remove the problem. - Currently I am working on trying to find the root of the problem with static variables. However it seems like there are some deeper problem in the `debugger-libs` that this extension is based on. I will be reporting this problem to the mono guys, who are in charge of working on this side of things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |