FrontPage Templates need to have aspx support by allowing editable

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Front page templates need to support editable content prior to the opening
html tag (such as exists in dreamweaver), otherwise the templates are useless
for aspx page, because when the template is re-applied, it overwrites the
aspx page declaration and any user control reference tags.
If this support is present, could any one let me know. It is supprising that
microsoft does not support its own technology. For me this is the #1 feature
of dreamweaver, and i would swith to frontpage in a heartbeat for its
supperior stability, if only templates could support this.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...96ff7cbf&dg=microsoft.public.frontpage.client
 
Unfortunately the FP 2003 DWT currently does not support it
- hopefully lots of peope will also vote to Agree w/ your post and MS will
get the message that many of us MVPs also have been pressing for (to correct
this shortcoming)
 
I just fiqured out how to include template support. While not eloquent, it
works. If i manually type in a begin and end instance of an editable region
previous to the html block (which is technically outside of the template
begin region): it still works, and is not overwritten when applying a
template update.

Also Visual Studio does not change the template tags (which is great
because visual studio does change the placement of dreamweaver template tags
when placed outside of the html block -even when told not to - another
problem area, especially after correcting it 20 times in a day).

So for me, this has really opened up front page as a usuable tool!

If someone from microsoft reads this - please add this support in an
eloquent form - it is not that hard to do, and this is a huge huge plus. It
could even be an extension to the exstsing tags, thus backwards compatible,
and perhaps as simple as a plugin or updated feature to existing frontpage
2003. (while you are at it, why not add optional updatable regions as well).

This is not just a convience. In the 'real' world of small to moderate sites
(i.e., 20 to a 200 pages), when a set of pages are created, they are almost
always template based. This means if a client or another party involved with
the site, wants to change a templated area - they have to use the same
software. Many clients feel more comforatable using a front-page package than
learning dreamweaver, and the cost is more reasonable.
Yet without this template support on aspx pages, it is an impossibily for
..net sites.
THIS WILL OPEN UP NEW MARKETS FOR FRONTPAGE AND MAKE LIFE EASIER FOR US.
Also frontpage is so much more stable and quicker, makes for a better client
relationship.



Stefan B Rusynko said:
Unfortunately the FP 2003 DWT currently does not support it
- hopefully lots of peope will also vote to Agree w/ your post and MS will
get the message that many of us MVPs also have been pressing for (to correct
this shortcoming)
--
_________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
________________________________________________



Michael V. Khalsa said:
Front page templates need to support editable content prior to the opening
html tag (such as exists in dreamweaver), otherwise the templates are useless
for aspx page, because when the template is re-applied, it overwrites the
aspx page declaration and any user control reference tags.
If this support is present, could any one let me know. It is supprising that
microsoft does not support its own technology. For me this is the #1 feature
of dreamweaver, and i would swith to frontpage in a heartbeat for its
supperior stability, if only templates could support this.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...96ff7cbf&dg=microsoft.public.frontpage.client
 
Michael
Nice Workaround for Creating NEW PAGES only!
- thanks for posting back w/ the discovery (-:

The method only works for NEW pages that don't have ANY code in the page before a DWT is applied
- if there is already code in the page do not apply a DWT (see below)

Recap:
Adding an editable region (for code before or SSI) in Code view to the top of the page (before any DocType or html tags) is
preserved by the DWT when applied - but any existing code is destroyed
(it even supports <% @LANGUAGE="VBSCRIPT" %> for ASP which, when used, must be the first tag in a page)
- even though it is "outside" of the starting DWT template tag (added after the opening html tag)
Similarly adding code after (as an editable region after the </html> tag) Is also Preserved - but any existing code is destroyed
- even though it is "outside" of the ending DWT template tag (added before the closing html tag)

Existing pages:
As a workaround for Existing pages w/ unique code before/after in the pages:
BEFORE you apply a DWT the first time:
Make sure all your coded pages are closed before any initial edits to the DWT to add the new code regions
Open your existing page and Copy all your code before (and code after if needed) to clipboard or notepad Before applying the DWT w/
the page & allowing it to create the new regions,
Then paste you code back into the newly created editable regions of the templated page!
- Further DWT updates to the templated pages will leave the page unique code before/after alone

Agree it would be nice to NOT have to use the workarounds for existing pages
- as for new pages, it is no different than hand coding regions in the Head section for page title, keywords, description, styles,
etc.

Now if we can eventually get the FP 2002 SE in (non WSS) server based Webs to recognize DWTs for automatic updates (w/o opening all
attached pages to update DWT changes) And while Preserving existing Code Before/After), we may have some real use for DWTs in a
professional web dev environment!




|I just fiqured out how to include template support. While not eloquent, it
| works. If i manually type in a begin and end instance of an editable region
| previous to the html block (which is technically outside of the template
| begin region): it still works, and is not overwritten when applying a
| template update.
|
| Also Visual Studio does not change the template tags (which is great
| because visual studio does change the placement of dreamweaver template tags
| when placed outside of the html block -even when told not to - another
| problem area, especially after correcting it 20 times in a day).
|
| So for me, this has really opened up front page as a usuable tool!
|
| If someone from microsoft reads this - please add this support in an
| eloquent form - it is not that hard to do, and this is a huge huge plus. It
| could even be an extension to the exstsing tags, thus backwards compatible,
| and perhaps as simple as a plugin or updated feature to existing frontpage
| 2003. (while you are at it, why not add optional updatable regions as well).
|
| This is not just a convience. In the 'real' world of small to moderate sites
| (i.e., 20 to a 200 pages), when a set of pages are created, they are almost
| always template based. This means if a client or another party involved with
| the site, wants to change a templated area - they have to use the same
| software. Many clients feel more comforatable using a front-page package than
| learning dreamweaver, and the cost is more reasonable.
| Yet without this template support on aspx pages, it is an impossibily for
| .net sites.
| THIS WILL OPEN UP NEW MARKETS FOR FRONTPAGE AND MAKE LIFE EASIER FOR US.
| Also frontpage is so much more stable and quicker, makes for a better client
| relationship.
|
|
|
| "Stefan B Rusynko" wrote:
|
| > Unfortunately the FP 2003 DWT currently does not support it
| > - hopefully lots of peope will also vote to Agree w/ your post and MS will
| > get the message that many of us MVPs also have been pressing for (to correct
| > this shortcoming)
| > --
| > _________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > ________________________________________________
| >
| >
| >
| > "Michael V. Khalsa" wrote:
| >
| > > Front page templates need to support editable content prior to the opening
| > > html tag (such as exists in dreamweaver), otherwise the templates are useless
| > > for aspx page, because when the template is re-applied, it overwrites the
| > > aspx page declaration and any user control reference tags.
| > > If this support is present, could any one let me know. It is supprising that
| > > microsoft does not support its own technology. For me this is the #1 feature
| > > of dreamweaver, and i would swith to frontpage in a heartbeat for its
| > > supperior stability, if only templates could support this.
| > >
| > > ----------------
| > > This post is a suggestion for Microsoft, and Microsoft responds to the
| > > suggestions with the most votes. To vote for this suggestion, click the "I
| > > Agree" button in the message pane. If you do not see the button, follow this
| > > link to open the suggestion in the Microsoft Web-based Newsreader and then
| > > click "I Agree" in the message pane.
| > >
| > >
http://www.microsoft.com/office/com...96ff7cbf&dg=microsoft.public.frontpage.client
 
PS
If using the workarounds:
Be aware that renaming the DWT editable regions outside of the DWT template tags is not supported
And the starting editable region tag in the templated page (<!-- #BeginEditable "xxx" -->) is editable
(but should not be)

--




| Michael
| Nice Workaround for Creating NEW PAGES only!
| - thanks for posting back w/ the discovery (-:
|
| The method only works for NEW pages that don't have ANY code in the page before a DWT is applied
| - if there is already code in the page do not apply a DWT (see below)
|
| Recap:
| Adding an editable region (for code before or SSI) in Code view to the top of the page (before any DocType or html tags) is
| preserved by the DWT when applied - but any existing code is destroyed
| (it even supports <% @LANGUAGE="VBSCRIPT" %> for ASP which, when used, must be the first tag in a page)
| - even though it is "outside" of the starting DWT template tag (added after the opening html tag)
| Similarly adding code after (as an editable region after the </html> tag) Is also Preserved - but any existing code is destroyed
| - even though it is "outside" of the ending DWT template tag (added before the closing html tag)
|
| Existing pages:
| As a workaround for Existing pages w/ unique code before/after in the pages:
| BEFORE you apply a DWT the first time:
| Make sure all your coded pages are closed before any initial edits to the DWT to add the new code regions
| Open your existing page and Copy all your code before (and code after if needed) to clipboard or notepad Before applying the DWT
w/
| the page & allowing it to create the new regions,
| Then paste you code back into the newly created editable regions of the templated page!
| - Further DWT updates to the templated pages will leave the page unique code before/after alone
|
| Agree it would be nice to NOT have to use the workarounds for existing pages
| - as for new pages, it is no different than hand coding regions in the Head section for page title, keywords, description, styles,
| etc.
|
| Now if we can eventually get the FP 2002 SE in (non WSS) server based Webs to recognize DWTs for automatic updates (w/o opening
all
| attached pages to update DWT changes) And while Preserving existing Code Before/After), we may have some real use for DWTs in a
| professional web dev environment!
|
| _____________________________________________
| SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| "Warning - Using the F1 Key will not break anything!" (-;
| To find the best Newsgroup for FrontPage support see:
| http://www.net-sites.com/sitebuilder/newsgroups.asp
| _____________________________________________
|
|
| ||I just fiqured out how to include template support. While not eloquent, it
|| works. If i manually type in a begin and end instance of an editable region
|| previous to the html block (which is technically outside of the template
|| begin region): it still works, and is not overwritten when applying a
|| template update.
||
|| Also Visual Studio does not change the template tags (which is great
|| because visual studio does change the placement of dreamweaver template tags
|| when placed outside of the html block -even when told not to - another
|| problem area, especially after correcting it 20 times in a day).
||
|| So for me, this has really opened up front page as a usuable tool!
||
|| If someone from microsoft reads this - please add this support in an
|| eloquent form - it is not that hard to do, and this is a huge huge plus. It
|| could even be an extension to the exstsing tags, thus backwards compatible,
|| and perhaps as simple as a plugin or updated feature to existing frontpage
|| 2003. (while you are at it, why not add optional updatable regions as well).
||
|| This is not just a convience. In the 'real' world of small to moderate sites
|| (i.e., 20 to a 200 pages), when a set of pages are created, they are almost
|| always template based. This means if a client or another party involved with
|| the site, wants to change a templated area - they have to use the same
|| software. Many clients feel more comforatable using a front-page package than
|| learning dreamweaver, and the cost is more reasonable.
|| Yet without this template support on aspx pages, it is an impossibily for
|| .net sites.
|| THIS WILL OPEN UP NEW MARKETS FOR FRONTPAGE AND MAKE LIFE EASIER FOR US.
|| Also frontpage is so much more stable and quicker, makes for a better client
|| relationship.
||
||
||
|| "Stefan B Rusynko" wrote:
||
|| > Unfortunately the FP 2003 DWT currently does not support it
|| > - hopefully lots of peope will also vote to Agree w/ your post and MS will
|| > get the message that many of us MVPs also have been pressing for (to correct
|| > this shortcoming)
|| > --
|| > _________________________________________
|| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
|| > "Warning - Using the F1 Key will not break anything!" (-;
|| > ________________________________________________
|| >
|| >
|| >
|| > "Michael V. Khalsa" wrote:
|| >
|| > > Front page templates need to support editable content prior to the opening
|| > > html tag (such as exists in dreamweaver), otherwise the templates are useless
|| > > for aspx page, because when the template is re-applied, it overwrites the
|| > > aspx page declaration and any user control reference tags.
|| > > If this support is present, could any one let me know. It is supprising that
|| > > microsoft does not support its own technology. For me this is the #1 feature
|| > > of dreamweaver, and i would swith to frontpage in a heartbeat for its
|| > > supperior stability, if only templates could support this.
|| > >
|| > > ----------------
|| > > This post is a suggestion for Microsoft, and Microsoft responds to the
|| > > suggestions with the most votes. To vote for this suggestion, click the "I
|| > > Agree" button in the message pane. If you do not see the button, follow this
|| > > link to open the suggestion in the Microsoft Web-based Newsreader and then
|| > > click "I Agree" in the message pane.
|| > >
|| > >
|
http://www.microsoft.com/office/com...96ff7cbf&dg=microsoft.public.frontpage.client
|
|
 
I just converted over a 100 page site that was previously on a half dozen
dreamweaver MX 7.1 templates. I used site wide search -nd-replace to change
the tag syntax, and to add the editable region at the top, i.e., changing
'<%Page.." to '<-- editable tag syntax.. <%Page.. and simular antics for
creating the closing tag.
Also converted over the dreamweaver templates in a simular manner
for aspx pages, i name the templates exampleName.aspx.dwt

This all worked flawlessly.

HOwever, i was mistaken on the notion that visual studio 2003 does not
change the tag placements for everything above the begining body tag (it
moves all commented tags, i.e., editable tags, down to the body tag. It does
the same for dreamweaver tags. however this is a visual studio issues, and
not one for frontpage.

much easier to work with the site in frontpage, because frontpage works,
does not crash, and its faster.

Stefan B Rusynko said:
PS
If using the workarounds:
Be aware that renaming the DWT editable regions outside of the DWT template tags is not supported
And the starting editable region tag in the templated page (<!-- #BeginEditable "xxx" -->) is editable
(but should not be)

--




| Michael
| Nice Workaround for Creating NEW PAGES only!
| - thanks for posting back w/ the discovery (-:
|
| The method only works for NEW pages that don't have ANY code in the page before a DWT is applied
| - if there is already code in the page do not apply a DWT (see below)
|
| Recap:
| Adding an editable region (for code before or SSI) in Code view to the top of the page (before any DocType or html tags) is
| preserved by the DWT when applied - but any existing code is destroyed
| (it even supports <% @LANGUAGE="VBSCRIPT" %> for ASP which, when used, must be the first tag in a page)
| - even though it is "outside" of the starting DWT template tag (added after the opening html tag)
| Similarly adding code after (as an editable region after the </html> tag) Is also Preserved - but any existing code is destroyed
| - even though it is "outside" of the ending DWT template tag (added before the closing html tag)
|
| Existing pages:
| As a workaround for Existing pages w/ unique code before/after in the pages:
| BEFORE you apply a DWT the first time:
| Make sure all your coded pages are closed before any initial edits to the DWT to add the new code regions
| Open your existing page and Copy all your code before (and code after if needed) to clipboard or notepad Before applying the DWT
w/
| the page & allowing it to create the new regions,
| Then paste you code back into the newly created editable regions of the templated page!
| - Further DWT updates to the templated pages will leave the page unique code before/after alone
|
| Agree it would be nice to NOT have to use the workarounds for existing pages
| - as for new pages, it is no different than hand coding regions in the Head section for page title, keywords, description, styles,
| etc.
|
| Now if we can eventually get the FP 2002 SE in (non WSS) server based Webs to recognize DWTs for automatic updates (w/o opening
all
| attached pages to update DWT changes) And while Preserving existing Code Before/After), we may have some real use for DWTs in a
| professional web dev environment!
|
| _____________________________________________
| SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| "Warning - Using the F1 Key will not break anything!" (-;
| To find the best Newsgroup for FrontPage support see:
| http://www.net-sites.com/sitebuilder/newsgroups.asp
| _____________________________________________
|
|
| ||I just fiqured out how to include template support. While not eloquent, it
|| works. If i manually type in a begin and end instance of an editable region
|| previous to the html block (which is technically outside of the template
|| begin region): it still works, and is not overwritten when applying a
|| template update.
||
|| Also Visual Studio does not change the template tags (which is great
|| because visual studio does change the placement of dreamweaver template tags
|| when placed outside of the html block -even when told not to - another
|| problem area, especially after correcting it 20 times in a day).
||
|| So for me, this has really opened up front page as a usuable tool!
||
|| If someone from microsoft reads this - please add this support in an
|| eloquent form - it is not that hard to do, and this is a huge huge plus. It
|| could even be an extension to the exstsing tags, thus backwards compatible,
|| and perhaps as simple as a plugin or updated feature to existing frontpage
|| 2003. (while you are at it, why not add optional updatable regions as well).
||
|| This is not just a convience. In the 'real' world of small to moderate sites
|| (i.e., 20 to a 200 pages), when a set of pages are created, they are almost
|| always template based. This means if a client or another party involved with
|| the site, wants to change a templated area - they have to use the same
|| software. Many clients feel more comforatable using a front-page package than
|| learning dreamweaver, and the cost is more reasonable.
|| Yet without this template support on aspx pages, it is an impossibily for
|| .net sites.
|| THIS WILL OPEN UP NEW MARKETS FOR FRONTPAGE AND MAKE LIFE EASIER FOR US.
|| Also frontpage is so much more stable and quicker, makes for a better client
|| relationship.
||
||
||
|| "Stefan B Rusynko" wrote:
||
|| > Unfortunately the FP 2003 DWT currently does not support it
|| > - hopefully lots of peope will also vote to Agree w/ your post and MS will
|| > get the message that many of us MVPs also have been pressing for (to correct
|| > this shortcoming)
|| > --
|| > _________________________________________
|| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
|| > "Warning - Using the F1 Key will not break anything!" (-;
|| > ________________________________________________
|| >
|| >
|| >
|| > "Michael V. Khalsa" wrote:
|| >
|| > > Front page templates need to support editable content prior to the opening
|| > > html tag (such as exists in dreamweaver), otherwise the templates are useless
|| > > for aspx page, because when the template is re-applied, it overwrites the
|| > > aspx page declaration and any user control reference tags.
|| > > If this support is present, could any one let me know. It is supprising that
|| > > microsoft does not support its own technology. For me this is the #1 feature
|| > > of dreamweaver, and i would swith to frontpage in a heartbeat for its
|| > > supperior stability, if only templates could support this.
|| > >
|| > > ----------------
|| > > This post is a suggestion for Microsoft, and Microsoft responds to the
|| > > suggestions with the most votes. To vote for this suggestion, click the "I
|| > > Agree" button in the message pane. If you do not see the button, follow this
|| > > link to open the suggestion in the Microsoft Web-based Newsreader and then
|| > > click "I Agree" in the message pane.
|| > >
|| > >
|
http://www.microsoft.com/office/com...96ff7cbf&dg=microsoft.public.frontpage.client
|
|
 
Back
Top