VB6 and Server 2008

[Chris J]

Hi all,

I'm posting as a follow-up on this thread:

http://groups.google.co.uk/group/mi...read/thread/25781f7b1d987306/490ef079b658c57a

....I've not found anything more definitive than this, with the exception
of a statement on VB6 support and Vista[1]. Is anyone aware of any
concrete information one way or the other about the amount of support
(or lack thereof) for legacy VB6 apps/components on Server 2008?


Cheers,

Chris....
[1] http://msdn2.microsoft.com/en-us/vbrun/ms788708.aspx

 

[Cor Ligthert[MVP]]

Chris,

I don't know if that is your goal, this kind of message as you stated it are
mostly done by persons who want to create a long trolling message thread
because on the fact that they are disapointed or angry at Microsoft (for
whatever reason).

...I've not found anything more definitive than this, with the exception
of a statement on VB6 support and Vista[1]. Is anyone aware of any
concrete information one way or the other about the amount of support
(or lack thereof) for legacy VB6 apps/components on Server 2008?

VB6 is a programming language from 10 years ago now. Some people did like it
very much and are therefore sad that the support on newer development is
discontinued.

That beside the effort Microsoft has done to make it as easy as possible for
especially VB6 users to go to the newer VB versions. (This even for 3
versions behind VB6). This has result in after VB2002 and VB2003 good
conversion tools in VB2005 and by instance as things which are by the first
VB.Net users not so wanted as the static My class.

If you want to get more information about the lifetime than ask this in one
of the in a way still active classic VB newsgroups. Those which start with
"microsoft.public.vb*".

To others please don't make again a trolling thread from this, two in the
last weeks is in my idea enough.

Cor

 

[Michael D. Ober]

Chris,

I don't know if that is your goal, this kind of message as you stated it
are mostly done by persons who want to create a long trolling message
thread because on the fact that they are disapointed or angry at Microsoft
(for whatever reason).

...I've not found anything more definitive than this, with the exception
of a statement on VB6 support and Vista[1]. Is anyone aware of any
concrete information one way or the other about the amount of support
(or lack thereof) for legacy VB6 apps/components on Server 2008?

VB6 is a programming language from 10 years ago now. Some people did like
it very much and are therefore sad that the support on newer development
is discontinued.

That beside the effort Microsoft has done to make it as easy as possible
for especially VB6 users to go to the newer VB versions. (This even for 3
versions behind VB6). This has result in after VB2002 and VB2003 good
conversion tools in VB2005 and by instance as things which are by the
first VB.Net users not so wanted as the static My class.

If you want to get more information about the lifetime than ask this in
one of the in a way still active classic VB newsgroups. Those which start
with "microsoft.public.vb*".

To others please don't make again a trolling thread from this, two in the
last weeks is in my idea enough.

Cor

It's still a valid question - does Windows Server 2008 support older VB 6
applications?

Mike.

 

[Cor Ligthert [MVP]]

Michael,

It's still a valid question - does Windows Server 2008 support older VB 6
applications?

Yes the same as forever "Who will be the next president of the USA", however
not for this newsgroup.

Cor

 

[Chris J]

Chris,

I don't know if that is your goal, this kind of message as you stated
it are mostly done by persons who want to create a long trolling
message thread because on the fact that they are disapointed or angry
at Microsoft (for whatever reason).

That isn't my intention -- I'm genually trying to determine what the
level of support there will be, if any. Yes I'm aware it's an obsolete
language as far as Microsoft is concerned and that doesn't bother me.
However I'm not in a position where I can port a large legacy app to
..NET (which would be the ideal) -- time and expense being the main factors.

I'll go to the classic VB groups; I posted here simply due to the query
I linked to in my original post which was also posted here.

Cheers,

Chris...