December 2005 - Posts
It appears that the censorship loving folks finally have pissed off a co-blogger on our site. I find this annoying. Ian has been an active member of our little community for a few years now and it annoys me to think that people out there feel the need to tell him to keep his posts on topic and to watch his language.
I reserve the right to post what I please on my blog. I never signed any sort of censorship or content agreement.
I have been known to mix personal and professional posts all of the time, with a few profanities. I do this because, quite simply put, I’m lazy and I don’t want to maintain a professional and a personal blog.
If you have subscribed to my blog or anyone else’s then you must put up with the good, the bad, and the ugly; otherwise unsubscribe.
My comments to Ian and others that have dropped off or cut back because of these censorship pigs, Fuck’em! Come back and don’t change a thing. If they can’t handle what you have to say then they can simply unsubscribe.
As you probably have heard there is a new release of Atlas (MSFT's answer to Ajax). After reading through some of the content and a few blog posts I found myself almost ready to drive down to MSFT Campus and buy a beer for the entire Atlas team!
Take a look at what Richard posted to the Atlas Blog. Under "Changed", you see "1. atlas: server UI controls removed". That right there made me almost shout with joy. Every since I first laid eyes on any sort of Atlas bits (and was able to blog about it) I bitched about having a completely new set of controls, just for Atlas enabled features. I even went so far as to corner Shanku and Scott about the issue during the MVP/AspInsider summits, and really expressed my concerns about it. Looks like my efforts have paid off! Read a post by Nikhil about a possible (IMHO nice) solution using ExtenderControls to add the Ajax functionality to the exist controls.
I would give my left ____ to work here.
I need some feedback from people using the CCTray (CruiseControl Tray App) to monitor their applications and have X10 integration. Anyone want to test out my new build of the CCTray with X10 support, including the UI for settings? I want to gather feedback before I actually submit it to Owen and Mike for CVS. It is built with the current "CruiseControl.NET-1.0.source".
Download it here
Here is a screenshot of the Automation Tab in the Settings UI:
I have not yet fully tested the CM17A (firecracker) interface; but I know the code works just haven't been able to test it in this environment. I have a new one on order and it should be here anytime now.
Features:
- Turn on or off X10 support all together
- Choose the COM Port
- Choose the X10 Device CM11A or CM17A
- Testing inline
- Ability to chain together a collection of X10 actions to:
Successful, Fixed, Broken and Still Failing events
- Turn on or off the Time based Exclusions
- Exclude on Weekends
- Exclude by specific time of day
- Exclude based on Sunrise/Sunset for your given longitude/latitude
(default long/lat are for Vancouver BC, Canada)
Let me know your thoughts.
So I have been attempting to install VS.NET 2005 on a new build of my primary machine for the past week or so. Every single time I tried, in and out of VPC with the DVD ISO's and CD-ROM ISO's and with/without burning each to disk it failed with the error 1335. Pretty damn annoying if you ask me.
Last night I felt pretty tolerant so I re-downloaded the DVD ISO from MSDN for the 3rd time, and after the hash checked out I decided to move the ISO to another (SATA, slightly faster) drive. It worked! Woot!. It actually worked. I have no idea what actually caused it to work, the new drive, a new ISO from MSFT or what but I actually have VS.NET 2005 installed on my machine.
Right now, it appears to be working in the VPC session as well.
So if your having the same issue, try moving the ISO onto another drive and re-attempt the install. You just never know.
I've been doing allot of work recently with CruiseControl.NET and noticed that a few in the community have bridge the gap between CCNET and X10. Essentially controlling lights or devices based on your build status. I decided to build this right into the CCTRAY application itself.
As you can see above you can control all aspects of your X10 setup with CCNET. Devices supported are both CM11A and CM17A (Firecracker). I have tested it on CM11A and have yet to test it on the CM17A but I dont see any issues with it.
I followed the same requirements as the original CCTRAY, which means only .NET Framework V1.1, which means I had to use the SerialPort workspace stuff from GotDotNet and not the native provider in V2.
I have a few more things to add before I publish anything. If you can think of anything to add to it, let me know!
More Posts