Frequently Asked Questions

Q1. Will support for the .net 2.0 framework be added?

A. There is currently no plan to support .net 2.0. We have limited resource and feel that our effort is best spent on targeting the .net 3.5 framework. If you require a specific task, changing the sourcecode to compile against .net 2.0 should not be too difficult.

Q2. Why is IIS6 not supported?

A. We have had a lot of feedback on this and IIS6 support has been added with the 3.5.1.0 release.

Q3. How often will releases be made available?

A. We are currently working on a release cycle of 8 to 10 weeks, though we plan to provide a ‘rollup’ release mid-cycle. The rollup releases will contain any bug fixes that we have made and any new functionality that we feel is stable enough to ship.

Q4. How is the pack versioned?

A. The 3.5 library will always have a major version of 3 and a minor version of 5. With each release cycle we increment the build number by one, so major releases will be 3.5.0.0, 3.5.1.0, 3.5.2.0 etc.

We will increment the revision number for Rollup releases or any other release made between the standard releases, e.g. 3.5.0.1, 3.5.1.1, 3.5.1.2.

Q5. What guarantee is there that backwards compatibility will be maintained in future releases?

A. We aim to maintain backwards compatibility; however on rare occasions a change may be made that breaks this compatibility. We will publicise any breaks (that we know of!) so that you may plan your adoption. Remember, the full sourcecode is available, so if a new release causes you any issues, you can easily revert selected parts of the change.

Q6. Which branch has the latest code?

A. There are several branches under source control. All the release branches are branched off our Main branch. The 3.5.0.0 branch contains the original 3.5.0.0 release. The 3.5.1.0 branch has all the new functionality we ship with 3.5.1.0 and will be the branch where we make any fixes / enhancements for the lifetime of the release. If you would like to work with the code, it is recommended that you work with the branch for the current release at the time. We will merge any fixes and enhancements to the newer development release branches on a regular schedule.

Q7. I submitted a task, why is it not in the release?

A. Firstly, thanks for the code! If you have not heard back from us, please drop us a reminder email. Several submissions have been marked for inclusion in the next release.