About the author
Boaz I'm a software developer, working at a small company in the Netherlands. Currently I'm mostly using techniques like .NET, C#, SQL and jQuery, but I have experience with JAVA and PHP as well.

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

FireDotNet is now available as an official NuGet package on nuget.org:

FireDotNet is a library I created to show ASP.NET server-side log messages in the Firebug console on the client-side. A few months ago I updated the library to a NLog target so all NLog messages are send to Firebug.

I used this opportunity to make some changes too. First of all I automated the builds using TeamCity. I installed a NuGet plugin for TeamCity so dependencies are automatically resolved. This means that I no longer need to have the NLog.dll files under version control. Besides managing dependencies it can also automatically make a NuGet package and publish it to both my private NuGet server and the official NuGet server.

Another nice feature of TeamCity is that it can manage version numbers for you. There is a build feature named AssemblyInfo patcher and - as the name already implies - it modifies the version number of your AssemblyInfo.cs files. So from now on all FireDotNet builds will have a version number that consists of:
MajorVersion.MinorVersion.BuildNumber.SvnRevisionNumber eg.
Where I control the first two numbers and the last two are automatically set by TeamCity.

Last but not least I managed to add a new feature too! From now on FireDotNot by default only outputs to requests form localhost. This means that you, when deploying your project, no longer have to think of removing FireDotNet from it. Except of course if you changed the allowRemote property.

December 11, 2011 - Comments [0] - Posted in ASP.NET | FireDotNet | NLog | NuGet