Hi,

No other reports of this. Is the build happening when the "delay" is shown?

Please switch on vmicro>compiler>verbose then build and email the output to info[at]visualmicro.com along with a link to this thread. This will show us some of your config save you telling us.

Thanks

The only thing that can be is your virus checker. Visual micro can't control those windows. All it can do it place .zip files with vs templates in a folder below the extension which vs auto detects and unpacks when it needs to.

Open task manager > process when the delay happens then sort by cpu usage (make sure you are seeing all process for all users if applicable). This will show what program(s) is causing the issue

If you install the visual micro extension then in tools>options>visual micro>location>assembly you will see the path where vs has installed visual micro. Below that folder is "Project Templates" which contains the .zips.

Visual Studio has full control of this. Maybe you just need to leave it one time to sort itself out. How long do you wait each time it happens?

Oh I see, I will trace it to see what might be.

Hi

I think this is a VS issue ....

Visual studio manages the install and uninstall of extensions. An extension is not an .exe program it is just dlls that Microsoft load when they want to load based on if an extension is installed.

The Microsoft vsix installer is responsible for installing extensions and any dependencies an extension has. The only dependancy visual micro has is C++ and for that we just tell microsoft we need their c++ extension.

The visual studio extensions are .vsix files. You can download the visual micro .vsix extension from the visual studio gallery. A .vsix file is just a zip file and when the vsix installed runs it unpacks to whatever folder it wants and then configures visual studio to load the extension.

Extensions are uninstalled from "tools>extensions and updates" which again uses the vsix installer to uninstall. When an extension is uninstalled it disappears from the list in extensions and updates.

The Help>About window in visual studio confirms which extensions and VS tool chains you have installed.

To be honest it sounds like a bug in VS 2017 possibly caused by the vsix installer but can't really be attributed to Visual Micro.

Quote:


I don't understand this? There isn't a v17 and what does "and higher" mean?

Quote:


You didn't create/build a project and try any of visual micro so maybe worth exploring sometime. It's much faster build system and many other helpful features.

No probs, thanks for the update.