ASP (not asp.net)

22 Apr 2009 3:37 PM

JC

Hello,
I am a visual foxpro programmer and already very dissapointed that MS is
killing this product. Now I have to deal with the ASP future since ASP.net is
absolutely not what I need. My clients are not looking for a product capable
to manage any kind of corporation but simple small/medium business willing to
provide a simple Intranet. So my question is simple can I continu using ASP
(not asp.net) or do I have to deal with one more product discontinued ?

JC

22 Apr 2009 3:50 PM

Daniel Crichton

JC wrote on Wed, 22 Apr 2009 08:37:02 -0700:

> Hello,
> I am a visual foxpro programmer and already very dissapointed that MS
> is killing this product. Now I have to deal with the ASP future since
> ASP.net is absolutely not what I need. My clients are not looking for
> a product capable to manage any kind of corporation but simple
> small/medium business willing to provide a simple Intranet. So my
> question is simple can I continu using ASP (not asp.net) or do I have
> to deal with one more product discontinued ?

Yes, you can continue to use ASP. Windows 2008 still supports it (I actually
spoke to someone from the Windows 2008 team at TechEd who pointed out that
the initial release of Core could run classic ASP but not ASP.NET because it
didn't include the .NET Framework!). However whether that support remains in
future versions of Windows is up to Microsoft.

--
Dan

22 Apr 2009 3:50 PM

Bob Barrows

JC wrote:

> Hello,
> I am a visual foxpro programmer and already very dissapointed that MS
> is killing this product. Now I have to deal with the ASP future since
> ASP.net is absolutely not what I need. My clients are not looking for
> a product capable to manage any kind of corporation but simple
> small/medium business willing to provide a simple Intranet. So my
> question is simple can I continu using ASP (not asp.net) or do I have
> to deal with one more product discontinued ?
>

Classic ASP will not go away.
http://www.hanselman.com/blog/LifecycleSupportForClassicASPInWindows.aspx

--
HTH,
Bob Barrows

22 Apr 2009 4:05 PM

Daniel Crichton

Bob wrote on Wed, 22 Apr 2009 11:50:55 -0400:

> JC wrote:
>> Hello,
>> I am a visual foxpro programmer and already very dissapointed that MS
>> is killing this product. Now I have to deal with the ASP future since
>> ASP.net is absolutely not what I need. My clients are not looking for
>> a product capable to manage any kind of corporation but simple
>> small/medium business willing to provide a simple Intranet. So my
>> question is simple can I continu using ASP (not asp.net) or do I have
>> to deal with one more product discontinued ?

> Classic ASP will not go away.
> http://www.hanselman.com/blog/LifecycleSupportForClassicASPInWindows.
> aspx

While it will get lifecycle support on versions of Windows that are still in
their support period, it doesn't mean that the next version of Windows
Server will include it. Then again 5 years from now I'll probably still be
running sites on Windows 2003 so it's not a huge problem for me yet ;)

--
Dan

22 Apr 2009 5:04 PM

Bob Barrows

Daniel Crichton wrote:
Show quoteHide quote

> Bob wrote on Wed, 22 Apr 2009 11:50:55 -0400:
>
>> JC wrote:
> >> Hello,
> >> I am a visual foxpro programmer and already very dissapointed
> that MS >> is killing this product. Now I have to deal with the ASP
> future since >> ASP.net is absolutely not what I need. My clients
> are not looking for >> a product capable to manage any kind of
> corporation but simple >> small/medium business willing to provide a
> simple Intranet. So my >> question is simple can I continu using ASP
> (not asp.net) or do I have >> to deal with one more product
> discontinued ?
>
>> Classic ASP will not go away.
>> http://www.hanselman.com/blog/LifecycleSupportForClassicASPInWindows.
>> aspx
>
> While it will get lifecycle support on versions of Windows that are
> still in their support period, it doesn't mean that the next version
> of Windows Server will include it. Then again 5 years from now I'll
> probably still be running sites on Windows 2003 so it's not a huge
> problem for me yet ;)
>

Even if it isn't included, there will be nothing to prevent someone from
registering the asp.dll file on that machine, will there?

--
HTH,
Bob Barrows

23 Apr 2009 10:01 AM

Daniel Crichton

Bob wrote on Wed, 22 Apr 2009 13:04:46 -0400:

Show quoteHide quote

> Daniel Crichton wrote:
>> Bob wrote on Wed, 22 Apr 2009 11:50:55 -0400:

>>> JC wrote:
>>>> Hello,
>>>> I am a visual foxpro programmer and already very dissapointed
>> that MS >> is killing this product. Now I have to deal with the ASP
>> future since >> ASP.net is absolutely not what I need. My clients
>> are not looking for >> a product capable to manage any kind of
>> corporation but simple >> small/medium business willing to provide a
>> simple Intranet. So my >> question is simple can I continu using ASP
>> (not asp.net) or do I have >> to deal with one more product
>> discontinued ?

>>> Classic ASP will not go away.
>>> http://www.hanselman.com/blog/LifecycleSupportForClassicASPInWindows.
>>> aspx

>> While it will get lifecycle support on versions of Windows that are
>> still in their support period, it doesn't mean that the next version
>> of Windows Server will include it. Then again 5 years from now I'll
>> probably still be running sites on Windows 2003 so it's not a huge
>> problem for me yet ;)

> Even if it isn't included, there will be nothing to prevent someone
> from registering the asp.dll file on that machine, will there?

Assuming that version of Windows would still allow it to be registered, and
that IIS still has ability to pass files to it to be processed. Then again,
hopefully that time is far enough away that I don't have to worry about it
for at least a few more years ;)

--
Dan

30 Apr 2009 6:13 AM

Mark McGinty

Show quote Hide quote

"Daniel Crichton" <msn***@worldofspack.com> wrote in message
news:uf0G%23p$wJHA.4364@TK2MSFTNGP03.phx.gbl...
> Bob wrote on Wed, 22 Apr 2009 13:04:46 -0400:
>
>> Daniel Crichton wrote:
> >> Bob wrote on Wed, 22 Apr 2009 11:50:55 -0400:
>
> >>> JC wrote:
> >>>> Hello,
> >>>> I am a visual foxpro programmer and already very dissapointed
> >> that MS >> is killing this product. Now I have to deal with the ASP
> >> future since >> ASP.net is absolutely not what I need. My clients
> >> are not looking for >> a product capable to manage any kind of
> >> corporation but simple >> small/medium business willing to provide a
> >> simple Intranet. So my >> question is simple can I continu using ASP
> >> (not asp.net) or do I have >> to deal with one more product
> >> discontinued ?
>
> >>> Classic ASP will not go away.
> >>> http://www.hanselman.com/blog/LifecycleSupportForClassicASPInWindows.
> >>> aspx
>
> >> While it will get lifecycle support on versions of Windows that are
> >> still in their support period, it doesn't mean that the next version
> >> of Windows Server will include it. Then again 5 years from now I'll
> >> probably still be running sites on Windows 2003 so it's not a huge
> >> problem for me yet ;)
>
>> Even if it isn't included, there will be nothing to prevent someone
>> from registering the asp.dll file on that machine, will there?
>
> Assuming that version of Windows would still allow it to be registered,
> and that IIS still has ability to pass files to it to be processed. Then
> again, hopefully that time is far enough away that I don't have to worry
> about it for at least a few more years ;)

ASP.DLL is just an ISAPI filter, correct? So unless they orphaned the ISAPI
spec [highly unlikely], or did away with IActiveScript [likewise highly
unlikely], or did something really sleazy like explicitly preventing ASP.DLL
from loading [no speculation as to liklihood], then classic ASP will
necessarily continue to be possible long after it is supported. (Consider
CDONTS.DLL as an example: declared deprecated as of Server 2000, not shipped
as of 2003, still very much usable.)

-MM

Show quoteHide quote

> --
> Dan
>

24 Apr 2009 7:19 AM

Sylvain Lafontaine

Technically, it will still be supported in the near future; however, this
will be at a very basic level. For example, Web Expression 2.0 don't
support ASP but do support PHP and ASP.NET.

If I were you, I would go with either ASP.NET or PHP, not ASP anymore. With
ASP, there is no future and when there isn't any future, there's not much
present either.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

Show quoteHide quote

"JC" <J*@discussions.microsoft.com> wrote in message
news:8BFD67E7-147F-4A50-8B2C-EEFF36ADD000@microsoft.com...
> Hello,
> I am a visual foxpro programmer and already very dissapointed that MS is
> killing this product. Now I have to deal with the ASP future since ASP.net
> is
> absolutely not what I need. My clients are not looking for a product
> capable
> to manage any kind of corporation but simple small/medium business willing
> to
> provide a simple Intranet. So my question is simple can I continu using
> ASP
> (not asp.net) or do I have to deal with one more product discontinued ?
>
> JC

3 May 2009 2:33 PM

JM

> If I were you, I would go with either ASP.NET or PHP, not ASP anymore.
> With ASP, there is no future and when there isn't any future, there's not
> much present either.

But that's not what his "customers" seem to want or need.

ASP.NET adds complexities that a lot of small businesses just don't want
to have to deal with whereas ASP simply adds a single file to IIS. About as
simple as scripting gets in today's world..

John