Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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 ExtensionsModulesModulesGetting StartedGetting Started
Previous
 
Next
New Post
4/26/2011 10:22 PM
 
Here is my environment: Windows 7, Visual Studio 2010 Professional.



So far I have installed DNN on my local computer and the development toolkit as described in the video by Chris Hammond. I am able to build my first blank local module as the video shows as well.





Here is where I am now. I want to look through the code of an existing module to get familiar with how things work. I also have some ideas on modifing the event module. So, I downloaded the event module 5.1.5 source code module. I installed it on my local DNN and I can see the files.



Here is the problem: When I try to open the project in Visual Studio, first it wants me to connect to a team foundation server - I don't have source control. I am a one man shop. When I exit that dialog it upgrades the module. I can then see the subproject (the scheduler) but the main project is listed as unavailable.



I can open the files in notepad, but they are not available to VS2010. I have also tried this now with other modules and have the same problem. Obviously the problem is on my end, but where?



Any ideas? I would hate to have to install some source control modules just to look at the files.















 
New Post
4/26/2011 11:44 PM
 
Usually, but not always as in this case, source control bindings are removed from the VS solution file prior to creating the source package. They can be easily removed by editing the VS solution file (DotNetNuke.Events.sln) in NotePad or other text editor prior to opening the solution in VS.

Remove this entire section and re-save the file:

GlobalSection(TeamFoundationVersionControl) = preSolution
  SccNumberOfProjects = 2

  . . . . . . . . . . . . . . . . . . . . .

  SccProvider1 = {4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}
 EndGlobalSection

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
 
New Post
4/27/2011 10:38 PM
 
Thanks, I tried that and I still get the project unavailable. It now says

"Unable to read the project file 'DotNetNuke.Events.vbproj" but I did not edit that file, just the solution file as you suggested.
 
New Post
4/28/2011 9:23 AM
 
The DotNetNuke.Events.vbproj file imports an MSBuild targets file, "Install\Project.targets" which requires that MSBuild Community Tasks be installed. This allows the project, when built in release configuration, to update the DNN manifest and package itself into source and install versions. If you have not installed MSBuild Community Tasks or if it's assembly is not located in the default MSBuildExtensionsPath (C:\ProgramFiles\MSBuild\MSBuildCommunityTasks for 32 bit installations or or C:\ProgramFiles(x86)\MSBuild\MSBuildCommunityTasks for 64bit installations) the project filee cannot be loaded. If you do not want to take advantage of this custom build environment, you could comment out or delete the following line from DotNetNuke.Events.vbproj:

<Import Project="$(MSBuildProjectDirectory)\Installation\Project.targets" />

I also noticed additional source control binding information in the DotNetNuke.Events.vbproj file. Although I don't believe these will cause the project not to be loaded, you might as well remove them

<SccProjectName>SAK</SccProjectName>
<SccLocalPath>SAK</SccLocalPath>
<SccAuxPath>SAK</SccAuxPath>
<SccProvider>SAK</SccProvider>

They are located in the first <PropertyGroup> section.

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
 
New Post
4/28/2011 11:06 AM
 
OK. Here is what I found.



In the errors I found buried an error that C:\Program Files (x86)\MSBuild\MSBuilddnntctasks\dnntc.msbuild.tasks.targets cannot be found.



So I went into the folder and found that when I installed the MSbuild tool it installed the file as dnntc.msbuild.task.targets Notice the missing S. So I created a copy of the file and renamed it to include the s in the file name and wow just like magic I can open the files and read them!



Woo Hoo!



Thanks for the help.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesGetting StartedGetting Started


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out