AutoExport2DotNet

SUMMARY

This package allows you to automatically export your Linq to Umbraco classes to a library folder ever time a doc type is updated.

In the current release of Umbraco v4.5, anybody wanting to use Linq to Umbraco will currently have to export their classes manually every time they update their doc types. This package allows the export to occur automatically to a preconfigured directory, every time the doc type is updated.

HOW TO USE

The package is configured via an autoExport2DotNet.config file located in the default umbraco config folder.

The standard output options are defined on the root autoExport2DotNet node.

mode - Defines the export mode. Can be either "poco" or "abs" where poco exports your poco classes, and abs exports your poco classes with abstractions.

datacontextname - Defines your data context name

namespace - Defines the namespace for your classes

None standard output options are defined on one or more output nodes nested within the autoExport2DotNet root node.

machinename - Defines the machine name the output should run on.

outputdir - Defines the output directory for the generated files

format - Defines the format of the output. Can be either "cs" or "dll" where cs outputs a set of .cs files, and dll outputs a single, compiled dll.

UPDATES

1.0.1 - Updated to work with 4.5.1 due to export doc types moving to the media folder

1.0.2 - Fixed issue with version check in 4.5.2 Beta

1.0.3 - Compiled against .NET 3.5

BUGS & ISSUES

Whilst there aren't any restrictions as to where you can set the outputdir attribute, it is advised that you do not point it to your bin or App_Code folders, as this will lead to your app pool constantly recycling, and may lock your application.

Please raise any issues on the forum below. All feedback is welcome and appreciated.