This Saturday, 12th January, I got a chance to talk about Azure DevOps at a local meetup. The event was about Azure DevOps Launch & the session was about CI/CD and the title for my session was: Let’s Build LOLSystems : Complete CI/CD in Action. LOL-System is a custom I bought for my fictitious company used for demo purpose. I showed how we can setup CI/CD for ASP.NET Core application in Azure DevOps and deploy it to Azure Web Apps.
My friend Prachi tagged me on this meme on Facebook and I couldn’t agree more with her. When I started my career, my entire version control was folders – zipped, tagged and stored on multiple hard-disks. But then things changed. My guru Raj, enlightened me about advantages of version control systems. I learned about how multiple people can collaborate on projects or how errors can be reversed by going through code history if version controls like Team Foundation Server or GitHub are used. I started using those and these days, all my projects and samples are either in Visual Studio Team Services or in GitHub repository. Going one step ahead, I’m using Visual Studio Mobile Center for DevOps along with these version control systems.
But what is this all about? How it helps in building successful mobile applications? And I thought about answering these questions in a video series. The goal is to explain mobile DevOps and different steps in mobile DevOps in small (less than 10 mins) videos. After completing this series, you’ll be able to build cross-platform Xamarin.Forms mobile application, which will consume Microsoft Cognitive Service and set-up mobile DevOps for the same.
To follow along with this series, I’m recommending following minimum hardware/software combination:
Intel i5, 8GB, 50GB machine with Hyper-V support & Windows 10 Professional
MacBook or MacMini with i5, 4GB, 50GB for compiling iOS apps
Visual Studio 2017 Community Preview
With these hardware/software additional services used in this series are: