Re: Coming Expression replacement for FrontPage

Tech-Archive recommends: Fix windows errors by optimizing your registry

I want to do my design work, development and deployment with the KISS
principle: Simple tools, solid reliable results. I dont want to have
anything to do with this finicky, obscure, geeky, techy stuff. They can
keep it.

<coreybryant@xxxxxxxxx> wrote in message
news:1160836751.472443.101180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
In my opinion, Microsoft was trying to re-do the HTML compliant coding.
They could not do it and now Expressions creates coding that is much
more, if not all, compliant.

You can choose what DOCTYPE you want etc. I currently use Expressions
and I can still publish, but using a lot of those components that
require FPSE:
http://www.timeforweb.com/frontpage/forum/forum_posts.asp?TID=5894&PN=1
are probably going to be gone soon to rely on server side languages.
FPSE are not all that secure and when MS came out with FP 2003 but not
FPSE 2003, that was our first clue that something else was in the works

-Corey
http://www.loudcommerce.com/promo/google.asp



.

Relevant Pages

  • RE: submit button issues?
    ... you.......That was the problem I didnt have FPSE. ... This is the first time I have ever attempted to create a ... "brelade" wrote: ... When it asks you to save, choose in my network places, if you dont see it ...
    (microsoft.public.publisher.webdesign)
  • Re: Coming Expression replacement for FrontPage
    ... Microsoft was trying to re-do the HTML compliant coding. ... They could not do it and now Expressions creates coding that is much ... FPSE are not all that secure and when MS came out with FP 2003 but not ...
    (microsoft.public.frontpage)