Sitecore tools, I’ve got tons of them. Written because of I need them for projects, maintenance or sometimes just for fun or exploring the API. Last Friday I found out a colleague and I have maintaint the Sitecore items very poorly. Result: all of the items where exclusively checked out to: sitecore/admin. And as a lazy programmer, I’ve decided to create a small tool which can check in item recursively based on username.
When you leave the User-field blank, all items which are locked will be unlocked.
No support for this tool of course and usage is at your own risk, but I’ve tested it and worked fine for me(220.127.116.11+). Should also work on 5.1, but you’ve to migrate from partial classes to just one class.
Planning to create a Sitecore 5.3 IDE Tool like the XPath tool when I’ve got some spare time.
It’s actually quite on my blog isn’t it? Altough Hans did post a real quality post, all my latest post are still under embargo. Still working on the HTML-profiles stuff and actually rewriting my 5.3 posts. Later today I’ll inform you guys what happends on Search Engine level and explain a little bit more about the way I test Sitecore distributions.
But for now I want to point you guys on 2 blogs. First of all, Scott Guthrie spoke to the world, last night. He wrote this entry about Visual Studio 2005 SP1:
This release contains several hundred fixes for customer reported bugs with VS 2005. It also includes built-in support for the VS 2005 Web Application Project, which we previously released earlier this year as a standalone download (SP1 adds a few additional features to it, fixes a few bug, and has some additional performance tunings for it). Before installing VS 2005 SP1 (both the Beta and final release), you’ll need to uninstall any previous installs of the VS 2005 Web Application Project standalone download that you have on your machine.
When you want to help MS and you can take the risk, you can register on MS Connect and download it and supply some feedback if you like to.
The second post I want you guys to pay some attention to, is from the MVP Bart de Smet. Altough he’s from Belgium(yes we always make jokes about them in Holland), he’s one of my quality sources for staying up-to-date in the changing C# 2.0/C# 3.0 world. Last saturday he showed me that namespaces are more manageble then I tought…
This is a commonly applied technique to abbreviate namespaces, for example in VSTO:
using Outlook = Microsoft.Office.Interop.Outlook;
using Word = Microsoft.Office.Interop.Word;
This can actually solve the problem in our LECTRIC-Library with duplicate Sitecore namespaces. Keep you guys informed.
Today it was Sitecore day in Zaltbommel. An Admin-training was delivert by Kim, one of the teachers of Sitecore. And Mr Vice-President, Torben Brams, was kicking asses @ our Salesteam: showing the (new) world of Sitecore. And ofcourse had a little tiny chat with him. The chat with Kim was more a long conversation during the day, as I helped him a bit out with the training-pc’s. Hope to do it over again with both with a little more time,
One thing Torben pointed on was the new MondoSearch integration. For more details, compared to Lucene, take a look at this matrix. But I’m not interested in Lucene. I’m not saying it’s bad, I’m just saying that I’m not interested. Lucene does its works for the core and master database, but it isn’t an engine for a website. Therefor, both MondoSearch and dtSearch deliver terrific products. Well, I suppose when Torben is that enthousiastic, it should be damn good.
Actually, I’m a dtSearch fanatic. Both Hans and I got excited on this product after a quite succesfull custom implementation at one of our customers. We’ve written a highly advanced custom Indexer and Querier(isn’t a word, is it ;)?). dtSearch has a Sitecore-like API. You can talk to dtSearch from Com(+), Java, .NET. Documentation is available at several resources, it does include usefull developer tools, etc. Lots of reasons to stay enthousiastic… But now Torben came up with the new product and I’ve to review it ofcourse :P. So I’ve decided to create a test. Testing will be done on the following criteria:
- Implementation time: Installing and time to have the first results on my screen.
- Preformence: Both querying, advanced querying(incl fuzzy search) and usage of impossible search criteria(try to create endless parsetrees)
- Indexing: I’m quite interested in the possibilities and time of indexing on larger sites. I’ve decide to index my blog, www.lectric.nl and www.slashdot.com with the maximum of 4 levels.
- Extra features: Stuff like cool admin panels.
- Extensibility: How does the API work? Do a get a clue how to integrate other datasources? I’ve got 9 sites in my installation, you’ve got a solution? Etc.
First step tomorrow is to get a MondoSearch module. Hope to do the testing the upcoming weekend. Suggestions are welcome. Till that time, I do not support MundoSearch(yes this one is for you, Bart, Anton, Robin, Frank & Sjoerd).