Yesterday I went live for the first time on YouTube. I improvised, literally, a session about the basics of Azure Kubernetes Service with the target objective to deploy an empty application starting from scratch.
The experiment was very intense because I had a couple of issues, but it delivered a not so bad result. Thank for my friends Giulio and Giuliano of getlatestversion.it for the feedback and for listening to me for almost an hour!
For this first stream I talked in Italian, but in the future when I’ll be more confortable I’ll swith to English to reach a broader audience.
recently Microsft published a list of video encoderstested for Live streaming with Microsoft Stream (http://bit.ly/LiveEnc).
One of this products is OBS Studio, a free and open source software for video recording and live streamig (https://obsproject.com/).
This is a great news and big improvement on live events direction compared to Skype for Business.
This area (meetings, meetings recording and live events) is definitely the one that I love in Teams (in conjunction with Stream).
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.
Azure Feeds used to be scoped to an organization. However, to enable public feeds and to become more consistent with the rest of Azure DevOps, feeds created through the new create feed UI are now project-scoped.
The only way to create an org-scoped Azure Artifact Feed is through API calls and it’s not reccomended.
If we want to share a feed with an entire organization this is what we need to do.
When referring to an image, an artifact, a registry, a tag, what exactly is the reference? Do we mean:
For the sake of clarity of communications, there are several elements that make up an artifact or image name, and they are fairly important when we think about artifacts moving from one registry to another. See Choosing a Docker ContainerRegistry for more context
Should we really refer to an image, tied to a specific location? As humans, would we really say the fully qualified name, or would we use shorthand references? And what terminology would, or should we use? There are several terms we use interchangeably, which I’ll call out their meanings:
Image / Artifact
Images & Artifacts
The first thing you may notice is I reference Images and Artifacts interchangeably. It turns out the infrastructure we use to store…
If your Windows 10 Search Bar is broken you’re encountering an issue that is spreading to many Windows 10 users at the time of this writing.
This is NOT an official statement (I’m not responsible for any side effects caused by this) about how to fix but running this script inside a PowerShell session with administrator privileges and restarting the machine can solve your issue (it worked on my machine).
The development platform is the production environment for the job of creating software. / Michael T. Nygard
When you work with many customers you start to collect your personal database about the best and worst practices that you see and how much they are spreaded.
A thing that is very common is that development or IT related activities are treated like second class citizens in the company. Low end laptops (some with traditional HDD and not SSD!), low budget for testing or QA environment. I can’t explain why this is happening… I suppose it’s a cultural issue. Let’s look at an analogy. Suppose your company CRM went down so people from the selling department couldn’t do their job. That would be at least a severity 2 outage!
So I couldn’t agree more with Nygard: treat IT tools as production because it really is production!
The Microsoft Visual Studio Setup Project is an old technology to create installer developed by Microsoft. It is out of support from nearly a decade and not present in Visual Studio anymore but when I visit customer sites I find legacy technologies and I need to deal with it on the short-term.
A couple of days ago I was working on an automated CI build on Azure DevOps and we hit an issue when trying to compile an old VDPROJ (migration to Wix in progress, btw ☺). We encountered an HRESULT 8000000A error.