December 2007 - Posts
I'm thinking of hosting a blog myself. Most important reason would be that bloggingabout.net doesn't allow some stuff like scripts, embedding flash and links to things like the 'connect with me' button and so on. Which is completely understandable by the way. What I'm not sure about is which software to use. Do you guys have any tips on which blogging software to use? Or maybe even on if I should or shouldn't host it for myself? If you do, let me know.
Technorati tags:
blog,
software,
blogging
A Dutch web site, made in SharePoint, uses a specific ActiveX.
Only the name of that control is not really specific:
The MSDN forums haven't been available the last couple of hours.
The message isn't so pretty:
Technorati tags:
error,
funny
Next to the message in the subject, one of the symptoms we encountered is that although the solution contains some test projects the 'Create private accessor' menu has disappeared. Also, selecting 'Create unit tests...' produces an error. And when editing a testrun config and selecting the 'Code coverage' option, the settings dialog simply closes, without any message.
All these (and probably more) symptoms can occur because of a corrupt solution file. In our case the nested projects section was corrupted. Chances are this is because of some project or solution folder not being removed the way it should have been. Anyway, I tried fixing the solution file by hand but because of too many projects and solution folders this wasn't the way to go. Those GUIDs don't make a file very readable... I made a new solution file, containing the same solution folder structure, and added the existing projects. I overwrote the existing solution file, and that was that. So when you're experiencing any or all of the above symptoms, try building up a new solution file.
Hope this helps.
A [wikipedia:RUP] project consists of 4 different phases. The elaboration phase (the second phase in the RUP project lifecycle) is normally done with a small team. One of the important reasons for this is that you want to define the basic form of your architecture. This means you think about concepts, elaborate on them, develop proof of concepts and select the ones that work best for your specific project.
If there is one thing you can not use (early) in an elaboration phase of a project, it's having too many team members. There's probably not enough work to go round. Because of that the members who do not or can not contribute to defining the architecture or developing the proof of concepts will eventually end up being assigned production (or construction) tasks.
That's where things go wrong: in an elaboration phase the architecture is designed and takes its basic form, but in construction the architecture should be stable and proven. In elaboration you define the standards and guidelines, while construction needs those things to be available. Tasks in elaboration take some time because they have to 'grow'. Because of this they are harder to plan, while tasks in construction have a hard deadline. And as one of the 'elaborators', it's pretty darn annoying when one of the 'constructors' comes up to your desk every two hours to ask if the part they are waiting on is ready. That kinda kills the whole goal of the elaboration phase...