By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,865 Members | 1,725 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,865 IT Pros & Developers. It's quick & easy.

Page Directive & Dreamweaver??

P: n/a
Hi all,

I am using a dreamweaver template for a web app i am working on.

Each time i update the template my page directives at the top of the
associated pages gets removed.

Anyone had problems with this?
Know how to fix?
Fill me in on what is going on?

Cheers,
Adam
Jan 31 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
First of all, you should NEVER use any editor not intended for ASP.NET to
edit .aspx files. Editors such as Dreamweaver are HTML editors and do not
know what the directives do, and because they are wysiwyg (visual) editors,
they will usually recreate all the code each time, or at least remove parts
of the code that they do not know what mean. My suggestion is to do one of
the following:
Avoid editors other than the one you use to create your ASP.NET application
(probably Visual Studio .NET)

OR

If you really want to use a graphical HTML editor, create a separate page
using whatever editor you like, and then copy and paste the desired sections
from that code into your .aspx file.
My personal opinion of most graphical HTML editors (including Dreamweaver),
however, is that they are not very good. They often create inefficient and
sometimes unnecessary code. In order to make them create code that is good
enough to be worth using you often need to put in so much effort that it
would be quicker to write it by hand. But even more important, why are you
trying to edit your file in another editor anyway? Only ASP.NET editors will
be able to recognize your webcontrols, so unless you plan on using all HTML
controls in your code, a graphical HTML editor won't be much help. And if
you do plan on using only HTML controls, why are you making it in ASP.NET to
begin with?
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"Adam Knight" <ad**@pertrain.com.au> wrote in message
news:Ol*************@TK2MSFTNGP15.phx.gbl...
Hi all,

I am using a dreamweaver template for a web app i am working on.

Each time i update the template my page directives at the top of the
associated pages gets removed.

Anyone had problems with this?
Know how to fix?
Fill me in on what is going on?

Cheers,
Adam

Feb 1 '06 #2

P: n/a
Let me respond to say that DreamWeaver supports the development of
non-code-behind ASPX pages, so your premise that DreamWeaver is not intended
for ASP.NET is incorrect. Just because Microsoft didn't produce the tool
doesn't mean that you cannot use for ASP.NET development.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Nathan Sokalski" <nj********@hotmail.com> wrote in message
news:ec*************@TK2MSFTNGP15.phx.gbl...
First of all, you should NEVER use any editor not intended for ASP.NET to
edit .aspx files. Editors such as Dreamweaver are HTML editors and do not
know what the directives do, and because they are wysiwyg (visual)
editors, they will usually recreate all the code each time, or at least
remove parts of the code that they do not know what mean. My suggestion is
to do one of the following:
Avoid editors other than the one you use to create your ASP.NET
application (probably Visual Studio .NET)

OR

If you really want to use a graphical HTML editor, create a separate page
using whatever editor you like, and then copy and paste the desired
sections from that code into your .aspx file.
My personal opinion of most graphical HTML editors (including
Dreamweaver), however, is that they are not very good. They often create
inefficient and sometimes unnecessary code. In order to make them create
code that is good enough to be worth using you often need to put in so
much effort that it would be quicker to write it by hand. But even more
important, why are you trying to edit your file in another editor anyway?
Only ASP.NET editors will be able to recognize your webcontrols, so unless
you plan on using all HTML controls in your code, a graphical HTML editor
won't be much help. And if you do plan on using only HTML controls, why
are you making it in ASP.NET to begin with?
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"Adam Knight" <ad**@pertrain.com.au> wrote in message
news:Ol*************@TK2MSFTNGP15.phx.gbl...
Hi all,

I am using a dreamweaver template for a web app i am working on.

Each time i update the template my page directives at the top of the
associated pages gets removed.

Anyone had problems with this?
Know how to fix?
Fill me in on what is going on?

Cheers,
Adam


Feb 1 '06 #3

P: n/a
Sorry, my bad. But it will still cause problems for most people developing
in ASP.NET if they use Visual Studio at all if it can't support codebehind
files, since that is what Visual Studio uses by default. But I never tried
to imply that only Microsoft's ASP.NET software works, it may be my
preference, but I am willing to believe that there are other good ASP.NET
editors out there. But I have seen the HTML output of Dreamweaver, and when
I edited it by hand, I got it to look exactly the same in about half as much
code.
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"Christopher Reed" <ca****@nospam.nospam> wrote in message
news:eC**************@TK2MSFTNGP15.phx.gbl...
Let me respond to say that DreamWeaver supports the development of
non-code-behind ASPX pages, so your premise that DreamWeaver is not
intended for ASP.NET is incorrect. Just because Microsoft didn't produce
the tool doesn't mean that you cannot use for ASP.NET development.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Nathan Sokalski" <nj********@hotmail.com> wrote in message
news:ec*************@TK2MSFTNGP15.phx.gbl...
First of all, you should NEVER use any editor not intended for ASP.NET to
edit .aspx files. Editors such as Dreamweaver are HTML editors and do not
know what the directives do, and because they are wysiwyg (visual)
editors, they will usually recreate all the code each time, or at least
remove parts of the code that they do not know what mean. My suggestion
is to do one of the following:
Avoid editors other than the one you use to create your ASP.NET
application (probably Visual Studio .NET)

OR

If you really want to use a graphical HTML editor, create a separate page
using whatever editor you like, and then copy and paste the desired
sections from that code into your .aspx file.
My personal opinion of most graphical HTML editors (including
Dreamweaver), however, is that they are not very good. They often create
inefficient and sometimes unnecessary code. In order to make them create
code that is good enough to be worth using you often need to put in so
much effort that it would be quicker to write it by hand. But even more
important, why are you trying to edit your file in another editor anyway?
Only ASP.NET editors will be able to recognize your webcontrols, so
unless you plan on using all HTML controls in your code, a graphical HTML
editor won't be much help. And if you do plan on using only HTML
controls, why are you making it in ASP.NET to begin with?
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"Adam Knight" <ad**@pertrain.com.au> wrote in message
news:Ol*************@TK2MSFTNGP15.phx.gbl...
Hi all,

I am using a dreamweaver template for a web app i am working on.

Each time i update the template my page directives at the top of the
associated pages gets removed.

Anyone had problems with this?
Know how to fix?
Fill me in on what is going on?

Cheers,
Adam



Feb 2 '06 #4

P: n/a
I agree. While DreamWeaver provides some advantages to those who cannot
afford higher priced tools for not only HTML, ASP.NET, PHP, classic ASP,
etc., it has some disadvantages in how it reformats the code when you mess
around with the designer. Then again, before VS 2005, even VS did that too.
Additionally, I agree with you regarding the code-behind disadvantages; then
again, WebMatrix has the similar issues from that perspective.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Nathan Sokalski" <nj********@hotmail.com> wrote in message
news:u$**************@TK2MSFTNGP11.phx.gbl...
Sorry, my bad. But it will still cause problems for most people developing
in ASP.NET if they use Visual Studio at all if it can't support codebehind
files, since that is what Visual Studio uses by default. But I never tried
to imply that only Microsoft's ASP.NET software works, it may be my
preference, but I am willing to believe that there are other good ASP.NET
editors out there. But I have seen the HTML output of Dreamweaver, and
when I edited it by hand, I got it to look exactly the same in about half
as much code.
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"Christopher Reed" <ca****@nospam.nospam> wrote in message
news:eC**************@TK2MSFTNGP15.phx.gbl...
Let me respond to say that DreamWeaver supports the development of
non-code-behind ASPX pages, so your premise that DreamWeaver is not
intended for ASP.NET is incorrect. Just because Microsoft didn't produce
the tool doesn't mean that you cannot use for ASP.NET development.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Nathan Sokalski" <nj********@hotmail.com> wrote in message
news:ec*************@TK2MSFTNGP15.phx.gbl...
First of all, you should NEVER use any editor not intended for ASP.NET
to edit .aspx files. Editors such as Dreamweaver are HTML editors and do
not know what the directives do, and because they are wysiwyg (visual)
editors, they will usually recreate all the code each time, or at least
remove parts of the code that they do not know what mean. My suggestion
is to do one of the following:
Avoid editors other than the one you use to create your ASP.NET
application (probably Visual Studio .NET)

OR

If you really want to use a graphical HTML editor, create a separate
page using whatever editor you like, and then copy and paste the desired
sections from that code into your .aspx file.
My personal opinion of most graphical HTML editors (including
Dreamweaver), however, is that they are not very good. They often create
inefficient and sometimes unnecessary code. In order to make them create
code that is good enough to be worth using you often need to put in so
much effort that it would be quicker to write it by hand. But even more
important, why are you trying to edit your file in another editor
anyway? Only ASP.NET editors will be able to recognize your webcontrols,
so unless you plan on using all HTML controls in your code, a graphical
HTML editor won't be much help. And if you do plan on using only HTML
controls, why are you making it in ASP.NET to begin with?
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"Adam Knight" <ad**@pertrain.com.au> wrote in message
news:Ol*************@TK2MSFTNGP15.phx.gbl...
Hi all,

I am using a dreamweaver template for a web app i am working on.

Each time i update the template my page directives at the top of the
associated pages gets removed.

Anyone had problems with this?
Know how to fix?
Fill me in on what is going on?

Cheers,
Adam



Feb 2 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.