I just created a new Arduino project using the latest vMicro version (2.2023.1006) and discovered my 'board.txt' custom build script was no longer being honored.

After playing around for a while, I discovered that the new project creation process creates another [project-name] folder under the [project-name] folder and puts all the project-name files there.  Now my 'board.txt' file is in the wrong place (or the build system to see it.   

So for my 'WallE3_Quicksort_V1' project I have the following folder tree

Arduino --> WallE3_Quicksort_V1 --> WallE3_Quicksort_V1 --> WallE3_Quicksort_V1.ino (and other files)

In all my previous projects it would look like

Arduino --> WallE3_Quicksort_V1 -->  WallE3_Quicksort_V1.ino (and other files)

Why is this extra folder layer being created?

TIA,

Frank

Tim,

Thanks for looking at this so quickly.  I just sent a reply to your email sent from 'forum_admin@visualmicro.com'.  If that's not the right way, please let me know and I'll fix it 

OK, I figured out how to put everything (except the TeensyOTA.ttl file) into the forum reply 

Frank

Thanks for sending the info

Each project can have ites own board.txt, therefore you should always place it in the project folder.

There can be a lot of confusion for users when the solution is in the same folder as the first project they create in a new solution. All other (secondary) projects in the same solution would often be either in a ..\parent folder or in a sub folder below the "first" project, neither is ideal for many reasons. For example, working with source control, confusion over includes paths, local library locations etc. Therefore, the "File>New>Arduino Project" command ensurs that the solution is out of the way of the main project by being a level up. This is similar to how vs usually works when "create separate folder for solution" is enabled.

If you need to create a new arduino project and solution that share a single folder you can use the standard Visual Studio "File>New>Project" command. When you use that window there is a checkbox called "create separate folder for solution is enabled" that you should uncheck. Vs will remember your selection.

We do recommend a solution in a parent folder, that also works well with the new feature that supports "special" folders below a solution for core, libs, sketchbook etc. The special folders makes it easier to use single source control for all sources and tools used to build the code.

To move your current code you should be able to move the project code up a level, and delete the .sln. Then select "File>Open>Arduino Project"

edit: Your board.txt is using the solution property variables for intermediate and final path. In you current two folder scenario you should verify the variables are set correctly. They should default to how VS normall works.

"File>New>Project" is different option to "File>New>Arduino Project"

File>New>Project uses the standard Visual Studio new project wizard which also includes some Visual Micro new project templates such as Blank/empty project. That creates the same type of project as the "File>New>Arduino Project" but gives more control over the location.

We are considering a setting to allow the new arduino project to work in a single folder but it can be confusing for many users.

The problem comes when cloning a library or creating a shared code projects. In this case, the separate code or library (s) would end up located below the project folder. 

That becomes confusing when a 2nd project needs to use the same shared code or library.

By having a separate solution the following folder layout can be achieved, this also makes is easier to use with source control.

Solution Folder
      Misc Docs
      Shared code 1
      Cloned library 1
      Arduino Project 1
      Arduino Project 2

The arduino project is still in a single folder. The arduino ide will be happy with the lower folder where the .ino files are. That is an arduino project.

The .sln solution folder is a Visual Studio thing. It's not actually needed for the project. The .vcxproj can be opened directly with Visual Studio which would auto create a solution when you save or exit. The same project can be inmultiple solutions.

Unfortunately, windows does not have a prompt with a checkbox on it. We have to create an entire WPF tool window to provide that functionality. There is a lot of confusion caused by having the solution in the same location, especially if you have a project open and then click "File>Add>New..."

If we made the WPF window with the checkbox, most users would turn it on without really understanding the impact. It's another issue with making options too easy.