Hi there,

I have just spent a frustrating hour trying to get started with Visual Micro in VS 2015. When I created a new Arduino project I was unable to save it. I just kept getting a message box say the operation could not be completed.

I finally tracked it down to a setting in Visual Studio options. If you got to Tools->Options->Projects and Solutions -> General there is a setting "Save new projects when created". I usually work with this un-ticked so that I don't end up with loads of scrappy test projects in my project directory.

Anyway, if I put this tick back in place everything works fine. This is a work-a-round not a solution. Visual Micro should really let you choose to only save the project when you want to not when it is created.

Keep up the good work.

Phil

Another thought is that the "File>New>Arduino Project" menu item will probably work okay. This will create your test projects in documents\arduino leaving "File>New>Project" to use your standard location(s). 

There is no difference between the projects that both options create.

Hi,

The thing is that when you use "File>New>Project" you simply have a Visual Studio "new c++ project" template that creates a project. Visual Micro doesn't play any part in that. When you save you are simply saving a C++ project and Visual Micro does not play any part in that. This is why I feel it is a VS bug.

Another point is that the "File>New>Arduino project" creates the project immediately by calling the Visual Studio new project wizard in the background and then Visual Micro adds the required .ino source code. There is no possibility in this scenario to create the physical project later.

The last point to consider is that Arduino doesn't use project files. For an arduino compile the physical folder is inspected for files. Visual Micro works the same way in the root of the project folder unless you change the compatibility settings but I don't recommend that because it makes life more difficult.

If you want to make any suggestions or investigate why a new C++ template project does not honor the setting I would be very interested to hear your findings. Having said that there are some files that Visual Micro will always want to create such as the intellisense helpers and settings files in the __vm folder it creates below each sketch. So I am not sure how that will work and wouldn't want to divert more important dev work to investigate.