Almost a year ago now, I introduced RedStar.Amounts, a .NET library to handle units and amounts in an easy way. The code It allows you to explicitly state what unit a certain amount is measured in. So instead of doing this: var lengthInCm = 400; You can do this: var length = new Amount(400, LengthUnits.CentiMeter); What’s more, you can perform calculations without having to wonder what the unit is: var length = new Amount(1000, LengthUnits.CentiMeter); var width = new Amount(1,
If you’re working in the .NET stack regularly and don’t know AppVeyor yet, it’s definitely worth checking out. AppVeyor is a CI system focused in .NET projects. You can easily link it to GitHub, Bitbucket and Visual Studio Online. It can build your project, run tests, deploy, and… publish to NuGet. This is what I will cover in this post today. When you have a piece of code that is repeated across two or more projects, it can be interesting,
How many times have you had to ask a colleague what unit that external application is using? Or worse, had bugs because you forgot to divide by 100? In many applications, it is common to change values when they are received by dividing or multiplying them. This is done because the other application uses centimeters, while our application uses meters, or some similar difference. There are libraries that mitigate this, but I didn’t find one to my liking. I’ve used
NuGet is a great way of handling dependencies. It isn’t perfect, but if you’ve experienced the days of DLL hell, you know NuGet hell is at least more manageable. One step that I’ve found was always missing, is automating the publishing of your NuGet package. We’ve played around with different scripts in the past, bat files and PowerShell files, but it was always a bit hacked together. And it always required several manual steps when a new project was created.