Marko Lahma's Blog

Quartz.NET is now CLSCompliant!

2009-09-11T08:17:00.001+03:00

Quartz.NET trunk was updated with Common.Logging 2.0 which was made CLSCompliant and now it was also possible to make Quartz.NET obey the requirements of Common Language System compliance with a few tweaks to the source code.

At the same time I also dropped support for VS2003 and VS2005 solutions. Using VS2008 for now allows targeting .NET 2.0 and source code finally gets the sweet language features of C# 3…

Maybe next little issue to dabble with could be to make Quartz.NET run under medium trust…

Getting Started With Quartz.NET – Part 2

2009-09-03T14:03:00.000+03:00

In the previous post we did a short evaluation whether Quartz.NET would be a viable choice for a project. In this post we’ll go through the steps to get Quartz.NET up and running.

Getting the distribution

You will find the latest download information on Quartz.NET’s download page. Just follow the links and choose the latest binary distribution. In your case that is Quartz.NET 1.0.1. After you have have download the zip file you should extract it to some location so we can explore the distribution a bit further.

What’s inside the package

Quartz.NET is distributed ready to run and source included the package does not contain documentation at the moment as the latest API documentation and the tutorial are available on the project’s website.

The bin folder

This folder contains the actual binaries that you will need to use Quartz.NET in your application. There are separate subfolders for 1.1, 2.0 and 3.5 respectively.

The database folder

This folder contains the create scripts for Quartz.NET database. There’s a script for each supported database.

The lib folder

This folder contains the external dependencies of Quartz.NET. Quartz.NET requires Nullables library for the 1.1 build to get nullable-like features and the Common.Logging framework for all builds. The folder contents are needed when building from the source.

The server folder

This folder contains the Quartz.NET sample Windows Service. It acts as a sample how to build a windows service for running of jobs and it can be used as-is if ne customizations are required. This server will be discussed in future blog posts.

The src folder

This folder contains the source the Quartz.NET.

You can also find the the solution files,license, readme and change log information in the root of the distribution.

Now that we have had a quick tour around he distribution we should be ready to create our first little sample application in part 3 of our series.

Getting Started With Quartz.NET – Part 1

2009-08-30T14:02:00.001+03:00

This is the first blog post on the series of posts about getting familiar with Quartz.NET. In this blog posts we dig in to the requirements and common things we might want to decide before proceeding.

Evaluating whether Quartz.NET is the thing for you

First of all, it’s always a good thing to evaluate whether the tool is suitable for one’s needs. It goes without saying that like any other tool, Quartz.NET is no silver bullet (but a good golden hammer I hear). The easiest way to nail it is to quote the project’s home page:

Quartz.NET is a full-featured, open source job scheduling system that can be used from smallest apps to large scale enterprise systems

Well big words but I believe that Quartz.NET can live up to it. Quartz.NET was ported from the famous Java Quartz and so If you’re familiar with the Java one, you should have no trouble grasping the concepts of Quartz.NET. Quartz.NET is distributed with same license as Java version, Apache 2.0, which in short gives plenty of breathing room including hassle-free commercial usage.

Quartz.NET is for you if…

You need a flexible scheduling framework written in pure .NET
You need failover or clustering support for job scheduling/execution
You want the best bang for the buck, it’s free as in beer

Quartz.NET might not be for you if…

You have a “no open source” policy ;)
You are trying to handle workflows or batch processing (well you can bend it but it’s just not a natural fit)
You prefer Visual Studio wizards and shrink-wrapped products – Quartz.NET will have it’s learning curve like any other framework

If you decided yes (a good call) we can proceed!

Quartz.NET requirements

Quartz.NET 1.0 is written in C# and targets framework 1.1 and above (you probably would get it to run with framework 1.0 quite effortlessly). So the requirements in a nutshell:

.NET Framework 1.1 or above, builds supplied for 1.1, 2.0 and 3.5 separately
Database if fail-safe persistence required, supported databases include MS SQL Server, Oracle, MySQL, PostgreSQL, SQLite and Firebird

As you can see, Quartz.NET is quite self-contained and requires little from you application. If you got interested with the framework then the next post is for you as were going to get started with Quartz.NET!

Start Your Engines

2009-01-18T16:31:00.001+02:00

This is the famous first post! I'm starting to blog about mostly technology related things (.NET in particular), probably with special focus on my pet project, Quartz.NET.