Hi,
Quote: Since moving from the the old Add-in to a Visual Studio Extension we have had to use the gallery extension version to manage gallery submissions. The gallery extension version is seen in tools>extensions and updates and it is the only version of significance these days. The minor version in tools>options should reflect the gallery extension version. Altering the major version in tools>options causes the visual micro "new release" dialog to appear for users which can be annoying so only happens every few months.
The gallery version is also shown on the
download page Quote:Then, when compiling a program for ESP8266, the project folder gets a new folder named "Release" filled with ".elf", ".bin", ".o" and other files. In fomer times these files had been written to the "temp" folder.
I my case the project folder -containing the source code- is placed on a SSD and is archived frequently. I want these files back to my "temp" folder which is on a standard HD. The files reduce my disc capacity and the remaining write cycles on the SSD and need not to be archived.
Visual Micro has attempted to do this for a long time because both Visual Studio and Atmel Studio do it for all other types of project. It is also useful for people who don't know how to switch on the temp folder path in the compiler output and for a lot of people who don't understand arduino has a temp build folder.
The "intermediate" location is a common visual studio project property which Visual Micro makes uses of. It is possible that in the last releases if the intermediate folder did not exist then Visual Micro creates it. When in previous releases I think it just skipped the copy.
I think you should be able to clear the path in "project property pages>intermediate directory" and then Visual Micro will not copy to that location or change to a temp folder that you create on a different disk.
The "output directory" is also used for the final export for some boards. Some newer hardware defs contain a "savehex" instruction which the arduino ide uses to export a resulting bin or elf etc (with the current board variant in the name) to the project folder. Visual Micro allows you to specify an alternate location using the "output directory". By default Visual Studio sets the output directory to "solution/configurationName". You can either move your solution to a different drive or set the path to be a temp folder somewhere that you have created.
Let me know if something doesn't work as stated or is unclear.