VS Arduino - Double same-name project folder convention?

Jun 17^th, 2026 at 3:03pm (UTC)

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:-

Save the new Output to a Text File and....

Support requests without the output above may be impossible to answer, so please help us to help you

VS Arduino › Visual Micro › Visual Studio 2019, 2022, 2026 › Double same-name project folder convention?

‹ Previous Topic | Next Topic ›

Pages: 1

Double same-name project folder convention? (Read 114 times)

FrankP Senior Member Offline Posts: 260 Joined: Oct 19^th, 2011	Double same-name project folder convention? May 29^th, 2026 at 4:41pm	Print Post
	For some time now I have gotten used to dealing with double-named folders for VS/VM projects, i.e. 2Wheel_Robot.ino. I believe this arrangement was required in conjunction with using the 'board.txt' file to execute my OTA a post-processing script that utilizes TeraTerm macros to upload sketches using Bluetooth wireless serial channel from my Windows 11 box to an HC-05 module on my robot. Now I am using Grok build to set up a github project in a different folder tree, and Grok tells me I don't need the double-naming convention. I'm reluctant to go with this, as I think it will screw up my hard-won OTA capability. Can someone clarify this for me? I have provided the Grok response below: TIA "This double nesting (260523_2Wheel_Robot inside another 260523_2Wheel_Robot) is NOT required by modern Visual Micro. It works, but it's unnecessary and makes the path longer than needed."


	IP Logged

Tim@Visual Micro Administrator Offline Posts: 12205 Location: United Kingdom Joined: Apr 10^th, 2010	Re: Double same-name project folder convention? Reply #1 - May 31^st, 2026 at 2:36pm	Print Post
	Hi, Visual studio has the concept of a solution. a solution can contain multiple projects. In this case it sounds like the solution and/or the solution folder has the same name as the project. Grok is right, visual micro doesn't mind if the solution (.sln) is in the same folder as the project or somewhere completely different. But it's less confusing and more flexible if the structure is Solution > Project1 > Project2 This applies even if the solution contains only 1 project. When creating projects in Visual Studio. It often prompts to create a solution folder. That also gives this "double name" scenario. Unless you have hard coded paths in custom events. It would be okay to close the solution and rename the top level folder so it's less confusing. In which case also rename the .sln. after reopening the solution, right click and rename it in vs too. So avoids confusion.


	WWW Facebook Twitter YouTube IP Logged

Pages: 1

‹ Previous Topic | Next Topic ›