In this video, I demonstrated how to get started with .NET Core on OS X, Docker and Windows. In this post, I am going to go into a little more detail on how to get started on building a simple .NET Core application on various.
In my previous post, I went over the user interface and application requirements. Let’s quickly revisit the project requirements:
- Get coordinates of the users and identify which cloud the ASP.NET Core app is running on.
- Populate maps with custom pushpins.
- Display the number of containers running on each cloud.
A week ago I was part of a team that put together a demo for Microsoft Build Conference. The Where You At Demo was a cool little live demo that my team pulled together at Build 2016. The purpose of the demo was to show, that ASP.NET Core applications can run on any cloud.
Meet the team
Scott Hanselman : Demo visionary and presenter , Azure load balancer, and problem solver.
Steve Lasker : Demo visionary, cloud deployment, containers, Visual Studio Team Services , and API Services
Glenn Condron: API services and Azure Storage.
Maria Naggaga (me): User Interface , HTML5 & JS, and API calls .
User would visit WhereYouAt landing page and see the following:
- Logo of cloud on which this ASP.NET Core application is currently running.
- Ask user to provide their location.
The big reveal
The pins on the map represent every person who has participated in the demo. Each color represents a different cloud.
At the bottom of the page you will see three containers. The containers show the number requests received and allocated per cloud.
Three weeks ago after being a Technical Evangelist for three years , I joined the Visual Studio and .NET team as Program Manager . Moving from one great job to the next.
Joining the Visual Studio and .NET team has been amazing! Not only I am a part of a team that makes great developer and user experiences, I have presented in Hong Kong, and helped build a demo for Build 2016 within the first couple of weeks.
My post today is all about working on group projects. As remote a PM, my team is spread across multiple states and continents so, when working on a group project,I have to make sure that I can accurately explain and express my ideas.
Over the past week and a half leading up to Build, I learned so much on effective communication and project expectations . Here are my lessons.
Precision of language
Fearless Inventor current logo was created with the Notegraphy app
Please Listen to my first episode here(link available soon)
In my previous blog , I wrote about the new ASP.NET5. Before we get started on setting up our development environment and deploying our ASP.NET5 projects to the cloud it is important to understand how .Net is able to run on OS X and Linux.
I am really excited to be speaking at OSCON in Portland ! In my talk “ASP.NET5 isn’t just Enterprise”/ “Legacy What ?” I will be discussing and demoing the new ASP.NET 5(formerly vNext). By the end of the talk my hope is, the audience will have an understand of Microsoft OSS story with ASP.NET , Visual Studio Code, Sublime, and DNX. In this post I am going go over in more detail the what ASPNET5 is , What DNX is, and How to get a project up and running in Visual Studio Code and Sublime on a Mac and PC.
Before you read this post, I assume you have read getting started with a vNext project on a Mac.
ASP.Net vNext has been designed to be cloud ready. So, regardless of whether you are on Mac/linux/PC or using sublime or Visual Studio 2015 deploying a website with Github is going to be the same workflow.
Deploying ASP.Net vNext Project using GitHub
The first thing we want to do is hook-up your vNext Project from Github to Azure using Kudu (if you don’t have repository fork mine). This allows for continuous deployment from your Github repo to Azure. Kudu is the engine that can run within and outside of azure that allows for git/hg deployments, WebJobs, and various other features in Azure Web Sites. Kudu does this by generating deployment scripts under the hood and, deploy a website when pushing changes to a Github repo.