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 mangled {build.project.name} prevents proper .HEX file transfer (Read 68 times)
FrankP
Senior Member
****
Offline


Posts: 260
Joined: Oct 19th, 2011
mangled {build.project.name} prevents proper .HEX file transfer
Jun 3rd, 2026 at 10:41pm
Print Post  
Using Visual Studio 2022 + Visual Micro

Teensy 4.1 project

Using recipe.hooks.deploy.preupload.1.pattern to launch Tera Term macro for OTA

build.project_name resolves to TEENSY~1.INO instead of teensy_main.ino

vm.runtime.build.intermediate_output_path works correctly and points to the right folder
The actual .hex file is named teensy_main.hex

This causes the Tera Term macro to not find the .hex file.

Has anyone else seen build.project_name return the 8.3 short name? Is there a different build property I should use instead?
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2920
Joined: Feb 13th, 2019
Re: mangled {build.project.name} prevents proper .HEX file transfer
Reply #1 - yesterday at 2:54pm
Print Post  
Thanks for the report, and the short paths are due to the command being written to a batch script behind the scenes if it begins with "cmd" to avoid long path issues etc..

As a workaround for now the attached command uses powershell so avoids the short paths completely while preserving the same functionality.

We will look at adding an option to avoid the batching for scenarios like this... and update when something is in place.
  

Please Register or Login to the Forum to see File Attachments
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint