Ramblings of a geek with a few hobbies…
As I mentioned last night, I made the 1.0.0 build of Chef and started doing some installation testing on Vista.
It’s official – Vista’s UAC is kicking my ass. It’s during the database setup that I’m having the problem. Sql Server gets installed OK, it’s for some reason the database restore that times out.
Kinda tired of running the sql express install at this point.
This evening I started to work on the registration process for Chef. There are so many ways to accept payments that it makes my head spin. A couple months ago I signed up for a RegNow account and they even waived the $20 setup fee for me. I’ve only recently started setting things up with them, and tonight ran through a Test payment.
The upload has just completed, so download it now!
There are numerous bug fixes in this release, alongside the major new feature of Recipe Sharing. Users can now create Chef Recipe Packages and give them to other Chef owners to place into their collection. Please feel free to check it out and let me know what you think.
As a continuation of my last post, I thought some of you .net developers may be interested in hearing about some of the issues I ran into when strong naming.
Admittedly, this is my first real attempt at using strong naming as it’s intended and therefore I just wasn’t aware of a few things when I was writing the code for Chef. Two days ago I created myself a strong name key (sn -k keyfile.snk) to sign my assemblies with. Due to the obfuscation step I need to do between compile and packaging, I need to delay sign the assemblies.
In an exercise in curiosity I decided to sign the assemblies with the public key half of my keypair and keep the private key “secret”. Which really means just not kept inline with the sourcecode, but rather living in a key container in the machine store on the build box. This process was mostly problem-free, I used the sn.exe utility to: create a keypair; import the keypair into a key container; extract a public key from the key container; tell .NET to allow me to run partially signed assemblies with that public key token (sn -Vr *,) for debugging purposes. It all went well until I went into visual studio and told it to use the public key for signing – it kept telling me that it was password protected and prompting me for the password. I never put a password on it.
So to get around that, I did the first step (creating the keypair) from Visual Studio and gave it a password, then it all worked just fine.
One feature in Chef is the ability to create bookmarks. In my ignorance, I was simply using the BinaryFormatter in .NET and serializing to disk an array of these things for loading later. Little did I realize that all of the version information for the objects is written out – and if the objects live in a strong named assembly and the assembly version changes, it cannot deserialize! There’s supposed to be a way you can get around this, by setting AssemblyFormat on the formatter to Simple but it continued to write the version information. I also tried the route of using a custom Binder during deserialization and that didn’t work either.
As a result, last night I rewrote that code to serialize/deserialize the information myself with XmlWriter and XPathDocument rather than rely on .NET. Version issues gone. That’ll definitely be something I’m not likely to forget anytime soon. I need to rewrite one other small area this weekend for a similar problem, then I can move on. All that’s standing between me and Beta 2 is some thorough testing, a website update, and a file upload. Should all happen this weekend.
Several hours today were spent advancing my automated build process for Chef. I’ve had CruiseControl.NET building the software for months now but I’ve had a gaping hole in the processes that has been staring at me since I started it.
What is this hole you ask? Version numbering.
Why is versioning so hard in this day and age? Seriously. With .NET there are all these really nice and easy attributes that all you have to do is type in the version string you want your assembly/binaries to have. That works really well, until you want those numbers to be dynamic – then it requires modifying a sourcecode file with a new hard coded string. But what about 1.0.*? you ask, referring to the ability to have the compiler generate parts of it for you. Well, what real good is it to have version numbers that you don’t control? If they get generated by the compiler it just makes everything difficult – like translating between a version label from CruiseControl to the state of source control at the time of the build. Maybe I’m missing something here, but I don’t think I am.
Another versioning issue is setup projects. The setup projects created in Visual Studio have a version number, product code, and upgrade code. Counter to intuition, the upgrade code is the same across versions for a given product and it’s the product code that changes between versions. Sooo, if you bump the version number you also need to create a new Product Code guid. Again, there’s no way (that I know of) to do this via command-line. Microsoft thinks you should open the setup project and bump the version number manually. They even go as far as prompting you to create the new Product Code guid when you do this. Microsoft, the creator of the great tool that is Visual Studio, make it very hard to do the Right Thing and have automated builds. Tisk, tisk.
And finally, the version string has implications on product keys – both generation and verification. For instance, if Suzie buys Chef 1.2, I need to have a way to have that license key work for 1.2.5, 1.4, and 1.9; but not 2.1. And I need to be able to forget about the details rather than think about it every single time I create a release. (Chef Beta 2 is days away, by the way).
My solution to these problems required a little planning, a little coding, and a lot of time waiting for test builds to be created. My process is as follows.
And that’s it. With a single click I have installation packages created with no further involvement. The files included in the package all have a version number that I can trace back to a CruiseControl label (to view build logs and in the future unit test results) and then back to a Perforce label with the same name to view the sourcecode files at were a part of the build. I’ll then also be able to compare those file versions with the recorded version numbers of bug fixes in FogBugz – something that will surely save time once Chef is in the wild.
Microsoft, please please please make this better in the future.
The development of Chef has been pretty interesting thus far. I had almost forgotten how much work is involved in getting an application shippable like this. My previous experience was with the release WakeUp! Alarm Clock, but that was as off-the-cuff as you can get: simple version control (umm, none at first then graduated to CVS); no bug tracking; no build process – builds were simply done on my development box; no unit test for regression testing (unit tests, what are those?!); and really no plan whatsoever. But I was in college and had no real experience in software, it was my first.
In these regards, Chef is completely different. I mean completely. My development environment is quite extensive in comparison to the days of old: Perforce for source control; FogBugz for bug tracking, support, forums and a bunch of other things; an automated build system driven by CruiseControl that give me a build and install at the click of a button; full NUnit test cases for the entire Chef API; and multiple VMWare environments for testing. Future posts may include some information on some of these topics, but for now a little information about FogBugz.
Chef Beta 2 isn’t quite as far along as I’d like it to be thanks to the Holidays and work. I’m targeting the middle of January for its release and that’s coming up fast. A couple dozen bug fixes and features/enhancements since Beta 1 have been done though, with the major ones out of the way.
One of these big features is Recipe Sharing, which I think will be a compelling reason to actually put recipes into the application. It’ll be very handy to just click the mouse a few times and be able to give recipes to fellow Chef users. And for sharing with non-Chef users, there’s always copy to clipboard.
So those of you interested should keep an eye out in the next few weeks for the final Beta release, with 1.0 hopefully coming in another month+ after that.
A while back I discussed needing to look into a new source control solution for Chef. To recap, CVS had just gotten on my nerves for a few things: file deletion and moving; pretty crappy windows client support (gui); clunky (to me) branch management; and poor infrastructure on my network. I just don’t feel comfortable using it on Chef going forward.
Some of my requirements for the replacement system: stable; reliable; simple backup/restores; good Windows GUI tools for management; inexpensive (read Free); intuitive; good documentation; preferrably a Windows server (to simplify my backups). The two forerunners were a coworker’s recommended, SourceGear Vault, and Perforce. Vault was built as a Visual Source Safe replacement and is free for a single user. Perforce, I learned, is a very popular and robust scm server that is free for 2 users or 5 workstations. After comparing the two for a while I settled on Perforce mostly because it met all of my requirements, and did so in a very elegant and polished fashion. Documentation has been spot-on and things work as advertised. I was able to import Chef, get it backed up and configure Visual Studio’s Source Control integration all in a span of a couple hours. Pretty impressive. Thank you Perforce for the free license.
Well it’s a week and two days later than desired, but it’s finally here. The first beta of the new Chef! For those of you that are going to be trying it out and providing your feedback, thank you very much – I really appreciate it.
Details available at www.ejichef.com.
Last night I put together a simple build system and got some of the application versioning in place for the future. I’m running CruiseControl.NET for the builds but haven’t set it up for continuous integration since I’m the only one coding. I’m also not running any build tasks other than a straight compile, although once I get some time that may change to include running my NUnit test cases.
All-in-all, I didn’t spend a lot of time on Chef this weekend, but I got a few very important things done.
In the very near future I need to really examine my source control system. I am using, and have been using, CVS at home for several years. But I haven’t really used it for more than a simple version controlled file repository – few branches, few labels, etc. At work I’m very comfortable with our source control system, but I’m just not with CVS. On my list of possible replacements are SubVersion and SourceGear Vault. All said, I’m still quite nervous about changing systems.
The Johnson Blog 