In regards to the EPrayer module source installation, this error stems from my use of a special build environment which allows me to locate the compiled module project and its associated files outside of a particular instance of DNN. Each time I build the project in Debug mode, a custom targets file deploys the various module controls, EPrayer assembly, script files, css files, etc. to a particular instance of DNN for testing and debugging. Then when I finally build the project in Release mode, it creates the module's install and source packages. I should remove a project's import of a custom BuildConfiguration.targets file when releasing the source version on CodePlex but that would be a time-consuming process requiring a manual modification to the source package. Also note that that EPrayer is a VS 2012 not 2013 project, although I don't think that should be a problem.

To convert the project for normal development inside of a DNN instance, please . . .

1. In the VS 2013 Solution Explorer, right click the project "WESNet.DNN.Modules.EPrayer" and select "Unload Project" from the context menu.
2. Again in Solution Explorer, right click the project and select "Edit WESNet.DNN.Modules.EPrayer.csproj"
3. At line 410 (just prior to the <ProjectExtensions> node, remove the line:
   
   <Import Project="$(MSBuildProjectDirectory)\_buildfiles\BuildConfiguration.targets" />
4. Resave the edited WESNet.DNN.Modules.EPrayer.csproj file.
5. Right click the project "WESNet.DNN.Modules.EPrayer" and select "Reload Project".
6. It is also likely that you will have to modify the project's references to DNN assemblies to point to those in the websites /bin folder rather than to my custom environment's References\xx.xx.xx folder (outside of DNN) where I keep assemblies for any current or previous DNN version which a particular project may reference.
7. As with any source web project you will also need to configure its VS 2013 Web properties web server, project url, and application root override url.

As an alternative to the above changes, it would also be possible to modify the _buildfiles\BuildConfiguration.targets file to point to your environment's location of the MSBuild.Community.Tasks.targets file. I would also need to provide you with the DeployModule.targets and CreateModulePackages.targets files which are not currently included in the source package.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner