31 May 2006
16 Aug 2011
Link to this post
Thanks for your email, unfortunately the Empty Project doesn't do the trick, as I am sure you know, it only has the assemblies to run a project not to compile a project that contains persistent classes. We have as many as 10 - 20 projects on the go that could be using any different version of OpenAccess, so we use the MSBuild method recommended by Telerik to compile our projects so that they can use different OpenAccess versions, including our Sitefinity Custom Modules. The Wmpty project doesn't contain the venhance.exe or enchancer.exe files required to compile in this manner.
I appreciate that the SDK is now out which now contains the files we require, but I would like to express a concern that the SDK hasn't always been as prompt as this time so if that is to happen again does this mean that Sitefinity Partners that are creating custom modules must wait longer or could the Empty project also create the required files?