eWorld.UI - Matt Hawley

Update: I've successfully migrated to Community Server :: Forums 2.0. However, roles were not brought over successfully, so if you were apart of my beta testers, please let me know. I've also just sent out a mass email to everyone that had signed up (great interface for that, I must say), alerting you of the upgrade and beta testers issues.

I just found this totally cool feature in BlogJet that I think everyone will be like "woah". BTW, the reference "Me" refers to BlogJet, I don't actually have a mini-me like Dr. Evil running around (although how cool would that be).

So following up on my constant barrage of non-technical posts, I think this marks #3 for the day. I guess I'm starting to make an impact at Weblogs @ ASP.NET, or I've just been here way too darn long. Anyway, I've finally made it within the top 40 posters (I'm #39 as of post #5 this afternoon). Thats pretty impressive considering the blogroll is pretty lengthy.

I remember many moons ago people started bashing Scoble (or maybe it was himself) for posting too much in 1 day. I remember something along the lines of him being limited (by himself) to about 6 posts a day.

Following up on my most recent post, WebDeploy (soon to be rebranded) 1.2.2 is ready for public consumption and use. This is mostly a bug fix version like its predecessor, however there is one glaring addition that will make all VS.NET Project Deployers extremely happy, more on that in a bit.

With WebDeploy 1.2.2 rolling around the corner, its time that I take a step back and say that its been one hell of a ride. However, with 1.2.2, and previous versions, its become blatantly obvious that the name "WebDeploy" just doesn't justify the tools' versatility. I've also found out (well, not recently) that Wise actually has a product called WebDeploy. Obviously, I wouldn't want to cause a stir with them and get sued over the name.

This is just a heads up for those developers creating applications in which your app can minimize to the systray.

Yesterday, I stated that I had to prepare a presentation for my .NET User Group, and after 3.5 hours of quickly throwing together a presentation and demos, I was done. Yay! I luckily only had enough time to leave work (yes late), drive to the Microsoft office, setup my laptop, and then go! Call that close? I would.