Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Cannot view any aspx page without the .aspx.cs present
Message
From
03/11/2003 14:51:32
Jerry Tovar
Dana Corporation Dana It
Maumee, Ohio, United States
 
General information
Forum:
ASP.NET
Category:
Other
Miscellaneous
Thread ID:
00841560
Message ID:
00845756
Views:
26
Cathi,

First of all, thanks for the reply.

Secondly, here is my progress on this issue.

I have performed an uninstall of .Net 2003 and then installed it again. But my Parser Error problems still exists.

But I have narrowed my problem down to some sort of security issues with the /BIN directory.

For example, if I create a new ASP.Net project in .Net and place a label on the Webform, then Build the project and attempt to view the webform1.aspx, I get Parser errors.

For a test, I then placed a "Hello World" Static .HTM web page into the /BIN directory of this project. I then tried to view this .HTM in a browser but could not. The browser returned an error: "The page cannot be displayed"

So I looked at the settings for this /BIN directory in IIS and found that the READ checkbox was unchecked and the execute permission = NONE. I then checked the READ and set permission = Scripts & Executables. My Static .HTM page then worked but my .ASPX still displayed Parser Errors. Also, if I re-built my project and attempted to view my .ASPX webform, the READ checkbox would uncheck again and the permission would = NONE again.

The weird thing is that even if I create a new virtual directory and a /BIN folder inside this directory, then copy my .ASPX, web.config and myproject.DLL to the appropiate spots, I still get parser errors when I attempt to view this webform in a browser.

What can I check on my system to get my webforms to work?

A few weeks ago I was able to build webforms and view them in a browser using ASP.Net. Now I can't view any .ASPX webforms that I create.

Any ideas would be appreciated.

Thanks,

Jerry




>Hi Jerry,
>
>I've been at PDC so I haven't been able to get back to you on this. It definitely sounds like you need to reinstall VS.NET. Something became corrupted on your machine that is causing VS.NET to get confused.
>
>>Cathi,
>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform