I recently changed the layout of some of my categories in BlogEngine.Net 1.4.5.0.  In short I wanted to add a few parent Categories for the categories that I was already using.  For example: I have a category name ".net" that I lump all of my .net related items in but what if I also have some java code or C++ code and I have a category for them as well?  To me it makes sense to have a parent category called "development" and then if I want to view all code or development related items including C#, VB, Java, HTML, C/C++ then all I have to do is click on the new parent category and voila you have everything development related no matter what the sub-category is.

So for the bug:
When the Category List control/widget is rendered it looks at the Category.FullTitle to build the URI. This works fine if you are not a sub-category, like ".net" using the example above, but when rendering the URI for these sub-categories its using the FullTitle which is a concatenation of the parents categories and the title of the sub-category: ie: "development - .net".  This does not work and that link should really just be to the ".net" category. So here is the simple code fix that I used, but take in mind that you could also make it so that "development - .net" works.  I just found a quick and easy fix...

Code fix after the break.
More...

This morning I was creating a branch in Team Foundation Server via VSTS, the branch name that I wanted to use was one that has been used before and is in fact still sitting around but is now old and out of date. So it being so out of date I just decided to delete the branch and then recreate if from the main branch of code.  After deleting the branch, I went to create the new branch and I get the message "TS14082: Can not lock item $/projectName/../filename.ext for merging. This item is checkout to another workspace".

 

At this point I have already deleted and committed the changed to the branch of code that I'm trying to recreate.  So being able to see what or even find who has files checked out was not an option, I was for the most part out of luck, well at least using the default tools that come in VSTS.  So I fired up the trusty Team Foundation SideKicks application and opened the Status Sidekick. This application allows you to search and view who has files checked out and what each of those files are (great tool, go get it). This tool allows you to filter based on username or even project name and then shows a nice tree view of all the files that are checked out and who has them checked out.



After gathering the details above I contacted each of the offending people who had items checked out in the old, now deleted branch, and asked them to "undo changes" to each of the files that were locked.  After all the files are no longer checked out or locked in any way, it allowed me to go ahead and recreate the branch using the same name.

What if you cant get a hold of those people or they cant undo the changes?
Lucky for you that the Team Foundation Sidekicks - Status Sidekick also supports undoing others pending changes. It accomplishes this by using the following command from the commandline:

tf undo $/path/to/file.txt /workspace:<WSname>;<domain\user>

Well i'm just getting into blogging and i thought that i would take a quick eval of all the different .Net blog packages.  I'm not sure why but for some reason i have ended up on BlogEngine.Net.  I have installed and looked that the following packages; Community Server, DasBlog, Subtext and BlogEngine.   To tell the truth i think that i like Community Server the best out of all of them, but i'm not sure that i want to install the 9000 features that come with it.  I do like the design and size of the BlogEngine but it leaves a few features that can NOT be stored in the db and that is a big negative, but will prob be fixed in up coming versions.   

With all of this said i'm going to be giving BlogEngine a try and perhaps i will write some code to get all features in the db myself.  we shall see if i stick with it or move over to one of the other blog packages.