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 StartedNew to DNN Plat...New to DNN Plat...Beginner DNN questionsBeginner DNN questions
Previous
 
Next
New Post
3/18/2010 2:55 PM
 

Hi all,

I was assigned a project to upgrade my company's web-based advertising-creation program ("AdMan") from VB 2003 to 2008. It uses DNN; I don't know what version, but the dates on the dll's are in June of 2004. After looking through the folders and code and trying to upgrade for a couple of days, I have some basic questions just to get me pointed in the right direction, and would appreciate any help that anybody can give.

I copied the "AdMan" folder from our network to my PC's C drive. The AdMan subfolders & files and the DNN folders & files are all mixed together in this AdMan folder (!). (There's also a subfolder called DotNetNuke, but this just seems to be a copy of all DNN stuff in the main folder except "CDI.Show.DataProvider".)

1) Is there any real reason to have your home-grown project and DNN all in one folder?

2) Is it even necessary to have the DNN source if you're going to use it "out of the box", or shouldn't we just be able to put the dll in /bin and add a reference to it?

3) OK, here's a longer and multi-part question. Intro: The AdMan folder contains AdMan.sln like you'd expect, and also DotNetNuke.sln since the DNN code is in the same folder. When I open these solutions, they have some projects in common (probably because AdMan wants to use some DNN functionality), in particular "http://localhost/XXXAdMan/DotNetNuke.vbproj" (where "XXX" is the company's initials). When I converted the DNN solution from 2003 to 2008, I got warnings for several projects:  MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please remove the reference to project http://localhost/XXXAdMan/DotNetNuke.vbproj and add it again.

 

What does it even mean to have a project in localhost? I did see on one forum posting here that DNN will not be a "web application project" but instead a VS "web site", but... well, I'm not sure what to ask.

I thought I'd try doing what the warning message said. For the first project listed, I right-clicked, selected Project Dependencies, and got a list of checkboxes for things that the project "Depends on:" I tried to unclick the one indicated, but got a message "This dependency was added by the project system and cannot be removed".

So in Solution Explorer, under the project's "My Project" node, I clicked on the "References" tab on the left, and by the reference "DotNetNuke", the path is "The system cannot find the reference specified".

And when I convert the other (AdMan) solution, its "Imports DotNetNuke" lines fail, and I get hundreds of errors about references to DNN classes not being found.

So... could someone give an explanation of what this localhost thing is all about, how I'd get DNN installed into localhost/XXXAdMan, how I'd re-add a reference to that if I *can* get it deleted, or even if I'm on the right track at all?

Thanks very much in advance!

 

 
New Post
3/19/2010 6:30 AM
 
1) best practice would be physically placing your custom application outside, using a virtual folder to include it into your DNN web site 2) you don't need the library folder with core framwork source code to run a DNN web site. If your site is from 2004, it might be a DNN 2 or 3, which didn't support the separation of website and framwork code. Check /providers/dataproviders/sqldataprovider folder for .sqldataprovider files, the highest number usually states the version currently installed. 3) Try to get the site running locally first. next analyse, what has been added by the custom solution and consider converting it to DNN 4 or DNN5 modules. remove the application (without deleting data( and upgrade to DNN 4.9.5 or latest DNN 5 (5.2.3 atm). install your modules and complete the site.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Beginner DNN questionsBeginner DNN questions


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