| darrel 2004-03-19, 6:29 pm |
| > Has anyone heard of Code Behind? Are any of you producing code that is a
part
> of a web application?
CodeBehind is just MS's terms for putting the server and client scripting in
a separate file than the HTML.
> Why hasn't Macromedia included Code Behind in the product and why do
they
> charge an additional US$ 895 for the honor and privilege of learning how
to
> make use of Code Behind in Dreamweaver MX 2004?
I have no idea, actually. Do you have a URL with more info?
> Code Behind creates a separate file that contains the ASP.NET C# code
> (typically in a file with an added extension of .cs after the fashion of
the
> ASP.net file) this is then compiled into a DLL so that your superbly
written
> code is kept away from prying eyes when the user runs your web
application.
> e.g. hello.aspx - hello.aspx.cs
Uh...right...I guess you already knew the answer, then. It's not specific to
C#, but rather any language .net supports. Also, even if your .net code is
in your aspx page, the end-user still can't see it. The DLL option is useful
to hide your code from clients that may purchase your application and
install it themselves.
> Comments (especially from anyone who has invested in the Code Behind
training)
There's really no training. If you want to use it, learn VS.Net (which I
hate, but hey, that's MS for you...) Otherwise, just do everything in one
page in DW. Then, down the road, if you really want to hide all the code
from your clients, just move the code into self-contained files and compile
them into DLLs and use them as custom class libraries.
-Darrel
|