clintonG
Thu Apr 28 09:10:32 CDT 2005
Oh yea --- that add-in will be helpful noting the description of the
functionality just helps establish my point that FrontPage 2003 was released
as lame crippleware with regard to its use with Visual Studio.NET 2003.
Anybody that has questions about the use of FrontPage 2003 with Visual
Studio.NET 2003 and vice versa should do themselves a favor and ask
questions in newsgroups such as
news://microsoft.public.dotnet.framework.aspnet and
news://microsoft.public.dotnet.general where they will learn what I stated
to be both factual and truthful without embellishment of any kind.
<%= Clinton Gallagher
"Jim Cheshire (JIMCO)" <contactme@mysite.com> wrote in message
news:ehk8ok%23SFHA.140@TK2MSFTNGP10.phx.gbl...
> clintonG wrote:
>> Let's see what is being said here.
>> What part of my comments are disagreeable? The truthful parts or the
>> factual parts?
>>
>> If my comments were not truthful or factual why would an add-in be
>> needed to make FrontPage work with Visual Studio.NET 2003?
>> I can't accept any any 'easier' blah blah bullsh!t as a response.
>> State the reason the add-in is needed.
>>
>
> As a quick teaser:
>
> * Suppose you could choose selected file types (i.e. cs, vb, vbproj,
> csproj, sln, suo) so that they will NEVER publish when your site is
> published? Sure, you can just set publish status on that file type, but
> when you add new files, will you always remember? Can you afford to push
> your source up to your host?
>
> * Suppose you could ensure that Debug was False in all of your ASP.NET
> pages before you deploy? (This is critically important!)
>
> What part of your post do I disagree with? Inline:
>
> [clintonG said]
>> The main disadvantage is the fact that FrontPage is NOT genuinely
>> integrated
>> nor does it genuinely interoperate with any release of Visual Studio. The
>
>
> How do you define "interoperate"? It is quite easy to open a site in
> FrontPage and VS.NET at the same time and edit in each. However, they
> really aren't supposed to interoperate. As long as each one of them was
> designed to provide UI functionality for ASP.NET, that's all that is
> required.
>
>
>> fact that Visual Studio.NET 2003 has a 'Designer' that mangles and
>> deletes
>> HTML source does not make for a great experience causing lots of wasted
>> time
>> and anguish. So using FrontPage 2003 to develop ASP.NET applications
>> remains
>> a wasteful and costly work in progress.
>
>
> I disagree with that simply because that's what I do with my site and I
> never have any problems. I've been doing it for over 2 years now.
>
> Does VS.NET 7.x have designer issues? Yes, it does. However, it doesn't
> have any issues with the HTML created by FrontPage in my experience. I do
> know the issues involving the designer, I know why they happen, and I know
> how to effectively work around them should I encounter them. Truth is
> that I don't.
>
>
>> Everything remains a work-around as
>> there is pithy support for developing ASP.NET when using FrontPage. The
>> documents at [1],[2] and [3] should be reviewed. More documents from
>> others
>> reading this topic are welcome.
>
> Are you sure that pithy is the word you wanted here? If it is, then
> that's one statement we can agree upon.
>
> --
> Jim Cheshire
> JIMCO
>
http://www.jimcoaddins.com
>
> New Spawn Version!
> Version 1.9.6 adds new features!
> Get it today FREE at:
>
http://www.jimcoaddins.com
>
>
>