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 ...Problem with accessing Source Install FilesProblem with accessing Source Install Files
Previous
 
Next
New Post
6/7/2006 1:01 PM
 

I reciently downloaded the newest DNN3.2.2 Source version and am attempting to access it via Visual Studio 2003 on my Windows XP Pro SP2 box. It looks like everything is configured correctly. I am not a newbee to DNN and  have configured and deployed several older versions and run into very few problems. This problem has me stumpted and I am hoping someone may have some insight.

When attempting to open the project if VS2003 I get a message stating "The project location is not fully trusted by .NET runtime." I followed the insturction from Microsoft Help to fix the problem, however the message still persists. It seems to be thinking it is in a virtual directory. The message is appearing every time VS attempts to open any of the resources assocated to my base DotNetNuke.vbproj. I have opened, compiled, and run several other of my other web projects and thery aren't experiencing the problem. I have tried opening up my folder permissions, IIS permssions, everything I can think of. All the websites tested, including my DNN project, are in the inetpub/wwwroot default website space. Does anyone have any idea what might be going on??? Any help would be greatly appreciated.

 
New Post
12/18/2006 12:18 PM
 

I'm curious if you found a solution to this problem.  I'm experiencing the same issue.

thanks,

yogs

 
New Post
1/29/2007 5:46 PM
 

Unfortunatelly no. It did not seem to affect anything, other than annoy me every time I opened the project. I could not spend any more time tracking down a solution. Also, we just upgraded our development environment to VS2005, so I am now moving in that direction. Seems to be fixed in v.4.4.0 with VS2005.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem with accessing Source Install FilesProblem with accessing Source Install Files


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