Microsoft has these “virtual labs” where you are supposed to be able to get hands on with some of their products w/o all the pain of downloading and installing them.
Right now I can’t the site to respond, but I am guessing it is a temp problem, not that they have removed this service.
Some of the labs they have are:
Thanks to Somasegar for the links.
Scott Hanselman has a little post about how to setup paging in DasBlog.
This is something I will implement when I upgrade to DasBlog 2.0, but I won’t be doing that until they get off of asp.net 1.1 and onto 2.0.
They were supposed to be releasing a 2.0 version a few weeks ago, but hopefully it will be out soon.
Haacked blogs about the 19 laws of programming.
My favorite, and one that I personally know to be very true, is Brooks law:
Adding manpower to a late software project makes it later.
Which can also be stated as:
The bearing of a child takes nine months, no matter how many women are assigned.
I have all but given up on Code Checkin Policy in TFS.
For me, running the policy checker against one of my solutions takes about 30 minutes.
That is unacceptable.
But, there is still some hope of running the static analysis on the back end, so I am still looking around at the goings on in this area.
A new Code Comment Checking Policy has been released, which would be really nice way to force the people to comment their code.
When I saw a new item in my RSS feed from Rob Conery about MV* I was immediately interested to read it, because I have been working on trying to create my web app pages using MVP, but am unable to find any examples beyond the most basic.
I would love to see how other people manage the interactions between the Controller and the View, to see how it compares to how I am doing it.
My view interfaces tend to be kinda large. For example, if I have a button that I hide and show depending on business rules, I will create a MyButtonVisibility property on the interface can set the properties from the controller.
I would be interested to see how others deal with things like the hiding / showing of items. I could see wrapping more of that kind of functionality in the view, and giving the view some more logic but I think you would then start to lose some of the testability.
Anyway, the articl on Rob’s blog was really to talk about creating an MVC style architecture for subsonic itself, not the pages that use it. However, Rob seemed to suggest that the new changes would aid you in using MV* in your pages by forcing you into good habits.
But I really don’t understand how that would work. If you have code that does:
And you change it so that you use a Controller (or Manager as I have called it when loading Business Objects or DTOs) to look like this:
Product product = ProductController.Get(newID); product.ReorderLevel = 100; ProductController.Save(product,"unit test");
I don’t see how this helps you create an MV* architecture in your pages.
Maybe I am just not understanding.
The “flag for later” feature in Outlook is really nice, but the down side of it is that you can easily put stuff off for later, and end up with a task list like this:
These red items are ones that are overdue.
I guess I need to put an entry in my task list to go through my task list.