NuGet

Chocolatey Automatic Packages

I updated three packages this morning. I didn’t even notice until the tweets came in from @chocolateynuget. How is this possible? It’s simple. I love automation. I built chocolatey to take advantage of automation. So it would make sense that we could automate checking for package updates and publishing those updated packages. These are known as automatic packages. Automatic packages are what set Chocolatey apart from other package managers and I daresay could make chocolatey one of the most up-to-date ......
Posted On Thursday, January 3, 2013 1:15 AM | Comments (0)

this.Log– Source, NuGet Package & Performance

Recently I mentioned this.Log. Given the amount of folks that were interested in this.Log, I decided to pull this source out and make a NuGet package (well, several packages). Source The source is now located at https://github.com/ferventc... Please feel free to send pull requests (with tests of course). When you clone it, if you open visual studio prior to running build.bat, you will notice build errors. Don’t send me a pull request fixing this, I want it to work the way it does now. ......
Posted On Wednesday, December 19, 2012 11:21 PM | Comments (0)

Refresh Database–Speed up Your Development Cycles

Refresh database is an workflow that allows you to develop with a migrations framework, but deploy with SQL files. It’s more than that, it allows you to rapidly make changes to your environment and sync up with other teammates. When I am talking about environment, I mean your local development environment: your code base and the local database back end you are hitting. Refresh database comes in two flavors, one for NHibernate and one for Entity Framework. I’m going to show you an example of the one ......
Posted On Wednesday, December 12, 2012 5:08 PM | Comments (2)

Chocolatey - Guidance on Packaging Apps with Both an Install and Executable/Zip Option

One of the thoughts I've been considering recently with chocolatey is consistency with packages and naming conventions as chocolatey continues to grow. It's fine to name packages by the app/tool name, that's both intuitive and expected. What I am more interested in is when an application has multiple installation options (ie. an MSI and a ZIP). It can become confusing for people to install these when they don't know what they are getting if they call a package that has both. If you start with one ......
Posted On Saturday, February 25, 2012 12:01 PM | Comments (0)

Software Release Management - Why You Can’t And Shouldn’t Force People to Use the Latest Version

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. This does not apply to SaaS or websites. These do not end up in the hands of the users in the same sense. For those of you who immediately think of Chrome or Firefox, which are applications that end up in ......
Posted On Wednesday, January 25, 2012 10:28 AM | Comments (2)