1. Open **Visual Studio Installer**
1. Note down which edition of Visual Studio you have installed (eg `Professional` or `Community`)
1. Click **Modify**
1. Click **Individual Components**
1. Locate the **Development activities** heading
1. Check the **Visual Studio C++ core features** component:
[![Location][1]][1]
1. Click **Modify**
1. Spy++ might now reside in the following paths, once you substitute the `{edition}` placeholder with your Visual Studio edition

        C:\Program Files (x86)\Microsoft Visual Studio\2017\{edition}\Common7\Tools\spyxx.exe
        C:\Program Files (x86)\Microsoft Visual Studio\2017\{edition}\Common7\Tools\spyxx_amd64.exe


  [1]: https://i.stack.imgur.com/4wvpG.png


It&#39;s part of the C++ profiling tools component.

Using the `dotnet` command line tool, how can I add a reference to an existing local package that is *not* downloaded with NuGet?

I have tried adding a local package to a project `bar` with `dotnet`:

```lang-none
dotnet add package /Users/sakra/foo/bin/Debug/foo.1.0.0.nupkg
```

The package `foo.1.0.0.nupkg` has been created with `dotnet pack` in a different project. The command `dotnet add package` however tries to download the file `foo.1.0.0.nupkg` from https://api.nuget.org/ which of course fails.


Add a package with a local package file in &#39;dotnet&#39;

I define the timer in each my-progress, used to update the value of view, but the console shows the value of the constant changes, and the value of view is still not changed, how can I do in the timer to change the value of view

    Vue.component(&#39;my-progress&#39;, {
        template: &#39;\
    			&lt;div class=&quot;progress progress-bar-vertical&quot; data-toggle=&quot;tooltip&quot; data-placement=&quot;top&quot;&gt;\
    				&lt;div class=&quot;progress-bar&quot; role=&quot;progressbar&quot; aria-valuenow=&quot;0&quot; aria-valuemin=&quot;0&quot; aria-valuemax=&quot;100&quot; :style=&quot;{height: pgvalue}&quot;&gt;{{pgvalue}}\
    				&lt;/div&gt;\
    			&lt;/div&gt;\
        	&#39;,
        data : function(){  
      
        	return {
        		pgvalue : &#39;50%&#39;,
                intervalid1:&#39;&#39;,
        	}
        },
        computed:{
    
            changes : {
                get : function(){
                    return this.pgvalue;
                },
                set : function(v){
                    this.pgvalue =  v;
                }
            }
        },
        mounted : function(){
          
        	this.todo()		
        },
        beforeDestroy () {
          
           clearInterval(this.intervalid1)
        },
        methods : {
                 
        	todo : function(){    		
        		this.intervalid1 = setInterval(function(){
        			this.changes = ((Math.random() * 100).toFixed(2))+&#39;%&#39;;
        			console.log (this.changes);
        		}, 3000);
        	}
        },
    })

here is the link:
[jsbin.com/safolom][1]


  [1]: http://jsbin.com/safolom/edit?html

how to use setInterval in vue component

### Background

I am looking for Spy++. I believe it should be included in Visual Studio 2017 since the latest Visual Studio help content references it:
https://docs.microsoft.com/en-us/visualstudio/debugger/introducing-spy-increment.

### Problem

I have just done a clean install of Visual Studio 2017, but Spy++ does not exist in the file system. I can&#39;t find it.

### Question

So I guess I need to select certain &quot;workflows&quot; when installing Visual Studio to have Spy++ installed? Anyone know if this is correct? And if so, which workflow/feature do I need?

### Setup

* Windows 10
* Visual Studio Professional 2017 15.1 (26403.3)


How do I get Spy++ with Visual Studio 2017?

<h5 id="background"><a aria-hidden="true" tabindex="-1" href="#background"><span class="icon icon-link"></span></a>Background</h5>
<p>I am looking for Spy++. I believe it should be included in Visual Studio 2017 since the latest Visual Studio help content references it:
<a href="https://docs.microsoft.com/en-us/visualstudio/debugger/introducing-spy-increment" target="_blank" rel="noopener noreferrer">https://docs.microsoft.com/en-us/visualstudio/debugger/introducing-spy-increment</a>.</p>
<h5 id="problem"><a aria-hidden="true" tabindex="-1" href="#problem"><span class="icon icon-link"></span></a>Problem</h5>
<p>I have just done a clean install of Visual Studio 2017, but Spy++ does not exist in the file system. I can't find it.</p>
<h5 id="question"><a aria-hidden="true" tabindex="-1" href="#question"><span class="icon icon-link"></span></a>Question</h5>
<p>So I guess I need to select certain "workflows" when installing Visual Studio to have Spy++ installed? Anyone know if this is correct? And if so, which workflow/feature do I need?</p>
<h5 id="setup"><a aria-hidden="true" tabindex="-1" href="#setup"><span class="icon icon-link"></span></a>Setup</h5>
<ul>
<li>Windows 10</li>
<li>Visual Studio Professional 2017 15.1 (26403.3)</li>
</ul>


What is the location of file:

    VCVARSALL.BAT

for Visual studio 2017?


VCVARSALL.BAT for Visual studio 2017

With the move from `project.json` to the new `csproj` format introduced with VS2017, I&#39;m struggling to understand the difference between the `dotnet` cli and the new `msbuild` and when to use one over the other.

1) To build a new `csproj` netstandard library from the command line, should I be calling the `dotnet` cli (for example `dotnet restore` `dotnet build`) or use `msbuild` (for example `msbuild ExampleNetstandard.sln`).
 
2) Also, my understanding is that there are two versions of `msbuild`, one built on the full framework and another targeting `dotnet core`. Is this correct? Should I always use the `dotnet version`

3) Is `dotnet cli` standalone or does it require `msbuild` to be installed?. For instance when you install the dotnet SDK does this install msbuild as well? If so is this different to the version that is installed with vs2017?

Relationship between the dotnet cli and the new vs2017 msbuild

Setting `OutputPath` in the new Visual Studio 2017 project format automatically adds the target framework in the path. For example, if I have these set in the project file:

    &lt;TargetFramework&gt;net462&lt;/TargetFramework&gt;
    &lt;OutputPath&gt;/build/debug/&lt;OutputPath&gt;

The actual output folder will resolve to `/build/debug/net462/`, not `/build/debug/` like in the older versions.
How do I solve this without workarounds like moving things around with post build actions?




How do I set `OutputPath` in a Visual Studio 2017 project (new .csproj file format) without the target framework cluttering the resolved path?

In &quot;old school&quot; MSBuild projects - as still used by Windows Forms in VS2017 for example - files could be &quot;nested&quot; via a `DependentUpon` item in the csproj file.

I used this to group unit tests together in Noda Time, e.g.

    &lt;Compile Include=&quot;LocalDateTest.PeriodArithmetic.cs&quot;&gt;
      &lt;DependentUpon&gt;LocalDateTest.cs&lt;/DependentUpon&gt;
    &lt;/Compile&gt;

That led to easily-navigable tests:

[![Nested tests][1]][1]

I knowingly &quot;lost&quot; this feature when moving to `project.json` for .NET Core, but had hoped it would return when converting to MSBuild. However, it looks like MSBuild projects based on the .NET Core SDK (root element `&lt;Project Sdk=&quot;Microsoft.NET.Sdk&quot;&gt;`) don&#39;t get the same treatment in Visual Studio 2017, even if an `ItemGroup` is added manually with the same elements as the &quot;old school&quot; project.

ASP.NET Core projects receive automatic nesting for minified CSS and Javascript, but it&#39;s not clear how to apply that to C# in .NET Core library projects.


  [1]: https://i.stack.imgur.com/mXuFy.png

Can files be nested in VS2017 Solution Explorer for .NET Core (non-ASP.NET Core) projects?

I just installed Windows 10 Creators Update (version 10.0.15063).

I have multiple versions of Visual Studio installed (2012, 2013, 2015 and 2017). I installed VS 2017 only a couple weeks ago.

### Problem

CMake (version 3.8.1) no longer finds the C/C++ compiler when run inside a &quot;VS2015 x64 Native Command Prompt&quot; (it _does_ work properly when run inside a VS 2017 command prompt).

### Reproduction

Content of `CMakeLists.txt`:

&lt;!-- language: lang-none --&gt;

    project (test)
    add_executable (test test.cpp)

(Content of `test.cpp` is irrelevant.)

CMake invocation, in a VS2015 x64 Native Command Prompt:

&lt;!-- language: lang-none --&gt;

    &gt; mkdir build
    &gt; cd build
    &gt; cmake -G &quot;Visual Studio 14 2015 Win64&quot; ..

CMake output:

&lt;!-- language: lang-none --&gt;

    -- The C compiler identification is unknown
    -- The CXX compiler identification is unknown
    CMake Error at CMakeLists.txt:1 (project):
      No CMAKE_C_COMPILER could be found.

    CMake Error at CMakeLists.txt:1 (project):
      No CMAKE_CXX_COMPILER could be found.

    -- Configuring incomplete, errors occurred!
    See also &quot;D:/dev/cmaketest/build/CMakeFiles/CMakeOutput.log&quot;.
    See also &quot;D:/dev/cmaketest/build/CMakeFiles/CMakeError.log&quot;.

### Analysis

The reason of the failure is clear when looking at `CMakeFiles/CMakeError.log`:

&lt;!-- language: lang-none --&gt;

    ClCompile:
      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\CL.exe /c /nologo /W0 /WX- /Od /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo&quot;Debug\\&quot; /Fd&quot;Debug\vc140.pdb&quot; /Gd /TC /errorReport:queue CMakeCCompilerId.c
      CMakeCCompilerId.c
    Link:
      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\link.exe /ERRORREPORT:QUEUE /OUT:&quot;.\CompilerIdC.exe&quot; /INCREMENTAL:NO /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /MANIFEST /MANIFESTUAC:&quot;level=&#39;asInvoker&#39; uiAccess=&#39;false&#39;&quot; /manifest:embed /PDB:&quot;.\CompilerIdC.pdb&quot; /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:&quot;.\CompilerIdC.lib&quot; /MACHINE:X64 Debug\CMakeCCompilerId.obj
    LINK : fatal error LNK1158: cannot run &#39;rc.exe&#39; [D:\dev\cmaketest\build\CMakeFiles\3.8.1\CompilerIdC\CompilerIdC.vcxproj]

`rc.exe` (Resource Compiler) is not found. Indeed, in the same VS 2015 command prompt:

&lt;!-- language: lang-none --&gt;

    &gt; where rc.exe
    INFO: Could not find files for the given pattern(s).

While it _is_ found in a VS 2013 command prompt:

&lt;!-- language: lang-none --&gt;

    &gt; where rc.exe
    C:\Program Files (x86)\Windows Kits\8.1\bin\x64\rc.exe
    C:\Program Files (x86)\Windows Kits\8.1\bin\x86\rc.exe

and a VS 2017 command prompt:

&lt;!-- language: lang-none --&gt;

    &gt; where rc.exe
    C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64\rc.exe

Checking the content of the `PATH` environment variables in various VS command prompts:

- Inside a VS 2013 command prompt, `PATH` contains

    &lt;!-- language: lang-none --&gt;

        C:\Program Files (x86)\Windows Kits\8.1\bin\x64

- Inside a VS 2017 command prompt, `PATH` contains

    &lt;!-- language: lang-none --&gt;

        C:\Program Files (x86)\Windows Kits\10\bin\x64
        C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64

- But inside a VS 2015 command prompt, `PATH` only contains

    &lt;!-- language: lang-none --&gt;

        C:\Program Files (x86)\Windows Kits\10\bin\x64

  which does not contain `rc.exe`.

### Questions

1. Is this a known issue or is it specific to my system?

2. What could Windows 10 Creators Update possibly install, uninstall or alter in the system (perhaps something related to Windows SDKs) that would trigger this problem?

3. What is a clean way to resolve this?

Edit: Installed VS 2017 components:

[![VS 2017 components installed][1]][1]


  [1]: https://i.stack.imgur.com/SqSCn.png

Content Type	Original Author	Original Content on Stackoverflow
Question	Sam	View Question on Stackoverflow
Solution 1 - Visual Studio-2017	Sam	View Answer on Stackoverflow
Solution 2 - Visual Studio-2017	James Barrass	View Answer on Stackoverflow

How do I get Spy++ with Visual Studio 2017?

Visual Studio-2017 Problem Overview

Background

Problem

Question

Setup

Visual Studio-2017 Solutions

Solution 1 - Visual Studio-2017

Solution 2 - Visual Studio-2017

how to use setInterval in vue component

Add a package with a local package file in 'dotnet'

Attributions