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 ...Hooking up VS 2008 to an existing instalation.Hooking up VS 2008 to an existing instalation.
Previous
 
Next
New Post
12/30/2009 4:52 PM
 

So I now have a fully operational 5.02 instalation at http://localhost/

Anyone know the procedure for hooking that up to VS 2008.  (I find plenty of references for doing a new setup, but not for doing it at root on an existing installation.)

I'm hoping it's as simple as adding the root website into the project, but I suspect there is more to it then that.

 
New Post
12/31/2009 6:32 AM
 

if you want to create your custom modules with VS, simply create a subfolder in desktopmodules and create from scratch or template.

make sure having a 2nd installation at hand lateron for testing proper installation of the module package.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/31/2009 1:30 PM
 

I originally developed the site under the full install with source.  Although for maintenance/upgrade/security reasons I have no intention of altering the source, I like the ability to step into the source and see what's going on.  The current full install package is missing part of the modules folder so I'm going to hold off on that for now.  Setting that back up looks like it might take a bit of work. 

I'm primarily a desktop developer so my familiarity with the web stuff is limited.  But I can get the site to open and load correctly by opening it from the Local IIS store in VS.  But, it won't compile, looks like the numerous upgrades have left some legacy code behind that I will need to remove.  Installing a starterkit site under the root also creates some problems.  For some reason VS tries to parse the config from the root website.  IIS also adds some printer folders that VS chokes on when loading.  I have to step through a ton of errors every time I open the solution.  I can remove them, but IIS recreates them.

Looks like any way I go on this I'm in for a bit of work.  Your solution will probably work the best for now.  I may just scrap the root site and do a fresh install of a 5.0 site in a subdirectory.  I'm thinking that might just be the easiest way to go.  Thanks for your feedback.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Hooking up VS 2008 to an existing instalation.Hooking up VS 2008 to an existing instalation.


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