ASP.NET and FP 2002

[Frank]

MS KB Article 817029 applies to FP 2003 and FP2002 w SP3 -- and is the
answer to my DBR problem by recreating some pages in ASP.NET. BUT..

Is ASP.NET in FP2002 w/SP3? (I cannot find it)

 

[Kevin Spencer]

See my reply to your same question in your previous thread.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

 

[Kevin Spencer]

Also, see Thomas Rowe's reply to the same question in the previous thread.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

 

[Frank]

for some reason I am not seeing all the thread responses.
Time to go to the store for XP Pro and FP2003.

Thanks

 

[Frank]

for some reason I am not seeing all the thread responses.
Time to go to the store for XP Pro and FP2003.

Thanks

 

[Kevin Spencer]

FP 2003 is what you need, Frank!

Or, just use ASP with FrontPage with an earlier version and use the 2nd
workaround from the KB article.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

 

[Cowboy (Gregory A. Beamer) - MVP]

Frank:

I would bite the bullet and upgrade. While FrontPage 2003 is not perfect, it
does at least render .NET controls and give intellisense on the tag portion
of the app (UI, not code). There are other reasons to move up, as well.

FP 2002 is "friendlier" with ASP.NET, but still has fewer features, even
with the SP applied. Prior to that, it was not as "friendly", but it still
will not work the same way as FP2003.

The other option is Dreamweaver, which has its own pluses and minuses. If
you are using FrontPage extensions to upkeep your web, however, I would not
venture the DW route unless you have an iron constitution.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[Frank Smith]

FP2002 SP3
Option 2 workaround....
when I get down to step 7 there is no "Code" button just the normal HTML
button

Step 11 has no "Design" button to force the update so the code reverts back
to the DBR settings.

 

[Kathleen Anderson [MVP - FrontPage]]

Inline.

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/

FP2002 SP3
Option 2 workaround....
when I get down to step 7 there is no "Code" button just the normal HTML
button

"Code" is for FP2003; "HTML" is for FP2002

Step 11 has no "Design" button to force the update so the code reverts
back
to the DBR settings.

What happens if you save your changes while you are still in HTML view?

 

[Frank Smith]

any thought about Netobjects Fusion?

Frank:

I would bite the bullet and upgrade. While FrontPage 2003 is not perfect, it
does at least render .NET controls and give intellisense on the tag portion
of the app (UI, not code). There are other reasons to move up, as well.

FP 2002 is "friendlier" with ASP.NET, but still has fewer features, even
with the SP applied. Prior to that, it was not as "friendly", but it still
will not work the same way as FP2003.

The other option is Dreamweaver, which has its own pluses and minuses. If
you are using FrontPage extensions to upkeep your web, however, I would not
venture the DW route unless you have an iron constitution.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[Kathleen Anderson [MVP - FrontPage]]

Frank:
I agree with Cowboy - bite the bullet and upgrade to FrontPage 2003. Many of
the issues with the DBRW are fixed by applying Office 2003 Service Pack 2:
http://support.microsoft.com/kb/906341

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/

 

[Frank Smith]

When "spiderwoman" and "Cowboy" speak..... that is the definitive answer....
off to the store for XP Pro and 2003..... and a bleeding checkbook
There is a point of "I am tired of messing with this"

Of course, I still wonder why these pages worked for YEARS without any
problems.
Did the host guys maybe do an update that triggered my problem?

Oh well, press on, just love computers,
Frank