I am a newbie programmer, using lots of books and online resources. I
need help to get my asp.net page to work because right now all I am
getting is errors.
The project is to have a drop down list select names from a Access
table, then display a gridview grid and a Detailsview Grid based on the
selection chosen. Sounds pretty easy huh. At home I got the project
made and working using MS Visual Web Developer 2005. The thing that
bugged me is that I would only see my page if that program was running.
I would prefer to call it anytime, like most normal web sites.
I started the project from home had it working then wanted to transport
it to work to finish it.
Home: XP, asp.net using VB programming, dotnet 2.0 frame, Access 2003,
MS Visual Web Developer Express 2005.
After I made the default.aspx file using MS Visual Web Developer (and
get the code syntax correct), I press F5 and my beautiful screen with
my datagrid controls work perfectly.
Work: SharePoint Services w/ WMSDE (or known as SQL Lite), dotnet 1.1
and 2.0, Server 2003, IIS 6, Front Page 2003, Access 2003. All latest
SPs and updates.
I copied all the files into a directory. Using IIS, I made a web site,
gave it a port number like 30000, allow anonymous access. When I type
in \\WSS:30000, I get the following error information:
Server Application Unavailable
The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web
browser to retry your request.
SO I decided to have a look inside of FrontPage 2003 to see my aspx
file, and (in design view) all my controls DropDownList, Gridview and
DetailsView say the same error notification:
There was an error rendering the control.
RegisterForEventValidation can only be called during Render();.
I did see a bunch of web sites talking about adding the following code
to disable event validation:
<%@ Page EnableEventValidation="false" % to my document or a similar
statement in web.config to set all documents to skip event validation
and make the grids work again.
The problem is that this didnt improve the situation.
--------------------------------------------
I do not believe that this is as much of a coding problem as it is a
dotnet or IIS setup problem.
I do not understand why I would have to have MS Visual Web Designer
running just so I can see my website work properly.
I do recognize that I may be doing something wrong in the setup
somewhere, may knowledge of "Why do I have to do all of this" is not
there yet.
It is likely that running another ASP application concurrent with
SharePoint is a bad idea (On this end I am going to set up another
Database server so I can keep working)
-------------------------------------------
If anyone has an idea what I can do, please tell me. I am at a loss.
Thanks,
Harvnet
