Visual Studio 2008/Vista X64/WAP project issue
- From: Chaitanya <Chaitanya@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 8 Jan 2009 11:41:01 -0800
I am hoping that someone can help me out with this issue that I am having.
Visual Studio 2008 is generating a warning that does not allow any of the
ASCX or ASPX pages to be generated via the designer.
The projects that I am working on right now are WAP projects. And I have
the project directory different from the web site directory where I am
actually doing the testing. Inside the WAP project, I have a script that
copies all of the pertinant files from the project directory to the site that
I am doing the testing and debugging in. In VS 2005, this did not present
an issue and I had no problems with getting this working. However, in VS
2008, the below error is generated on the @Page attribute of the ASCX file.
"asp.net runtime error: could not find a part of the path
'z:\inetpub\dotnetnuke\'"
(Note: Z is a partition on my hard drive that I do all of my programming out
of. It is valid and is not a removable drive.)
And when I try to open one of the ASCX files in the designer is just shows a
blank screen. In addition, adding things to the markup doesn't regenerate
the designer.cs file for the control.
I have "Use Local IIS Web Server" selected with the project URL being
virtual directory for the project and the "override application root URL"
check with the url showing as "http://localhost/dotnetnuke/".
I don't have a web.config in my WAP project because the controls that I am
building are running in the Dotnetnuke directory and the web.config file used
in that directory has all of the settings.
Switching from "Use Local IIS Web Server" to "Use Custom Web Server" seems
to work, but if I try to debug it forces me to put a web.config into the
project directory, which is kind of irritating.
I have tried adjust the permissions on the directory (Everyone now has FULL
control). I have tried adjusting the settings in IIS. No luck. I am
currently at a loss as to what is causing this issue. If it comes down to
it, I have a way to get it working, but would like to fix what seems to be a
permissions issue with IIS.
Any suggestions?
Chaitanya
.
- Prev by Date: Re: Edit.GoToDeclaration vs. Edit.GoToDefinition
- Next by Date: Re: Edit.GoToDeclaration vs. Edit.GoToDefinition
- Previous by thread: Edit.GoToDeclaration vs. Edit.GoToDefinition
- Next by thread: VS2005 mobile device deployer installing pre-existing dependencies
- Index(es):
Relevant Pages
|