I agree with that. Personally, I like the code behind model. I've known
for a bit over a year that Whidbey will focus more on inline code, but many
developers will want to stick with code behind because of the way they
develop. For people who are used to doing something such as writing an
interface for a third-party to use while implementation in an object is
completed, the code behind model feels very comfortable.
In the case of using FrontPage (or any other non-VS.NET Web development
tool), code behind is a means to secure your code not only from prying
eyes, but from inadvertant changes.
One of the major benefits of using FrontPage 2003 as opposed to earlier
versions is that FrontPage 2003 can render many Server Controls. In
earlier versions, you just see a placeholder. In FrontPage 2003, you are
able to more easily with with Server Control content. However, keep in
mind that you can't edit most Server Controls in the FrontPage UI. For
example, if you try and edit text that is inside of an ASP.NET Panel
control in FrontPage, you may notice that you never even get an I beam
pointer.
Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
jamesche@online.microsoft.com
This post is provided as-is with no warranties and confers no rights.
--------------------[color=blue]
>From: "Cowboy \(Gregory A. Beamer\)" <NoSpamMgbworld@comcast.netNoSpamM>
>References: <Xns94465D5EC1794JimHeaveyhotmailcom@207.46.248.16 >[/color]
<aTM7WDcuDHA.1412@cpmsftngxa06.phx.gbl>[color=blue]
>Subject: Re: VS.Net And FrontPage
>Date: Wed, 3 Dec 2003 12:50:40 -0600
>Lines: 69
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <uDcAq5cuDHA.556@TK2MSFTNGP11.phx.gbl>
>Newsgroups: microsoft.public.dotnet.framework.aspnet
>NNTP-Posting-Host: 170.143.252.32
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP11.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:194815
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
>
>I concur with Jim's assessment on this one, although I have not had a
>problem with FrontPage 2002 messing with my ASP.NET tags. I would still aim
>towards the CodeBehind methodology (ASP.NET in the aspx page, and code in
>either the aspx.vb (VB.NET) or aspx.cs (C#) page, depending on language).
>
>--
>Gregory A. Beamer
>MVP; MCP: +I, SE, SD, DBA
>
>************************************************* *********************
>Think Outside the Box!
>************************************************* *********************
>"Jim Cheshire [MSFT]" <jamesche@online.microsoft.com> wrote in message
>news:aTM7WDcuDHA.1412@cpmsftngxa06.phx.gbl...[color=green]
>> Hi Jim,
>>
>> You can certainly open the FrontPage Web site in Visual Studio .NET and[/color]
>add[color=green]
>> Server Controls and code. The only problem that you might encounter is
>> with pre-FrontPage 2003 versions not understanding the ASP.NET Server
>> Controls. For best compatibility, I would use FrontPage 2003 since it
>> supports ASP.NET.
>>
>> Jim Cheshire, MCSE, MCSD [MSFT]
>> Developer Support
>> ASP.NET
>>
jamesche@online.microsoft.com
>>
>> This post is provided as-is with no warranties and confers no rights.
>>
>> --------------------[color=darkred]
>> >Subject: VS.Net And FrontPage
>> >From: Jim Heavey <JimHeavey@nospam.com>
>> >Organization: Jim Heavey and Associates
>> >Message-ID: <Xns94465D5EC1794JimHeaveyhotmailcom@207.46.248.16 >
>> >User-Agent: Xnews/5.04.25
>> >Newsgroups: microsoft.public.dotnet.framework.aspnet
>> >Date: Wed, 03 Dec 2003 07:10:37 -0800
>> >NNTP-Posting-Host: 64-151-17-137-dhcp-kc.everestkc.net 64.151.17.137
>> >Lines: 1
>> >Path:[/color]
>>[/color]
>cpmsftngxa06.phx.gbl!cpmsftngxa09.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP10[/color]
