Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic RELEASE: 22.1128.24 - VS 2017/2019/2022/VS2022_ARM64/AS7 (Read 813 times)
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12186
Location: United Kingdom
Joined: Apr 10th, 2010
RELEASE: 22.1128.24 - VS 2017/2019/2022/VS2022_ARM64/AS7
Dec 28th, 2022 at 11:48pm
Print Post  
tip: If running the downloaded .vsix file fails then "RIGHT CLICK > OPEN WITH > VISUAL STUDIO VERSION SELECTOR"

  • If a path contains utf8 chars we were unable to drill down (dbl-click) into the code from compiler error messages.
  • Show clearer warnings if the current app is configured with invalid IDE Location. (Only applies to using Visual Micro alongside Arduino 1x IDE)
  • Intellisense library includes were missing after a failed build.
  • New project format intellisense: Added shared paths as includes. They are required to support include <> alongside #include ""
  • VS2022: Prevent escaping of gdb args. Escaping of compiler args was added in recent versions, inadvertntly affected debug args.
  • VS2022 Update causes debugger sources to be loaded from the temp build folder: Add a source file mapping list to the gdb debugger launch json.
  • Add the 'additional board support urls' to the verbose output so that support is easier.

Download Visual Micro for Vs 2022
Download Visual Micro for Vs 2017/2019
Download Visual Micro for Vs 2022 Windows on ARM64

22.1128.22
Download Visual Micro for Microchip Studio (AS7)

note: .vsix files are zip fles. The Microsoft extension installer manages the installation.

Known issue:-

  • Unable to set a hardware debugger breakpoint in INO code other than the project_name.ino. Other INO code can be "stepped into" and "stepped out of" but without break/trace features. (Under investigation)
« Last Edit: Jan 3rd, 2023 at 2:06pm by Tim@Visual Micro »  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint