Hi,
My sequence was  :
- Installed arduino plugin in existing VS2015
- Using 1.6.1 Arduino installation
- Installed VS2017
- Installed arduino plugin (did not ask any config data so must be using the previous

---> worked correct, compiles, downloads OK

- downloaded Arduino 1.8.1
- uninstalled VS2015
- uninstalled VS2017
- installed VS2017
- installed arduino plugin (did not ask config details)

Situation now : 
- can create "normal c++ projects"
- when creating arduino project i get the message in the attachment
- the project directory is created, when opening the project it looks ok
- when opening the included ino file I get the same message

Questions :
- Anyone seen this message and/or knows a solution
- Is there a way to completely remove all plugin info

  

Hi,

Have send the email.

For others reading this thread :
- I used both methods of creating new project
- The 1.8.1 arduino IDE works as expected.

Answers : 

2) Using Arduino 1.6.13 gives the same error message

3) C:\Users\Herman\Documents\Arduino

4) Yes it compiles : 
build.vm.build.optimised=1
roject\esp8266_d1_mini\Debug

Compiling debug version of 'vmicro_newarduiniproject' for 'WeMos D1 R2 & mini'
Program size: 224.969 bytes (used 22% of a 1.044.464 byte maximum) (15,97 secs)
Minimum Memory Usage: 31912 bytes (39% of a 81920 byte maximum)

5) C:\Program Files (x86)\Microsoft Visual udio.Arduino.15.dll

For 1) I need some more time, need to download/install VS2015. Will do asap and report results.

On 2) the fna5......nq3 directory underneath the Extensions does not exist

Did a quick install of VS2015.
Strange was that the vsmicro installer mentioned that it was already installed.

Creating a new product succeeded. Compiling too.
Not uploaded to device yet.

Yes that's it thanks

I can only guess the problem is the "tools for cmake 1.0" but I am sorry if I am wrong.

I say this because below is what is installed on a test server for visual micro.

The server hasn't got the "tools for cmake" installed, I think they are new.

The Android, IoS and Cross Platform tools are all C++

What I can say is that Visual Micro doesn't prevent the ino code from opening when you click to manually open the file. It only attempts to auto open when the project opens. So visual micro isn't able to prevent the problem because it is happening elsewhere. If it is the cmake system it is a bug that I am sure other will report. You could try change the visual studio file type of the .ino from c++ to document. (F4 properties). Then see if you can click and open it. If you can we can have a setting that switches all .ino file types to "document" as  a workaround. VS doesn't care what the file type is intellisense will continue to work.


note: visual micro works with the basic vc++ package. The test server has others installed for testing purposes only. If you can build a win32 c++ project that's all we need for intellisense to work. (Compile is not managed by visual studio)

Microsoft Visual Studio Community 2017 RC
Version 15.0.26020.0 D15REL
Microsoft .NET Framework
Version 4.6.01586

Installed Version: Community

Visual Basic 2017 RC   00369-50000-00000-AA346
Microsoft Visual Basic 2017 RC

Visual C# 2017 RC   00369-50000-00000-AA346
Microsoft Visual C# 2017 RC

Visual C++ 2017 RC   00369-50000-00000-AA346
Microsoft Visual C++ 2017 RC

Visual F# 4.1   00369-50000-00000-AA346
Microsoft Visual F# 4.1

Application Insights Tools for Visual Studio Package   8.4.01118.2
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2016   15.0.21206.0
ASP.NET and Web Tools 2016

Command Bus, Event Stream and Async Manager   Merq
Provides ICommandBus, IEventStream and IAsyncManager MEF services for loosely coupled Visual Studio extension components communication and integration.

Common Azure Tools   1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

JavaScript Language Service   2.0
JavaScript Language Service

JavaScript Project System   2.0
JavaScript Project System

JavaScript UWP Project System   2.0
JavaScript UWP Project System

KofePackagePackage Extension   1.0
KofePackagePackage Visual Studio Extension Detailed Info

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

Mono Debugging for Visual Studio   Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.

NuGet Package Manager   4.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

TypeScript   2.1.3.0
TypeScript tools for Visual Studio

Visual C++ for Cross Platform Mobile Development (Android)   15.0.26004.01
Visual C++ for Cross Platform Mobile Development (Android)

Visual Studio Tools for Universal Windows Apps   15.0.26009.00
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.

Xamarin   4.3.0.459 (7c3dcf2)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   7.1.0.13 (72366f7)
Visual Studio extension to enable development for Xamarin.Android.

Xamarin.iOS   10.4.0.33 (d93ae7e)
Visual Studio extension to enable development for Xamarin.iOS. 

Okay thanks for the testing I will experiment some more. The file type in the IDE > F4 properties is not related to the file association so notepad++ shouldn't affect it.

The visual micro settings are in regedit.exe HK_CURRENTUSER/software/visual micro. Visual micro doesn't store knowledge of where it is installed.

One other things to check is "tools>options>text editor>file extension". Make sure the .ino file extension is associated to C++. 

This affects which editor visual studio attempts to open when you edit code and now that I think about it is probably the issue. If no extensions are in the "tools>options>text editor>file extension" list then add .ino (with the leading .) and select C++

Excellent thanks. Very interesting!

Maybe of interest: VS2017 starts faster than previous versions and also loads extensions later. Normally visual micro always tries to add the .ino extension mapping. So it's strange it's not working. 

Maybe some sort of VS2017 RC bug but I am very interested to hear what you find. I will also try to replicate and have altered the error notice that visual micro displays with a hint about the tools file extension mapping