DevOps is about increasing efficiency and eliminating barriers. There’s a lot of convenience in deploying directly from Visual Studio Team Services into the Azure cloud. With plugin based build and release pipelines, it’s very easy to quickly configure a release and see the results online. You can quickly configure a release to deploy to Azure and the wizards and settings will automatically configure the necessary permissions and credentials in the two systems. Everything just works … unless you’re running VSTS in a separate account or environment from the target Azure subscription. In this post, I’m going to walk you through the black art of manually connecting VSTS to an Azure subscription to enable automated release and deployment pipelines.
To demonstrate the problem and how to fix it, we’re going to create a very simple Release pipeline. In VSTS, begin by opening Build & Release. From there, you can choose Releases and create a new release definition by pressing the large “+” on the page and choosing to create a release definition.
Begin with an empty definition.
For the purposes of this demo, you do not need to associate it with any build artifacts. You can select Choose Later.… Read more
There is much choice when it comes to Business Intelligence (BI) products these days. In this webinar session, you will learn about Microsoft’s Business Intelligence Platform, and get a wealth of tips and tricks to make your life easier and keep your customers happy.
In this webinar, you’ll learn:
Docker has grown wildly in the last few years. It’s gone from a fledgling startup to a billion-dollar company, and now it’s got the attention of the enterprise. A number of changes have happened at Docker too – there’s been a leadership transition as well as Docker giving many of its core components over to the open source community to be managed there. All this change has set the stage for the next chapter in Docker history. Docker at DockerCon 2017 announced a new initiative that is aimed to take containers to the next frontier through the Moby Project.
The Moby Project has bold ambitions. It seeks to expand containers to include not only applications, but also core system components as well on an operating system. Docker says, “Moby is a framework to assemble specialized container systems. It has a library of containerized components and a framework for assembling these components into a standalone container platform.” Traditionally, containers were subsequent to an operating system – it would boot, load the container engine, then load containers that hosted applications like databases, message queues, and web servers. Moby intends to containerize things like DHCP servers, DNS servers, and so on such that they too can be pulled and plugged in much the same way of traditional containers to build custom operating systems.… Read more
Since we looked at installing in the previous post, and the steps are the same, I will omit that from this post. We’ll just focus on all the awesome R tools Visual Studio provides for you.
Similar to Python, when we installed the data science tools we get an “R” section in our templates. If you go there you’ll see something like this:
Only one template to choose from, but that’s ok! That is all we need.
Just like there’s a Python Interactive, there’s also an R Interactive window. It acts very similar to the Python Interactive, as well. Just highlight or put your cursor on the line in a script you want to send to the interactive and hit
Ctrl+Enter. Of course, you can just type directly into the interactive to get some quick result or feedback on a piece of code. Oh, and there is syntax highlighting and intellisense right in the interactive!
Like all applications in Visual Studio, just hitting the green “Run” button will execute your code.… Read more
Containers are cool – and everyone and their mother is trying to get on board with them. While many applications are natural fit for containers in many cases, it feels like some applications are forced into containers so vendors can say, “Hey look at me! I do containers too!” This is particularly true of database vendors who are using container hype to sell their software. Imagine for a moment this not so unrealistic anecdote: your CEO just got back from a conference and heard all the really cool things that you can do with containers. He or she gives the edict to IT to containerize everything because he or she heard the sales pitch: “Containers can unify DevOps pipelines for databases, apps, and resources in IT. Containers are easier and faster to setup and install compared to virtual machines. Containers lower management needs and hardware requirements relative to VM’s by reducing infrastructure. All of this means huge costs saving. Wow! Aren’t containers great!?” So now, you’re faced with this edict and you have to figure out how to take a massive MS-SQL cluster, and containerize it… or do you?
Perhaps not on this scale, but this scenario is one that enterprises are facing every day.… Read more
ASP.NET Core offers the exciting ability to develop, test, and deploy on different platforms. In this 1-hour webinar with Jason Bell, you will learn how to use Docker to create a consistent testing and deployment target for ASP.NET Core applications. You will also examine a real-world case study application that uses Amazon’s EC2 Container Service.
In this webinar, you’ll learn:
Did you like this webinar? Check out our ASP.NET Core with Docker live, 2-day virtual course.
To perform the demonstrations as shown during the webinar, you must have the Docker tools installed for your platform (the Community Edition is fine). You can find a download for each supported platform here: https://www.docker.com/get-docker.
Yep, you read that right. Visual Studio isn’t the first thing you think of when you hear “data science”, but that may just change soon. In Visual Studio 2017 they have included several tools together where you can do Python, R, and F# data projects for analysis and visualizations.
In this post we’ll go over how to use Python that you can get with Visual Studio and all the tools that you can use that comes with it.
First thing’s first, you need the tools before you can use them. You can go this with Visual Studio Community Edition, which is free to use, so no MSDN subscription or anything is required to get started.
When you run the downloaded installer, just make sure you check the
Data Science and Analytical Applications section:
After installing, you now have access to quite a few more project templates to choose from.
That’s a good amount! Let’s go through a bit of each of the Python and R templates and see what all they give us.
Here’s what the current list of Python templates look like.
The GitHub repo used in this article can be found here.
One of the lesser known features of Docker is its ability to do cloud builds based on WebHooks from GitHub and Bitbucket. Bitbucket and GitHub integration works in Docker natively so that when code is pushed to a repository, Docker will download and deploy the code and build the image on Docker hub automatically with Docker Automated Builds.
Setting it up is easy. Logon to Docker Hub, and you can select from the Create menu, select Create Automated Build.
This will take you to a page with two big buttons – one for Github and one for Bitbucket. Both work the same way – You first link your Github account with the Docker Hub account. This process is pretty straight forward. Once you link the accounts, you can now select the GitHub or Bitbucket repository you want to use. Once you select the repository, you can now create the build integration. Name the Docker Hub repository whatever you want then click Create.
Now, you can git push your app to GitHub or Bitbucket with git, and it will then trigger a build on Docker Hub. The push will need to include a Dockerfile in the root of the git repo.… Read more
I have been interested in mobile development for several years now. I have dipped my toes into the waters of mobile development here and there. Recently, I have completed my Xamarin certification exam; so now I am legit. I would just like to highlight a bit of that journey.
My interest for mobile development started after I bought my first smartphone, the Motorola DROID. Does the LG Voyager count?? Anyway, once I bought my DROID, I was in love. Besides having access to a whole app ecosystem finally, I could also create apps for my phone. So with stars in my eyes and the sky as the limit, I started digging into Android development. Android apps would require that I say hello again to my old friend Java, which I had not touched since college. Given I had been working with C# for the last few years, switching back to Java would require a bit of a mental shift especially since I would need to learn Android concepts. The end all, be all was that I read a few books, did some tutorials but honestly, I couldn’t see myself getting into doing Java development for creating Android applications.… Read more
One of the most anticipated announcements in the Docker space when it comes to building images is Multi-Stage builds because of the huge benefits it gives to CI/CD pipelines in DevOps. Before this announcement, building software in a container usually involved creating a container with all the SDK’s and compilers in the container, uploading code into the container, compiling it, creating a drop, then building another container with just the runtime that sucks in the compiled code to run. This pattern required an external tool and storage to build the container image so it was more burdensome.
Multi-Stage builds on Docker though provide a mechanism for moving the output of a build from a builder container into another container that can be used for running. Consider the following the example. This Dockerfile builds a .NET core app in one container then packages it in another.
#Builder FROM microsoft/dotnet:1.1.2-sdk-jessie COPY /myapp /myapp RUN dotnet restore ./myapp && \ dotnet build -c release ./myapp && \ dotnet publish -c release -o pubdir ./myapp #Final Build FROM microsoft/dotnet:1.1.2-runtime COPY --from=0 /myapp/pubdir /myapp ENV ASPNETCORE_URLS http://+:80 ENTRYPOINT ["dotnet", "/myapp/myapp.dll"] EXPOSE 80
This file has two FROM instructions, which in a traditional Dockerfile only one is a allowed.… Read more