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.0Custom DNN ModuleCustom DNN Module
Previous
 
Next
New Post
1/8/2009 12:50 AM
 

Please please please.  If someone has a fix for this please let me know.   I am at my wits end with trying to figure this out.   I can't use the designer in VS2008 cause of this.   Any help at all would be appreciated.

No matter what changes I make to the project or IIS, this problem will NOT go away.      I can't be the only one that is running into issues with this.   

Again, I have my DNN virtual directory setup and running under Z:\InetPub\DotNetNuke.   Launching it by itself works just fine.

My project directory is Z:\Programming\xxxxxx\

In the web tab for my project, I am have "Use Local IIS Web Server" selected with a project directory set to a valid IIS Virtual directory.  I also have "Override Application root url" checked with the DNN virtual directory selected "http://localhost/dotnetnuke/"

So matter what changes I make to this, I can't get it working in VS 2008.   Designer doesn't work and no designer file gets generated when I make changes.   If someone has ANY idea, I would REALLY appreciate it.

Chaitanya

 
New Post
6/12/2009 11:57 PM
 

Hi Chaitanya,

I hope you resolved this already.  But if you didn't or if someone else is looking for the answer, I found the (an?) answer for my instance of this problem.

1) make sure that you have a virual directory for the root of your DNN site set up.
2) make sure that in your module directory, there is no web.config file
3) Make sure that the Project URL points to your module, in my case it's "http://localhost/PageConfirmDnn/DesktopModules/PageConfirm".  Where "http://localhost/PageConfirmDnn" is the virtual directory set up above.
4) make sure that the Override root URL is set to the virtual directory set above "http://localhost/PageConfirmDnn"  (this was my problem, I had a typo in the name, I looked at it about 19K times before I saw it!).  One note on this, I do not have I trailing / on my paths, I don't know if that makes a difference.
5) make sure that the directory is accessable by IIS (eg: check the permissions)
6) exit and reload VS2008 (this one tripped me up too).  it seems just chaning the properties is not enough, you need to get VS to reload them!

Regards!

Jeff

 
New Post
6/15/2009 4:45 AM
 

I used to get a lot of these errors whenever I needed to read some files from the server using Server.MapPath() method and using localhost virtual directory. This was because when running in localhost the website is actually a diretory in website(http://localhost). So I needed to add(/[Virtual directory name]) to solve this issue.

Hope this helps someone.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom DNN ModuleCustom DNN Module


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