23. May 2007 10:17 by Admin in General  //  Tags:   //   Comments (0)

Everyday I have a loft of stuff to write about on my Blog, but as you can see, it doesn’t always happen. Now it is time to do get back on track!
As a member of the team of open source project and its first release just out the door, now it's time to tell my story.

Some time ago I wrote about .Net slave Blog and its good stuff. After that, Mads contacted me about my post just to share a couple of gentle words.

Then I found out that Mads wants to create a new Blog engine with some really cool features in mind, specially:

  • Written entirely in C# and ASP.NET 2.0
  • Small in size and source files
  • Plug 'n play implementation (just copy to web server)
  • No third-party assemblies
  • Using ASP.NET themes and skins
  • Easy to extend using plug-ins
  • Many more…

Thinking about developing a new Blog engine these days is a risky thing to consider. When you already have a bunch of well done and well tested solutions, along with good development teams, starting from scratch is a thing that should be considered over and over again.

How did I get involve and why?

I got hooked up immediately after reading the simple specs I mentioned above. Then I checked the first bits of BlogEngine and liked the approach so fast that I immediately started wondering to myself about getting involved. I contacted Mads and got hooked. I also want to mention here that when Mads told me about moving the project to Codeplex and use team server Explorer, believe me, I was super skeptical. To my surprise, I can now tell that using both Codeplex and Team Foundation Explorer has been a really great experience.

Why use BlogEngine.Net?

Because, after trying many other Blog engines out there - developed with ASP.NET of course – you can easily find some problems. Or maybe not exactly problems but different implementation methods for different situations, in a way that is so complicated you end up disliking the engines because of the lack of SIMPLICITY. I tried some engines like .Text, Subtext, DasBlog, Community Server and others. Those platforms are really good, but maybe in a context where you don’t have to extend, because when you think about extensibility or customization, you can get into a non ending trouble, especially when you want to do something simple and end up learning a framework/platform that, in some cases, you have to debug through hundreds of classes just to get used to the code and understand how things work. For some people like me that like full control, even when you did not write the software, this is just not an option. No matter if I’m on the team or not, I will use BlogEngine.Net because it has all the ingredients an ASP.NET web developer loves when dealing with a Blog engine: easy to setup, easy to extend and easy to understand.

Now celebrate the first release

Today, I want to join Mads making the first official release of BlogEngine.Net. Go visit the BlogEngine.Net website and have a look at project and why not, setup your next Blog with it. Congratulations to all the Team for the first release. Cheers!

Debugging XSL

8. November 2006 05:23 by Admin in General  //  Tags:   //   Comments (0)

Developing XSL can be sometimes cumbersome and tricky. Especially if it is something you don’t do every day.

Luckily Visual Studio 2005 now provides the an XSL debugger.

To debug an XSL open Visual Studio and open a Project go to the File Menu \ Select New File and Create a New XSLT file.

Write your XSL file.

You can set breakpoints just by clicking on the left side of the editor just like you do for VB.Net of C#.

Now to test it right click on the editor and select properties:

In the properties for the XSL type a name on the

The XML menu provides two options:

The Show XSLT output will run the complete XSL and let the XSL Output in a new window. The output by default is not formatted. You can go to the Edit\Advanded\FormatDocument option to format it.

The Debug XSLT option will start the debugger and stop in the breakpoints you specified.

Press F10 or F11 to dig into the file. You can use the call stack windows and even the vales for variables in the Quick Watch and Watch Windows.

You can write XPAth Expression in the Quick Watch Dialog.

There are three special values that are handy when debugging:

last() is the context size, position() is the position, or index number, of the context node, relative to the context size; and self::node() is the value of the context node.

And enjoy your debugging experience ;)

Demo Photo

5. October 2006 10:44 by Admin in General  //  Tags:   //   Comments (0)
The description of the picture

Sunrise Over Zebras

11. October 2005 10:11 by Admin in General  //  Tags:   //   Comments (0)
A picture from my backyard!