Entries:
Comments:
Discussions:

Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Steve Lasker on Docker Tools for Visual Studio

24 minutes, 18 seconds

Download

Right click “Save as…”

Steve Lasker was kind enough to stop by our studio to preview some of the awesome (new) tools for Docker that you can use directly in Visual Studio. Docker (and containerization for that matter) is increasingly becoming a very important technology for developing scalable applications. Additionally, having the ability to specify the exact environment an application needs is revolutionizing the way we deploy and service applications (re the rise of DevOps). The new Visual Studio Tools for Docker are excellent for getting started with this important technology. Steve does a great walk-through on what is available today and what we can expect in the future. Enjoy!

Tag:

Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
    Unsubscribing
    Subscribing
  • For breakpoints, why can't just attach to process and start debugging?

  • Hi Niner,

    Because we're using NET Core, we don't yet have all the debugger components complete. Nor are they automatically deployed to the container image. Once they are in place, you could attach remotely. The experience I'm discussing here:

    • Wraps up the optional addition of the debugger components to the image
    • Sets the entry point of the container to be the debugger
    • Sets the debugger communication channel from VS to the running container
    • Hook this into the F5 experience so you don't need to do the extra steps of attaching, finding, etc. 

    Our goal is to enable container debugging remotely as well as locally. 

  • This is great!  With my own experimentation in docker I've been finding the database story really difficult to manage (at least if you want to stick with dotnet). If you listen to the folks over at kubernetes (for example) containers seem to be very "transient".

    How have you found people working with Docker and persistence so far?

    Are you seeing people include a database in their docker-compose files or are they leaving the persistence piece out of docker?

    We certainly can't get SQLSERVER on a container yet, SQLITE+EF isn't appropriate for someone hoping to run a scalable data solution. It's nice to see a postgre http://www.npgsql.org/doc/ef7.html connector is inbound... but I'm really interested to hear what others are working with in this space.

    Connection Strings to AZURE databases & SQLEXPRESS locally perhaps? (which brings back the risk of works on my machine, just try to do anything with SQL encryption)

    Vitesse (mysql) seems another really interesting data-solution for Core.NET as that is designed to be a container-y database (but the adaptor would need to be written)

  • Hi Alex,

    For SQLEXPRESS containers you should have a look at http://turbo.net.  I wish that was the way MS was headed with containers on servers but it seems it will be very different.

Remove this comment

Remove this thread

Close

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.