asp.net pages

[Guest]

Hi: I have a site that will have a few asp.net pages to access my Access database. The problem is, I can't seem to get them to work on my test platform( IIS and .net on the same computer as the frontpage site I am developing). It seems from reading, that the problem may be due to my IIS version. Microsoft says it should be IIS 6.0 and I have IIS 5.0. Is the only way to really develop this page is to publish the site to a hosting company with IIS6.0?? The page (asp.net) that I developed with Frontpage to access the database shows fine in preview, but when looked at in a browser, none of the database tables show up, nor the input field for the query. I tried a "hello world" asp.net page tested in Asp.net web matrix and it doesn't work either.

Is there any article or book that clearly states how to configure the IIS, .net etc. and test it to be sure all is working right together?

Thanks for any direction on these questions - I can't wait to get past the tool set up and into getting some work done.

 

[Jim Buyens]

IIS 5.0 ought to be OK. You installed the .NET Framework
on the same box, right? And you saved your file with a
filename extension of .aspx?

Also, I have a self-diagnosis page tht may help. You can
download it from:

http://www.interlacken.com/winnt/dnld/

Just click ASP.NET Self-Diagnosis Web Page. You'll have to
self-register.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

-----Original Message-----
Hi: I have a site that will have a few asp.net pages to

access my Access database. The problem is, I can't seem to
get them to work on my test platform( IIS and .net on the
same computer as the frontpage site I am developing). It
seems from reading, that the problem may be due to my IIS
version. Microsoft says it should be IIS 6.0 and I have
IIS 5.0. Is the only way to really develop this page is to
publish the site to a hosting company with IIS6.0?? The
page (asp.net) that I developed with Frontpage to access
the database shows fine in preview, but when looked at in
a browser, none of the database tables show up, nor the
input field for the query. I tried a "hello world" asp.net
page tested in Asp.net web matrix and it doesn't work
either.

Is there any article or book that clearly states how to

configure the IIS, .net etc. and test it to be sure all is
working right together?

Thanks for any direction on these questions - I can't

wait to get past the tool set up and into getting some
work done.

 

[Kevin Spencer]

Can you describe what you mean by "doesn't work?" Imagine what a car
mechanic would say if you told him that your car "doesn't work."

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Hi: I have a site that will have a few asp.net pages to access my Access

database. The problem is, I can't seem to get them to work on my test
platform( IIS and .net on the same computer as the frontpage site I am
developing). It seems from reading, that the problem may be due to my IIS
version. Microsoft says it should be IIS 6.0 and I have IIS 5.0. Is the
only way to really develop this page is to publish the site to a hosting
company with IIS6.0?? The page (asp.net) that I developed with Frontpage to
access the database shows fine in preview, but when looked at in a browser,
none of the database tables show up, nor the input field for the query. I
tried a "hello world" asp.net page tested in Asp.net web matrix and it
doesn't work either.

Is there any article or book that clearly states how to configure the IIS,

..net etc. and test it to be sure all is working right together?

Thanks for any direction on these questions - I can't wait to get past the

tool set up and into getting some work done.

 

[Jim Buyens]

http:/members.cox.net is a Unix server running Apache/1.3.26. The .NET
framework won't be available.

If you want to run ASP.NET pages, you need to find a hosting service
that provides Windows Web servers. To start looking, try the site
listed at the end of this article:

What to Ask a Prospective Hosting Service
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=9

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

Jim: Thanks for the response -I am using your book - very complete and informative. I have tried your self-diag page that came with the book - to no avail. When I try to browse it, it pops up as only code in Visual Studio (or something that looks like it) and there is no option from there to a browser view - or even debugging.

I did install .net framework on the same box and saved the file as

..aspx. I don't know if this matters, but I did not create a virtual
directory as discussed in your book- but I think I accomplished such
differently. I set up the web site and then published it to a
directory on my root (I gave frontpage the directory name I wanted and
it actually asked if I wanted the new directory created). I assume
that this then creates the virtural directory. I then open the
"remote" site in frontpage and try to view the aspx file by clicking
the internet browse icon. I also tried just opening directly from the
browser.