One of the strengths of Azure DevOps is that it’s very scalable. It can be configured to work for company of all sizes: from small teams of a few people, to a large enterprise with thousands of users.
When we work in complex environment we should follow the best practices to choose how to organize people and projects on our Azure DevOps Organization. This is a great piece of documentation to get started when we work in an enterprise scenario and I recommend reading it.
With this kind of setup is common that customers ask me to provide a way to limit visibility of work-items. This way only some people could access some work items. This is to provide better focus to teams, for example. But your project could have other needs to do this.
Today it’s an important day because it’s six months that I’m working at Microsoft and it’s the end of the probationary period.
I’ll remember forever my first day when I entered from main entrance at the Microsoft House in Milan and asked for a temporary badge because I was a new hire. One year and half before I entered the same door to attend a free workshop about Desktop Bridge and asked for a guest badge. I looked at everything with different eyes and many emotions. Life can be very rewarding if you have an objective and you work for it.
That day, I put the badge onto a sensor near a door and the door opened, I thought: “It’s real! I’m not dreaming!”.
In previous posts I documented some features of VSTS and a few scenarios of Application Lifecycle Management.
If you like VSTS it’s likely that you want to move your existing project from your current platform to VSTS. I’m currently planning a migration from JIRA to VSTS at work and here I am to share my findings.
In this post we’re going to explore how to get a full enterprise-grade development platform for free in 4 steps. Microsoft is offering for free the same environment that all of its sw engineers use every day to us. Continue reading →
dotnet is the base command of the SDK and it has many features like testing, nuget functionalites, managing dependencies and otheres. The new command is used to initialize new applications and we specify a console application and we want that application in the HelloCore directory. cd HelloCore moves into the newly created app directory.
View the code
With our favourite text editor we open Program.cs and we see that dotnet new has created a simple hello world app.
static void Main(string args)
> dotnet run
command we launch our first .Net Core app.
> Hello World!
.NET Core is a brand new implementation of .NET and it’s the multi-platform component of the .NET family.
With this blog post we explored the basic concepts of .Net Core. We also created our first app in 5 minutes.