ASP.NET Core Module is not installed on the new Visual Studio 2017 image

James Skimming's Avatar

James Skimming

13 Mar, 2017 01:24 PM


Can you please install the ASP.NET Core Module onto the Visual Studio 2017 image? It must have been installed on previous images.


As part of our CI build we deploy an ASP.NET Core app to the local IIS and execute some integration tests, previously this worked fine, but since the upgrade to VS 2017 this now fails.

I've investigated, via RDP onto the build worker, and found that the new image does not have the ASP.NET Core Module installed (a.k.a ANCM).


I've work around this by adding the following commands to our appveyor.yml

  - appveyor DownloadFile
  - DotNetCore.1.0.3_1.1.0-WindowsHosting.exe OPT_INSTALL_REDIST=0 /install /passive /log ANCMInstall.log
  - appveyor PushArtifact ANCMInstall.log

Our build now works correctly. Can you please install the ASP.NET Core Module into the image?

A point of note

This is not strictly related the issue above, I just thought it worth mentioning.

I'm not sure why, but using the suggested download link for the ASP.NET Core Module didn't work, maybe because it's a 302 to the URL I used above. If you're interested, here's the error log I received:

Running Install scripts
appveyor DownloadFile
Calls one batch program from another.
CALL [drive:][path]filename [batch-parameters]
  batch-parameters   Specifies any command-line information required by the
                     batch program.
If Command Extensions are enabled CALL changes as follows:
CALL command now accepts labels as the target of the CALL.  The syntax
    CALL :label arguments
A new batch file context is created with the specified arguments and
control is passed to the statement after the label specified.  You must
"exit" twice by reaching the end of the batch script file twice.  The
first time you read the end, control will return to just after the CALL
statement.  The second time will exit the batch script.  Type GOTO /?
for a description of the GOTO :EOF extension that will allow you to
"return" from a batch script.
In addition, expansion of batch script argument references (%0, %1,
etc.) have been changed as follows:
    %* in a batch script refers to all the arguments (e.g. %1 %2 %3
        %4 %5 ...)
    Substitution of batch parameters (%n) has been enhanced.  You can
    now use the following optional syntax:
        %~1         - expands %1 removing any surrounding quotes (")
        %~f1        - expands %1 to a fully qualified path name
        %~d1        - expands %1 to a drive letter only
        %~p1        - expands %1 to a path only
        %~n1        - expands %1 to a file name only
        %~x1        - expands %1 to a file extension only
        %~s1        - expanded path contains short names only
        %~a1        - expands %1 to file attributes
        %~t1        - expands %1 to date/time of file
        %~z1        - expands %1 to size of file
        %~$PATH:1   - searches the directories listed in the PATH
                       environment variable and expands %1 to the fully
                       qualified name of the first one found.  If the
                       environment variable name is not defined or the
                       file is not found by the search, then this
                       modifier expands to the empty string
    The modifiers can be combined to get compound results:
        %~dp1       - expands %1 to a drive letter and path only
        %~nx1       - expands %1 to a file name and extension only
        %~dp$PATH:1 - searches the directories listed in the PATH
                       environment variable for %1 and expands to the
                       drive letter and path of the first one found.
        %~ftza1     - expands %1 to a DIR like output line
    In the above examples %1 and PATH can be replaced by other
    valid values.  The %~ syntax is terminated by a valid argument
    number.  The %~ modifiers may not be used with %*
DotNetCore.1.0.3_1.1.0-WindowsHosting.exe OPT_INSTALL_REDIST=0 /install /passive /log ANCMInstall.log
'DotNetCore.1.0.3_1.1.0-WindowsHosting.exe' is not recognized as an internal or external command,
operable program or batch file.
Command exited with code
  1. Support Staff 1 Posted by Feodor Fitsner on 13 Mar, 2017 07:59 PM

    Feodor Fitsner's Avatar

    Thanks for the suggestion! It's been installed into Visual Studio 2017 image.

  2. 2 Posted by James Skimming on 14 Mar, 2017 01:16 PM

    James Skimming's Avatar

    Great thanks

  3. James Skimming closed this discussion on 14 Mar, 2017 01:16 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac