When developping an application often/always there is a need for logging. Security events, audit events etc. need to be logged as well as significant transactions.
Asp.NET makes this very easy for you. To configure your application
A complete overview of how to configure the health monitoring service can be found here
I’ll just show here what I’ve put in my config file for NBlogr
What I did before configuring my web.config was to install the asp.net services in my sql database by running the aspnet_regsql tool and installing all the asp.net services. Health monitoring in my case consists of monitoring the server and logging most of the events to the sql database and if a critical error occurs I’d want to know about it so it also sends me an email at that point.
And then I put the following configuration in my web.config which I’ll clarify below.
<healthMonitoring enabled=“true“>
<bufferModes>
<clear/>
Base4 has joined NBlogr on Codeplex
Alex James just informed me that base4 relocated to codeplex
That is good news they live closer together now.
History and back button support for ATLAS
The conceptual internet
There has been some talk lately on how to define web 2.0
In my opinion web 2.0 is something you add to the description of your application or service and have instantaneously a perceived coolness upgrade.
Everything is else is just the web. I’m up to the point that if I hear somebody mention web 2.0 to me I’ll run out the door screaming 
But let’s talk a bit more about conceptual url’s as Alex has called them. I feel they should be more self-describing urls. Alex and I have been discussing this way of forming url’s for a wee while now.
Self describing urls are urls that mean something to everybody also your mum and nana. When talking to users I often find that they don’t get anything that comes after http://www.somedomain.com/FooBar
However if it were common to implement a scheme like http://www.somedomain.com/MyAccount, http://www.somedomain.com/Blog
That is something they also grasp but what they don’t get (want to or need to) is why there is sometimes .aspx, .php, ….. and definitely the question mark is where the look in their eyes becomes fully glazed.
So a common schema to implement could be protocol://domain/DomainObject/View/RowIDOrFilter/Action/DomainObject/View/RowIdOrFilter/Action…. Now why do i feel that they should be called self describing. The reason is because you can read them in plain english :
At domain Get me the domainObject as a view with only RowIdOrFilter and do Action with it/make it Action/apply Action to it
http://www.nblogr.com/Category/DetailByName/Venues/ShowSublist/Entry/List/ would be valid and would say then at nblogr.com get me the categories By name Venues and from those show me a sublist of entries as a list. Now that is something my grandfather with alzheimer still understands and quite possible could navigate.
That way url’s are in fact really easy to remember if you make them all up of meaningful words so that would make internet more transparent for everybody to use.
This theory poses a problem when there are complex filters to be applied. However filters can be foreseen and hence be named upfront. And the biggest problem I see here is to come to a world wide consensus on which naming to use for commonly used filters ect. But in fact with predefined standards really everybody would benefit from it.
In asp.net with virtual path providers you can store your whole website in sql server and never have a real physical website running
Needless to say that I can’t wait for IIS 7 to get rid of the aspx extensions etc on my projects.
I’d say back to the basic idea of the computer/internet is here to assist people into doing better jobs not to confuse the hell out of them.
Flight centre doesn’t do what it promises
http://ims.co.nz/blog/archive/2006/09/08/2001.aspx
holds the whole story. Go and check it out because you might be next.
Preview release of NBlogr
Today I put a preview release of NBlogr online.
I still have to change the online site but will do so very shortly.
This release has very basic functionality and is not yet feature complete so a lot may change later on.
If anybody feels like joining the project do not hesitate 
All help I get is extremely welcome.
http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=Nblogr
I’m heading into a very busy week/couple of weeks so I’m not sure if I will be able to spend as much time as I’ve been spending lately on the project. But I think every week I will be able to show some progress at least.
If you feel like it go ahead and give it a try but don’t upgrade your blog just yet .
I’d be keen to know what your thoughts are on the subject.
FileUploading for NBlogr
To upload files in nblogr. I wanted the user to have the possibility to upload as many files as they wanted but only show one file element.
The upload procedure has to work without reloading the page entirely but there is no way of getting the size or the bytes of a file through the html input file control from clientscript without popping up a security warning.
And what do I personally think about security warnings : they are a necessary evil but limit you a lot in the development of contemporary sites with rich client interaction.
If I am to present a site to my parents and they have to figure stuff out themselves I’m pretty sure that once the read the words : Security warning, Potential risk etc… they will click no ==> site doesn’t work ==> site == crap
I wanted to include an upload with progress bar but decided to let that idea go and just give an implementation of a multiple file upload with a single inputelement. Maybe I will put this in during the next iteration. That way I can probably release a ctp this weekend and start thinking about a plugin architecture (thanks for the idea JD)
Because of the file issues i have to run it in an iframe :-s and have the page and the frame talk to eachother.