Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesMore development issues, MSBuild.Community.Tasks.targets" was not foundMore development issues, MSBuild.Community.Tasks.targets" was not found
New Post
3/31/2014 8:35 PM

C:\Users\Keith Stone.CREWSTONE\Documents\My Web Sites\DNN720\DesktopModules\WESNet_EPrayer\WESNet.DNN.Modules.EPrayer.csproj : error  : The imported project "C:\DNN5 Development\_buildlibraries\MSBuild.Community.Tasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.  C:\Users\Keith Stone.CREWSTONE\Documents\My Web Sites\DNN720\DesktopModules\WESNet_EPrayer\_buildfiles\BuildConfiguration.targets

Something that should be simple, just opening a project to look at it, is also becoming really annoying. I'm referred to example projects; Simplearticle, EPrayer, etc. I download the source and guess what, VS2013 pukes on opening them with some variant of the error above. I have the MSBuild tasks loaded, use them in templates, etc, but they are really looking like a royal pain in the ass. If using them means your project is corrupted and will only work with one file system what's the point? There's got to be a better way to get around these errors that make it impossible to open the whole project.

New Post
4/1/2014 9:31 AM

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
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesMore development issues, MSBuild.Community.Tasks.targets" was not foundMore development issues, MSBuild.Community.Tasks.targets" was not found

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?