I’ve been a C#.NET developer since I graduated from college in 2006 and presently a lead DevOps engineer for HomeNet Automotive. I’ve always had a passion for DevOps even before it became a buzz word. Throughout my career, I’ve tried to bridge the gap between the developers, IT operations, and DBAs by either learning more about their world or building tools to bring the teams closer together. The last few years I’ve been focusing more on developing CI/CD pipelines for cloud and on premise projects. When I’m not busy being a DevOps engineer, you can find me teaching computer science part time at Montgomery County Community College. If you haven’t guessed it yet, I have a passion for technology.
Many places monitor the server that hosts their NuGet packages, but do you monitor what actually goes into your NuGet server? In this session, I’ll show you how to leverage NuGet.Core package to scan your NuGet server. We’ll take a look at how to check for crucial things like authors/owners, descriptions and project URLs are filled out correctly. In addition, I’ll show you how to generate a DGML diagram that shows the dependency graph for your NuGet packages. Then we’ll top it off with how to export the information into a nice report that can be distributed for all to see.
If you’ve ever written an application that generates a SQL command string to create a database, perform a backup, or setup permissions you’ve been doing it the hard way. Since SQL Server 2005, Microsoft has provided a library to programmatically interact with SQL Server. The library is known as SQL Server Management Objects or SMO. This is the same library that is used by SQL Server Management Studio (SSMS) and handles much of the “guess” work at generating SQL command text to do almost any kind of management you want. In this session, I’ll show you how to create SQL Server monitoring and management tools for environments that can’t afford commercial tools like Idera or Red Gate.