Frontpage control

  • Thread starter Thread starter Erik J Sawyer
  • Start date Start date
E

Erik J Sawyer

Problem:
I take a working HTML page, containing a Frontpage Hit
Counter control, and rename it from .htm to .aspx. No
other changes are made to the file.

The hit counter now either doesn't display, or never
increments (stuck at "1").

Any thoughts?

Erik J Sawyer
Webmaster
Kingsport City Schools
 
aspx is an entirely different mechanism.. I don't believe you could run FP
controls on an aspx page - besides, ASP.NET needs to be compiled if you have
any script behind it.. this is sort of all or nothing - you run FP scripts
in an html file - or you do everything in ASP.NET
 
Sorry. The counter needs to be ruyn through the FrontPage server extensions.
ASP.Net pages are processed by a different ISAPI.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Neither a follower nor a lender be.
 
I understand that code-behinds need to be compiled, but
you can put code snippets in the HTML (similar to classic
ASP) and it can compile JIT.

- Erik
 
No, the counter runs through a CGI-style program
(specifically, _vti_bin/fpcount.exe). That link remains
intact, and should still work.

FYI, the page works fine if the extension is ASP. If it
was a matter of ISAPI engines, this would break it as
well.

- Erik
 
No, the runat="server" attribute tells the ASP.Net ISAPI
engine to process the control before it's sent to the
client. In this case, the counter is a CGI-style
program. The link must be processed by the client into a
sub-request (much as a graphic would be), and the counter
program returns the graphical counter display back.

- Erik
 
It just really seems you are barking up the wrong tree here. What's the
signifigance of changing the filename to .aspx? In the time it would take to
troubleshoot some wacky Frontpage macro problem - you could write an ASP.NET
counter.

Why are you trying to convert half of the app to aspx?
 
It's not a matter of converting "half the app". This is
a website that I have inherited from a predecessor, which
is 99% static content. I am "dipping my toe" into adding
some ASP.Net content to a page, but don't want to
overhaul the page just yet. Eventually, the page will
certainly be rewritten, and the counter will become
a .Net control, but I wasn't aiming at "fixing" something
that's "not broke"--at least not yet.

- Erik
 
Back
Top