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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Starterkit not visibleStarterkit not visible
Previous
 
Next
New Post
1/29/2007 6:31 AM
 
I am having serious problems getting started with DNN. I have DNN installed fine and can use the standard modules etc.However, when I try to install the starterkits for module development I am failing completely.

When I try to create the website from within Visual Studio or Web developer I do not see the DotNetNuke framework starter kit.  I have made sure I am looking for a Visual Basic project etc. I have done the proper installation, I have checked to see if the zip files are in the correct directory, etc.  If I install other starter kits, like the personal web site from Microsoft, they appear in the same directory as DNN, but they show up whereas DNN does not. I have tried reinstalling, getting the packages from a different mirror, going back to prior versions of the release kits. I’ve checked that I can open the zip files, that there are no permission problems.

I am out of ideas, anyone got an idea what I am doing silly?

 
New Post
1/29/2007 9:58 AM
 
You're saying "I have made sure I am looking for a Visual Basic project..."
Have you looked under 'New Web Site'?  Cause you won't find it under 'New Project'.
 
New Post
1/29/2007 11:16 AM
 

Yes, I am looking in the right place. That I know because I have the same installation on my server and it shows up there. I can't use that machine for development any longer. All Visual Studio products will have to come off it very soon.

Something to do with the installation of Visual Studio and Web developer (I can't get either of them to find it) is not right, but for the life of me, I have no idea what it might be. The only difference I can thinkof is that I have applied VS SP1 to the workstation, but not the server (and not going to either, see above).

 
New Post
1/30/2007 7:27 AM
 

More information.

I am seeing two entries in the event log:

1) One or more Visual Studio templates do not match any installed project packages.

2)One or more Visual Studio templates is invalid and will not be displayed. If I change the options to point the directory to theVisual Web Developer subdirectory of Project Templates then DotNetNuke shows up, but it creates another copy of the directory Visual Web Developer at that location.

 

If, after I revert the options back to the correct one, I copy the DocNetNuke.zip to the ProjectTemplates directory it shows up and I get no errors in the event log.

Anyone with bright ideas?

 
New Post
1/31/2007 9:36 PM
 

I tried this for the first time tonight and found the same problem.  After a few frustrating hours of troubleshooting, I found that the .vstemplate file isn't configured correctly.  The ProjectType element needs to be set to 'VisualBasic'.  I changed the DotNetNuke.vstemplate inside the DotNetNuke.zip file to the following and it fixed my problem.

<VSTemplate Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vstemplate/2005" Type="Project">
  <TemplateData>
    <Name>DotNetNuke Web Application Framework</Name>
    <Description>This template creates a DotNetNuke Web Application</Description>
    <ProjectType>VisualBasic</ProjectType>
    <ProjectSubType></ProjectSubType>
    <SortOrder>11</SortOrder>
    <CreateNewFolder>true</CreateNewFolder>
    <DefaultName>DotNetNuke Website</DefaultName>
    <ProvideDefaultName>true</ProvideDefaultName>
    <PromptForSaveOnCreation>true</PromptForSaveOnCreation>
    <EnableEditOfLocationField>true</EnableEditOfLocationField>
    <EnableLocationBrowseButton>true</EnableLocationBrowseButton>
    <LocationField>Hidden</LocationField>
    <Icon>DotNetNuke.ico</Icon>
  </TemplateData>....

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Starterkit not visibleStarterkit not visible


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