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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN home page but no modules load...DNN home page but no modules load...
Previous
 
Next
New Post
11/14/2006 11:00 PM
 

I've had numerous problems. I tried installing the Starter kit but kept getting a 'Can't connect to database' error. I wrote a small program, used my 'copy and pasted' connection string from the web.config and had no trouble pulling data from the database. Before that I couldn't get the database scripts to run in SQL Server 2005, but if I took the default install and let it install into SQL Express, it worked. Then I changed the connection string to SQL Server 2005, ran it and the database was now created in SQL Server 2005. But I still had trouble trying to start a Visual Studio project in Visual Studio 2005, so I abandoned that and got the Source version of DNN.

When I opened the website from the Source version everything seemed to work ok, originally. But then I noticed that in the directory above the website there was a Library folder and a solution file (.sln). So I thought, thats where I should really be opening Visual Studio from. So I then opened the solution file and was able to build it. But when I tried to run it I got an error saying that debugging couldn't occur because Windows Authentication had not been enabled. So eventually I was able to get the home page for DNN to come up but none of the modules or content loaded. It was a couple of blue bars and empty image placeholders.

One odd thing I also noticed in the Source version is that the website url comes up as 'DotNetNuke_2'. I didn't have another copy of it on my computer (XP Pro) so I thought that could be a problem. And when I tried to go directly to it with http://localhost/DotNetNuke_2 it immediately redirected me to localhost/DotNetNuke. I looked in the PortalAlias table and saw only DotNetNuke and nothing with _2 so I deleted the database, deleted my Source installation, deleted the virtual directory in IIS, created a directory with a different name, created the DotNetNuke database again, added my db_owner user, unzipped the Source again, and the install created a DotNetNuke_2 virtual directory again on IIS, and when I ran it I got the  'Can't connect to database' error again (haunting memories from the Starter Kit install). The issue now is that the database didn't get populated again.

Any suggestions would be appreciated. But if there are none, does anyone know if I really need to open the solution file and include the Library folder in my project if I just want to create my own application from DNN? Can I just open the website under the DotNetNuke folder and be ok? I don't really like not having access to all the code for a project but I don't know the purpose of that Library folder and my Pro DNN 4 book doesn't seem to say anything about it.

Thanks,

Tom

 
New Post
11/16/2006 4:36 AM
 

I think there are a few posts dealing with dnn source installations and visual studio. The best way to find them is to add something like "source install visual studio" and add to the google DotNetNuke phrase "+ForumsDotNetNuke site:dotnetnuke.com". If you put them together in the google search box you can find almost anything in this forum.

If you had found one I think one of the first things on the list to install a source version using visual studio is to open the solution file (.sln) in a text editor and modify the 2 instances of DotNetNuke_2 to reflect the name of your virtual directory - say(DotNetNuke or DotNetNuke4). Here is the first sentence from my solution file -

# Visual Studio 2005
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "http://localhost/DotNetNuke/", "http://localhost/DotNetNuke", "{79D3BA0F-F76F-4A84-AE7F-C6A01EC247F9}"

Instead of:

# Visual Studio 2005
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "http://localhost/DotNetNuke_2/", http://localhost/DotNetNuke_2, "{79D3BA0F-F76F-4A84-AE7F-C6A01EC247F9}"

Another thing you have to remember is to point your virtual directory to the "Website" directory and not to the DotNetNuke install directory.  You don't have to fool with the library directory as that will take care of itself.

I hope things go well for you - Good Luck.

Mike


Kist Enterprises
www.kistenterprises.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN home page but no modules load...DNN home page but no modules load...


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