I don’t really consider myself a fan-boy for any single platform, OS or Manufacturer. I have an IPhone which I think is a great day-to-day tool and I have been toying with the idea of an IPad for a while now. On the other hand I’ve been a Microsoft .NET Developer for >8 years now, (saying that made me feel just a bit old…), I use a PC, know v. little about Mac’s and like most things MS. (.NET Dev, Xbox, Win7, etc…).
There was fantastic stream of thought on Twitter last week about UX & UI Design; all started thanks to this tweet by @kellabyte, a Canadian developer with an uncanny knack for stirring up the masses and making them think.
What followed was a torrent of ideas on how to improve user experience, user interfaces & user interaction in terms of both the software & the hardware we use on a daily basis. Apparently Crowdsourcing + Brainstorming = Crowdstorming and a lot of credit for this post goes to following twitter folk: @robertmclaws, @cromwellryan, @uliwitness, @Montagist, @DavidQMora, @BenPittoors, @kellabyte and Others. There was a lot covered over the course of the chat, (here as a CSV file for posterity) but a few key things rang true with me so… stream of consciousness follows.
I was trying to get my Development Environment up & running the other day with Silverlight 4. It turns out that the Silverlight debug runtime isn’t actually part of the standard client, or the Silverlight 4 Tools for Visual Studio.
The “Silverlight managed debugging package” is part of the developer runtime, not the SDK or Tools. Make sure you have the latest version of the developer runtime installed (available at http://go.microsoft.com/fwlink/?LinkID=188039
On the plus side I did throw together this nice pretty clock just to test everything out.
There’s probably a dozen ways to break this, but it covers the basic for autosizing the grid, limiting the dimensiosn with min height & max height sections, drawing lines & drawing ellipses & a small bit of math.
We had a situation in work where we needed to make service installation a more configurable process.
So a very simple example, In order to install a .NET Windows Service we need to provide it with a username & password that the services will run as. We can either provide that information at installation time, or through the following properties in the ProjectInstaller.cs file for your service.
However in an environment where multiple developers are working on a service, particularly a service that requires elevated privileges and needs to run as a specific account, this can be a royal pain.
ASP.NET MVC 3 Beta & Enhancements to the Razor View Engine was announced by Scott Gutherie last week.