Docker Tools for Visual Studio 2015 - Preview

Free

Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a Docker Container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

(11) Review
Visual Studio
2015
Download (28,675)
7/27/2016
0.31.0
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (11)
Q and A (66)
Sign in to write a review
Sort by:

by Crafty33 | Tue 11:50 AM

Version not updated. 0.31 expected ?

by netoisc | June 29 2016

Great! thanks for let us test and use new asp.net core-based applications on docker.

by aquatick | June 27 2016

guys, any way to publish to secure docker using this stuff or it's totally degraded?

by Sebas---- | May 31 2016

Great extension (started awesome, not anymore). Does not work out of the box with multi project solutions. Main project gets build and added to docker container, but the dependencies (other projects in the solution) do not.

0.12 <= version had a nicer integration with visual studio, "publish to" worked great with a on premise docker server. Later verions made it more of a problem since you had to add the remote docker host to docker-machine (every developer has to do this, annoying!).

Hope some day they bring back the "publish" feature, and keep the current docker-machine for local debugging of containers.

Microsoft Cloud Explorer June 14 2016
| Edit |
Delete

Hi Sebas,
We are just beginning to explore multi-container support. The challenge is launching a debugger across multiple containers. Possible, but we're still exploring. What you can do is build each project, and in the project/container you wish to debug, add the other image references. That assumes you're looking to run multiple containers for each project. If you're trying to compile multiple projects into one container, that would be good to know, and what's not working.
Steve Lasker
Blogs.msdn.com/SteveLasker

by Christopher Myers | May 18 2016

Really great work on this add-on team! The documentation and Channel 9 videos are extremely helpful as well.

by 张志勇-.NET | April 20 2016

by Vinay Date | April 19 2016

by Jacob Reid | March 31 2016

by Will 保哥 | March 27 2016

few typo in the description:
stteps => steps
Chnage => Change

Microsoft Cloud Explorer March 29 2016
| Edit |
Delete

Thanks will. Corrections made

by Madd_dog | March 15 2016

This not a review but wanted to respond to a "comment review".
If you have received "Visual Studio 2015 Tools for Docker Core requires Docker Toolbox" just reinstall docker using the gui.

by cocowalla | March 10 2016

When I try to install I get 'Visual Studio 2015 Tools for Docker Core requires Docker Toolbox' - even though Docker Toolbox is already installed.

Sign in to start a discussion


  • Could not start debugging
    4 Posts | Last post Wed 10:27 PM
    • Hi all,
      
      I'm running Win10, VS2015U3, Docker for Windows Beta 1.12.0-rc4-beta19 and Docker Tools 0.30.0 and had a hard time enabling the debugging for an Asp.Net app. Building the app in release mode worked fine, the container was created and the app running and reachable. 
      
      In Debug config I had first to rename Dockerfile.debug into Dockerfile.Debug in order to prevent this error: 
      Error response from daemon: Cannot locate specified Dockerfile: app/Dockerfile.Debug
      Build : Failed to build the image
      
      This was an easy fix (make sure to check the Dockerfile.debug is renamed in \bin\Docker\Debug\app folder as well) but then I ran into the next problem when launching in Debug config:
      
      The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use Microsoft.NETCore.App 1.0.0 or newer. This may be expected if the target process did not run .NET code.
      
      The container was created, but the app obviously not executed. I ran 'docker exec -it [containerId] bash' and realized that the app folder was empty. After spending some time in trial and error troubleshooting I succeeded by removing      
      the "volumes:      - .:/app" entry from docker-compose.Debug.yml. 
      
      Now debugging works fine, but I am wondering what side effects could occur by removing this entry.
      
      
    • We should have a workaround for the casing issue of the Dockerfile now in the 0.31 release, which is an issue we logged against Docker.  
      
      We do currently depend on volume mapping the app folder to support editing html or other static content and hitting refresh in the browser without having to bring down and reconstruct the container. This is supported via CTRL-F5 currently .  If you only care about F5, then removing that entry should be fine, however a better solution is bring up Docker for Windows via the tray icon, goto settings and share the Drive that you project resides on, which should also resolve the issue and will support both Edit/Refresh and Debugging scenarios. 
    • Thanks for the information Devin. I already enabled the shared drives in Docker for Windows app as part of my earlier investigations, but without success. My project is located on D drive and I enabled volume mapping for C and D drives in Docker client. 
      However, I am fine with it now. Most important thing for me is that debugging is working.
    • Same here, 
      
      _v0.31.0_ solved the **The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use Microsoft.NETCore.App 1.0.0 or newer. This may be expected if the target process did not run .NET code.** issue but still have problem with running Debug.  
      
      Once I deleted `volumes: - .:/app` entry from **docker-compose.Debug.yml** worked like a charm.
  • Visual Studio 2015 reports an update to 0.31
    3 Posts | Last post Wed 6:26 AM
    • Visual Studio 2015 notifications is reporting an available update, but the version here is still 0.30, and no other download location is provided. 
    • Same for me. Frustrating.
    • Apologize for this, the notification came out a bit earlier than expected. We updated the build earlier this evening.  
      
      Devin
  • Stuck @ Opening site http://docker .........
    3 Posts | Last post Tue 9:06 AM
    • Hi,
      
      I'm having an issue with running a Web Application in Debug as "Docker". The project is an out of the box ASP.NET Core Web Application (.Net Core) > Web Application. The project runs find with Debug > "IIS Express", but with Debug > "Docker" no joy. It just gets stuck @ Opening site http://docker .........
      
      I'm currently using Version 1.12.0-rc-beta16(build: 4760) of the Docker for Windows beta and version 0.21.0 of the Docker tools.
      
      I've removed the word 'default' from the docker.props file:
      
      <DockerMachineName Condition=" '$(DockerMachineName)'=='' "></DockerMachineName>
      
      and I have restarted visual studio afterward the change.
      
      Docker is running fine and running docker images in PowerShell, the images for the web application are listed. 
      
      Only potential issue I can see is that within the docker log files it reports that its "trying to rewrite IP addresses for port mapping for"
      
      Any help would be very much appreciated.
      
      Thanks 
      
      Steve
      
      
    • Hi Steve,
      
      Thanks for reporting this issue. I think this is the issue from Docker for Windows beta. If I am not wrong then http://docker is not getting set to the IP address of Docker for Windows beta. You can confirm it by running(F5 or Ctrl+F5) the app on docker and when it tries to open site http://docker, please check the logs by docker system tray icon > Right Click > Diagnosis > logs and search for ip address. Open the IP address and if it works then it would confirm it is a docker platform issue. We recommend you to go to their forum and report it.
      
      Thanks
      Saurabh
    • Hi,
      I am still getting http://docker page as blank page. I expose the port to 8080 and also removed the machine tag from Docker.props file. I tried running the core application from both VS2015 and power shell script but the result is same.
  • Error debugging with new basic project
    3 Posts | Last post July 21, 2016
    • Win 10, VS 2015 Update 3, Docker 2.0.5465, .NET core VS2015 tooling preview 0.30.40625.1
      1. Create a new .NET Core Web App->Api-> name StatefulValuesMicroservice
      2. Add Docker Support
      3. DEBUG
      
      I get an error on start up of project in DEBUG.  Is there something I am missing to get this to run?
      Failed to run the command: "c:\users\fname.lname\documents\visual` studio` 2015\Projects\StatefulValuesMicroservice\src\StatefulValuesMicroservice\DockerTask.ps1 -Run -Environment Debug -Machine '' -RemoteDebugging $True -OpenSite $False". Click for details.	
      
      Details
      c:\users\fname.lname\documents\visual` studio` 2015\Projects\StatefulValuesMicroservice\src\StatefulValuesMicroservice\DockerTask.ps1 -Run -Environment Debug -Machine '' -RemoteDebugging $True -OpenSite $False
      VERBOSE: Setting: $env:CLRDBG_VERSION = "VS2015U2"
      VERBOSE: Setting: $env:REMOTE_DEBUGGING = 1
      VERBOSE: Executing: docker-compose -f 'C:\users\fname.lname\documents\visual studio 
      2015\Projects\StatefulValuesMicroservice\src\StatefulValuesMicroservice\bin\Docker\Debug\app\docker-compose.Debug.yml' 
      -p statefulvaluesmicroservice up -d
      Recreating statefulvaluesmicroservice_statefulvaluesmicroservice_1
      
      ERROR: for statefulvaluesmicroservice  No such image: sha256:aeb30f095aef0906ca8e46d1789dfeceba0c5690bdb02e811ca9b4b29471eacf
      Encountered errors while bringing up the project.
      Run : Failed to start the container(s)
      At C:\users\fname.lname\documents\visual studio 
      2015\Projects\StatefulValuesMicroservice\src\StatefulValuesMicroservice\DockerTask.ps1:507 char:5
      +     Run
      +     ~~~
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Run
    • Ok, I think figured out part of it.  Searching around the internet and I found someone had a similar problem because they had IIS installed.  All they did to fix the issue was change the port because it was conflicting with IIS.
      
      So I changed in docker-compose.debug.yml :
      ********************************************
      from
      ********************************************
      version: '2'
      
      services:
        statefulvaluesmicroservice:
          image: username/statefulvaluesmicroservice:Debug
          environment:
            - REMOTE_DEBUGGING=${REMOTE_DEBUGGING}
          ports:
            - "80:80"
          volumes:
            - .:/app
      
      ********************************************
      To
      ********************************************
      version: '2'
      
      services:
        statefulvaluesmicroservice:
          image: username/statefulvaluesmicroservice:Debug
          environment:
            - REMOTE_DEBUGGING=${REMOTE_DEBUGGING}
          ports:
            - "8080:80"
          volumes:
            - .:/app
      
      ********************************************
      
      This seems to work and allow it to run something; 
      however, it seems to open a URL to http:docker.com.  
      
      Is this what is supposed to happen instead of it going to my api?
      
      Doing a docker ps, I see this in the details 0.0.0.0:8080->80/tcp .
      
      How do I get to my api? 
      
      I have tried:
      
      localhost:8080/api/values
      [my ip]:8080/api/values
      192.168.99.100:8080/api/values
      
      
      
      
      
    • I also had to configure another port than 80 because I am running IIS and SSRS on my local machine on port 80.
      
      1. Add the UseUrls method into Program.cs (before .UseKestrel())
                  var host = new WebHostBuilder()
                      .UseUrls(Environment.GetEnvironmentVariable("ASPNETCORE_URLS") ?? String.Empty)
                      .UseKestrel()
                      .UseContentRoot(Directory.GetCurrentDirectory())
                      .UseIISIntegration()
                      .UseStartup<Startup>()
                      .Build();
      
      2. Change port # in Dockerfile(.debug)
      # Configure the listening port to 5000
      ENV ASPNETCORE_URLS http://*:5000
      EXPOSE 5000
      
      3. Change port # in docker-compose(.debug.)yml
          ports:
            - "5000:5000"
      
      4. Your api should be available via http://localhost:5000/api/values or http://docker:5000/api/values
  • Debuger dont attach
    6 Posts | Last post July 20, 2016
    • Hello All,
      
      I have Windows 7, DockerToolBox 1.11.2, VirtualBox 5.1.0, VisualStudio 2015 Update3 and Docker Tools 0.30.0.
      
      I create new .NET Core web app. When I hit F5 to run in debug app is compiled, build image. Then I see window Debug is starting after while process fail. When I open browser app is not running. Than I can start app with docker exec... Strange is that when I ran docker ps while "Debug is starting" windows is in VS I don't see any running container. After process in VS fail I see that container is running.
      
      What I doing wrong?
      
      Thanks
      
      Docker output>
      C:\Users\mtomasov\Documents\Visual` Studio` 2015\Projects\DockerTest2\src\DockerTest2\DockerTask.ps1 -Run -Environment Debug -Machine 'default' -RemoteDebugging $True -OpenSite $False
      VERBOSE: Executing: docker-machine env default --shell powershell | Invoke-Expression
      VERBOSE: Setting: $env:CLRDBG_VERSION = "VS2015U2"
      VERBOSE: Setting: $env:REMOTE_DEBUGGING = 1
      VERBOSE: Executing: docker-compose -f 'C:\Users\user\Documents\Visual Studio 2015\Projects\DockerTest2\src\DockerTest2\bin\Docker\Debug\app\docker-compose.Debug.yml' -p dockertest2 up -d
      Creating network "dockertest2_default" with the default driver
      Creating dockertest2_dockertest2_1
      Error calling docker-machine ip for docker machine default. Check to see if it is running and accepting connections.Security error.
      
    • It looks like the reason VS is failing is that the call to docker-machine ip is failing so VS does not know what site to connect to. I have found that Virtual Box machine can be a bit strange around user privilege, so that may be what you are seeing. Are you running VS and the command prompt at the same privilege (i.e. both as normal user or both as admin)? If not stop the docker-machine, restart both processes at the same privilege and then restart then docker-machine. If that doesn't help, try running the docker-machine ip command yourself and see if that provides any more information as to why it is failing.
    • Yes both VS nad cmd run under normal user privilege. 
      
      When I run docker-machine ip in cmd where I'm started VM it return 192.168.99.100
      
      Here is log of docker-compose with verbose
      VERBOSE: Executing: docker-compose --verbose -f 'C:\Users\mtomasov\Documents\Visual Studio 2015\Projects\DockerTest2\src\DockerTest2\bin\Docker\Debug\app\docker-compose.Debug.yml' -p dockertest2 up -d
      compose.config.config.find: Using configuration files: C:\Users\mtomasov\Documents\Visual Studio 2015\Projects\DockerTest2\src\DockerTest2\bin\Docker\Debug\app\docker-compose.Debug.yml
      docker.auth.auth.load_config: File doesn't exist
      compose.cli.command.get_client: docker-compose version 1.7.1, build 0a9ab35
      docker-py version: 1.8.1
      CPython version: 2.7.11
      OpenSSL version: OpenSSL 1.0.2d 9 Jul 2015
      compose.cli.command.get_client: Docker base_url: https://192.168.99.100:2376
      compose.cli.command.get_client: Docker version: KernelVersion=4.4.12-boot2docker, Os=linux, BuildTime=2016-06-01T21:20:08.558909126+00:00, ApiVersion=1.23, Version=1.11.2, GitCommit=b9f10c9, Arch=amd64, GoVersion=go1.5.4
      compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- (u'dockertest2_default')
      compose.cli.verbose_proxy.proxy_callable: docker inspect_network -> {u'Containers': {},
       u'Driver': u'bridge',
       u'EnableIPv6': False,
       u'IPAM': {u'Config': [{u'Gateway': u'172.18.0.1/16',
                              u'Subnet': u'172.18.0.0/16'}],
                 u'Driver': u'default',
                 u'Options': None},
       u'Id': u'47544cd355a8cae1c64bebf6c10c613cf5c294475f84c908fb9410fb4898842c',
       u'Internal': False,
       u'Labels': {},
      ...
      compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={u'label': [u'com.docker.compose.project=dockertest2', u'com.docker.compose.oneoff=False']})
      compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 0 items)
      compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=dockertest2', u'co
    • compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={u'label': [u'com.docker.compose.project=dockertest2', u'com.docker.compose.oneoff=False']})
      compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 0 items)
      compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=dockertest2', u'com.docker.compose.service=dockertest2', u'com.docker.compose.oneoff=False']})
      compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
      compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'3fd3c16521a94b7d1f1b45c819a37930d77a5d79caebe720195fd8a333bab03b')
      compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'',
       u'Args': [u'-c',
                 u'if [ "$REMOTE_DEBUGGING" -eq 0 ]; then dotnet DockerTest2.dll; else sleep infinity; fi'],
       u'Config': {u'AttachStderr': False,
                   u'AttachStdin': False,
                   u'AttachStdout': False,
                   u'Cmd': None,
                   u'Domainname': u'',
                   u'Entrypoint': [u'/bin/bash',
                                   u'-c',
      ...
      compose.cli.verbose_proxy.proxy_callable: docker inspect_image <- ('username/dockertest2:Debug')
      compose.cli.verbose_proxy.proxy_callable: docker inspect_image -> {u'Architecture': u'amd64',
       u'Author': u'',
       u'Comment': u'',
       u'Config': {u'ArgsEscaped': True,
                   u'AttachStderr': False,
                   u'AttachStdin': False,
                   u'AttachStdout': False,
                   u'Cmd': None,
                   u'Domainname': u'',
                   u'Entrypoint': [u'/bin/bash',
      ...
      compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=dockertest2', u'com.docker.compose.service=dockertest2', u'com.docker.compose.oneoff=False']})
      compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
      
      
    • compose.cli.verbose_proxy.proxy_callable: docker inspect_image <- ('username/dockertest2:Debug')
      compose.cli.verbose_proxy.proxy_callable: docker inspect_image -> {u'Architecture': u'amd64',
       u'Author': u'',
       u'Comment': u'',
       u'Config': {u'ArgsEscaped': True,
                   u'AttachStderr': False,
                   u'AttachStdin': False,
                   u'AttachStdout': False,
                   u'Cmd': None,
                   u'Domainname': u'',
                   u'Entrypoint': [u'/bin/bash',
      ...
      compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'3fd3c16521a94b7d1f1b45c819a37930d77a5d79caebe720195fd8a333bab03b')
      compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'',
       u'Args': [u'-c',
                 u'if [ "$REMOTE_DEBUGGING" -eq 0 ]; then dotnet DockerTest2.dll; else sleep infinity; fi'],
       u'Config': {u'AttachStderr': False,
                   u'AttachStdin': False,
                   u'AttachStdout': False,
                   u'Cmd': None,
                   u'Domainname': u'',
                   u'Entrypoint': [u'/bin/bash',
                                   u'-c',
      ...
      compose.parallel.feed_queue: Pending: set([<Service: dockertest2>])
      compose.parallel.feed_queue: Starting producer thread for <Service: dockertest2>
      compose.service.start_container_if_stopped: Starting dockertest2_dockertest2_1
      compose.cli.verbose_proxy.proxy_callable: docker start <- (u'3fd3c16521a94b7d1f1b45c819a37930d77a5d79caebe720195fd8a333bab03b')
      compose.parallel.feed_queue: Pending: set([])
      ........
      compose.parallel.feed_queue: Pending: set([])
      Error calling docker-machine ip for docker machine default. Check to see if it is running and accepting connections.Security error.
      compose.cli.verbose_proxy.proxy_callable: docker start -> None
      compose.parallel.parallel_execute_iter: Finished processing: <Service: dockertest2>
      compose.parallel.feed_queue: Pending: set([])
    • compose.parallel.feed_queue: Pending: set([])
      Error calling docker-machine ip for docker machine default. Check to see if it is running and accepting connections.Security error.
      compose.cli.verbose_proxy.proxy_callable: docker start -> None
      compose.parallel.parallel_execute_iter: Finished processing: <Service: dockertest2>
      compose.parallel.feed_queue: Pending: set([])
  • C:\ vs other drives
    6 Posts | Last post July 13, 2016
    • using Docker for Windows, I used to be able to deploy and debug on my e:\ drive (which is where I keep my source on windows).  but since the latest update, it seems that it no longer works on e:\ but works fine on c:\ (which is an SSD with limited space).
      
      I have made sure that I have a shared my E:\ in the "Shared Drives" setting.
      
      if I run the DockerTask.ps manually:
      
      .\DockerTask.ps1 -Build -Environment Debug -Machine '' -ClrDebugVersion VS2015U2
      
      I end up with the following error (I don't get this error with any projects that I copy to a directory on c:\)
      
      Sending build context to Docker daemon 85.32 MB
      Error response from daemon: Cannot locate specified Dockerfile: app/Dockerfile.Debug
      Build : Failed to build the image
      At E:\Source\dotNetCore\TestDockerConsoleApp\src\TestDockerConsoleApp\DockerTask.ps1:415 char:5
      +     Build
      +     ~~~~~
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Build
      
      
    • I ran into this previously as well and logged an issue on Docker at -> https://github.com/docker/docker/issues/24348#issuecomment-230834106. Looks like it is still being investigated  
      
      You should be able to workaround this by changing the casing of the Dockerfile.debug to Dockerfile.Debug in solution explorer 
      
      Devin 
      
    • Hi Devin, Tried to rename to Dockerfile.Debug and still no dice.  Oh well, was hoping that would be a quickie fix.  that would get me past my immediate issue of having to put just my docker debugging on the C:\ while everything else is on e:\.
      
      I can live with it though :-)
      
      thanks for the suggestion.  I'll try some other tweaking to see if it helps.
    • Which Dockerfile.debug? This would need to be renamed in the bin\Docker\Debug\app folder if running the script outside of VS.   Have you tried a rebuild of the project in Visual Studio.   Also, what casing is the file in the bin\Docker\Debug\app folder? You could also try passing "debug" for the environment parameter if running  the script outside of VS.  Seems like the same issue that I and a couple of others have ran into.  FWIW, We will work around the casing issue in an upcoming release of this extension
          
    • That worked!  Just tweaked the bin\Docker\Debug\app\Dockerfile.Debug.
      
      so, now visual studio goes into debug.  but then fails because it cant see the container (I see the container in >docker ps).  Works ok on c:\.  but I was having some problems earlier with Docker for Windows flipping out, so maybe a reboot is required.
      
      This is the error I now receive.
      
      Error response from daemon: Container bf6a0bae3fec394c089ef7459aa67c48c5ace2c9364c0750d505f851dd414b49 is not running
    • All works here.  What I do once I create my project is set the Dockerfile.debug to Dockerfile.Debug so that when it builds, it will copy that out to the app directory with the proper case.
      
      my other problem where the docker daemon wasn't listening was because I had 1 to many VM's running on my machine at the time and was out of resources.
      
      All is working great now.  You are my new best friend!!!
  • some bugs
    2 Posts | Last post July 12, 2016
    • 1. doesn't support normal usernames. $env:TEMP for users like Sava.Dragos will end up beging in powershell something that docker can't interpret 
      2. Does it works with docker for windows?
    • I'm running Docker for Windows and wasn't able to repro this by setting $env:TEMP  to c:\users\devin.breshears\AppData\Local\Temp, restart VS and then F5 the web app.  If you can repro with Docker for Windows can you share the error message or log an issue at https://github.com/docker/docker if appears to be a Docker issue
  • Remotedebugging in 0.30.0
    3 Posts | Last post July 11, 2016
    • Hello,
      I just installed the whole .NET Core 1.0 with VS20155Upd3.
      I am running Docker on Win8.1 with Virtualbox.
      I was able to build the ASP.NET dockersample without any issues.
      But when I try to run the Application the remote debugging is always enabled.
      I may be too silly to disable the remote debugging. I tried setting the variable, but at no place I was able to disable it.
      The command to build is always:
      DockerSample10" --configuration Release --no-dependencies
      But the running the container is 
      DockerTask.ps1 -Run -Environment Release -Machine 'default' -RemoteDebugging $True -OpenSite $False
      
      Running the command from powershell without remote debugging works perfectly.
      ./DockerTask.ps1 -Run -Environment Release -Machine 'default'
      
      I checked also the debug launch settings, but cannot find the reason why the remote debugging is true in relase and debug Did I miss anything?
    • Thanks rgall. Remote debugging is enabled when you press F5 (Start Debugging). If you want to run the app w/o debugging you have to use Ctrl+F5(Start Without Debugging). That should work for you.
      
      I agree -RemoteDebugging $True is confusing for Release configuration. We will resolve it in our next release. But, for now, it does not affect any accepted behavior. It should not enable debugging if you try Ctrl+F5.
    • Thanks for the answer,
      Sometimes it is necessary to debug in release. Nothing wrong with that, but also Ctrl+F5 does startup with debug = true?
      This is what was confusing for me. I
  • Roadmap/Support Plans
    2 Posts | Last post July 08, 2016
    • What plans and roadmap exist for supporting traditional .NET and Windows server containers with this extension?
    • Hi J-Boyd,
      We are actively working on the Windows Container tooling, specifically targeting existing .NET 3.5, 4.6 workloads with Windows Server Containers, with debugging. We don't yet have a release date. I imagine you've already found http://aka.ms/WindowsContainers to get you started without the tools.  
      It would be great to hear what your expectations are for Windows Containers. What types of apps are you building. Web, API, Console, WebJobs. How many projects are built into the container. Are you saving files on the server? Do you use web.config transforms?...
      Thanks,
      Steve
  • What is "username" in Docker image name?
    2 Posts | Last post July 06, 2016
    • The default $ImageName val (and thus Docker image name) shows up as "username/<projectname>" where username literally the string "username". For example, adding Docker support to a new empty proj makes the image name come through literally as "username/WebApplication1".
      
      Why is that? I ask because I'm trying to tie it into a larger Docker project, but it's unclear what purpose that's serving.
    • Thanks amattie. You can update that string and put the repo name you want to push onto docker hub. After our tools scaffold this docker assets for you, you own them and you can try tweaking with them, according to your needs.
1 - 10 of 66 Items