As software creators we don't get to decide what version of our tools / libraries that people use. If we try to force them, our users will go somewhere else. Update: What Type of Software This Applies To This post talks of tools, applications and libraries. Things that end up in the users hands....
“Because everyone wants to kick their database, but sometimes kicking your database is a good thing!” Many would not argue that you should version your code, and few would argue against versioning your code in a way that can lead back to a specific point in source control history. However...
Easy and Instant deployments and instant scale for .NET? Awhile back a few of us were looking at Ruby Gems as the answer to package management for .NET . The gems platform supported the concept of DLLs as packages although some changes would have needed to happen to have long term use for the entire...
Posted to
Rob Reynolds - The Fervent Coder
by
Rob Reynolds
on 02-16-2011
Filed under: NHibernate, Fluent NHibernate, RoundhousE, HowTo, UppercuT, Development, Git, Tools, .NET, Agile, Gems, Challenge
In a previous post I mentioned how I was going to show you how UppercuT (UC) has the ability to make gems stupid simple to create and publish. You ask if gems can get any easier and to that I answer, “Why YES, they can!” How about just filling out the information for the gemspec, running...
The Ruby community has enjoyed a great user experience with a package management system they use called Gems. A gem is a package (or a library), compressed with some additional metadata, and can be either source files or binaries. Let’s focus on binary gems. We have the same concept in .NET (DLLs...