Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based
applications and have no need for web services, asp etc. I suspect the back
will be broken in VB6 once the VB6 support date is met. So I have begun
looking at VBNet. I like the sound of the VB 2005 Express edition as this
almost sounds like it was designed for people like myself who have neither
the time nor money to become gurus but clearly there is a lot of learning
required to become just basically efficient in VBNet whatever the software
package. This is going to be costly in time and materials. My concern is
that a few years down the line VBNet will see a support end date and along
comes something else. Also the newer versions of the dotnet framework dont
seem to be compatiable with older versions of the VBNet software. To keep
up, legally, requires more cash output in buying the upgraded VBNet
software. Among other things this is all off-putting but if I knew VBNet was
going to be around for a long enough length of time to justify the efforts
might be helpful.
KT 14 2219
Continuing what Robin said. Microsoft is making a huge shift towards .NET
and making it the foundation for other products. If you look at Longhorn,
..NET is an integral part of the operating system, so given that is expected
out in 2006 (I think) and WinFX (2007) has the same plans, I would expect
..NET to be around for a long long time. Especially long enough for you to
justify spending the $10 that express editions are supposed to cost (I'm not
sure on that price, but I've just heard from others it's not going to cost
much at all).
I personally think (as a hobbyist in many forms) that the 700 dollars a
professional edition costs of VS, or even the ~200 the Standard edition
costs is well worth the money. I have other hobbies that cost a LOT more
per year than that.
Just my 2 cents...
-CJ
"Robin Tucker" <id*************************@reallyidont.com> wrote in
message news:cl*******************@news.demon.co.uk... If you look at how long VB has been supported (through all of its incarnations, from VB3), you will see that its a considerable period of
time (in computing terms). In fact, VB6 is still supported, even though VB.NET has been out for some years. Moreover (and this point is just as important), regardless of whether VB.NET remains supported, by learning VB.NET, you will pick up .NET framework experience, which is transferrable to the other languages in the .NET suite (C# for instance).
"KT" <no*****@noemail.com> wrote in message news:Oo**************@TK2MSFTNGP14.phx.gbl... Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based applications and have no need for web services, asp etc. I suspect the back will be broken in VB6 once the VB6 support date is met. So I have begun looking at VBNet. I like the sound of the VB 2005 Express edition as
this almost sounds like it was designed for people like myself who have
neither the time nor money to become gurus but clearly there is a lot of
learning required to become just basically efficient in VBNet whatever the
software package. This is going to be costly in time and materials. My concern is that a few years down the line VBNet will see a support end date and
along comes something else. Also the newer versions of the dotnet framework
dont seem to be compatiable with older versions of the VBNet software. To
keep up, legally, requires more cash output in buying the upgraded VBNet software. Among other things this is all off-putting but if I knew VBNet was going to be around for a long enough length of time to justify the
efforts might be helpful.
KT
If you look at how long VB has been supported (through all of its
incarnations, from VB3), you will see that its a considerable period of time
(in computing terms). In fact, VB6 is still supported, even though VB.NET
has been out for some years. Moreover (and this point is just as
important), regardless of whether VB.NET remains supported, by learning
VB.NET, you will pick up .NET framework experience, which is transferrable
to the other languages in the .NET suite (C# for instance).
"KT" <no*****@noemail.com> wrote in message
news:Oo**************@TK2MSFTNGP14.phx.gbl... Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based applications and have no need for web services, asp etc. I suspect the back will be broken in VB6 once the VB6 support date is met. So I have begun looking at VBNet. I like the sound of the VB 2005 Express edition as this almost sounds like it was designed for people like myself who have neither the time nor money to become gurus but clearly there is a lot of learning required to become just basically efficient in VBNet whatever the software package. This is going to be costly in time and materials. My concern is that a few years down the line VBNet will see a support end date and along comes something else. Also the newer versions of the dotnet framework dont seem to be compatiable with older versions of the VBNet software. To keep up, legally, requires more cash output in buying the upgraded VBNet software. Among other things this is all off-putting but if I knew VBNet was going to be around for a long enough length of time to justify the efforts might be helpful.
KT
Continuing what Robin said. Microsoft is making a huge shift towards .NET
and making it the foundation for other products. If you look at Longhorn,
..NET is an integral part of the operating system, so given that is expected
out in 2006 (I think) and WinFX (2007) has the same plans, I would expect
..NET to be around for a long long time. Especially long enough for you to
justify spending the $10 that express editions are supposed to cost (I'm not
sure on that price, but I've just heard from others it's not going to cost
much at all).
I personally think (as a hobbyist in many forms) that the 700 dollars a
professional edition costs of VS, or even the ~200 the Standard edition
costs is well worth the money. I have other hobbies that cost a LOT more
per year than that.
Just my 2 cents...
-CJ
"Robin Tucker" <id*************************@reallyidont.com> wrote in
message news:cl*******************@news.demon.co.uk... If you look at how long VB has been supported (through all of its incarnations, from VB3), you will see that its a considerable period of
time (in computing terms). In fact, VB6 is still supported, even though VB.NET has been out for some years. Moreover (and this point is just as important), regardless of whether VB.NET remains supported, by learning VB.NET, you will pick up .NET framework experience, which is transferrable to the other languages in the .NET suite (C# for instance).
"KT" <no*****@noemail.com> wrote in message news:Oo**************@TK2MSFTNGP14.phx.gbl... Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based applications and have no need for web services, asp etc. I suspect the back will be broken in VB6 once the VB6 support date is met. So I have begun looking at VBNet. I like the sound of the VB 2005 Express edition as
this almost sounds like it was designed for people like myself who have
neither the time nor money to become gurus but clearly there is a lot of
learning required to become just basically efficient in VBNet whatever the
software package. This is going to be costly in time and materials. My concern is that a few years down the line VBNet will see a support end date and
along comes something else. Also the newer versions of the dotnet framework
dont seem to be compatiable with older versions of the VBNet software. To
keep up, legally, requires more cash output in buying the upgraded VBNet software. Among other things this is all off-putting but if I knew VBNet was going to be around for a long enough length of time to justify the
efforts might be helpful.
KT
Plus, i wouldnt worry about the learning curve so much. If youre
programming, chances are youre reasonably bright, and so it really shouldnt
be that much trouble to learn the move from VB to VB.NET
"Robin Tucker" <id*************************@reallyidont.com> wrote in
message news:cl*******************@news.demon.co.uk... If you look at how long VB has been supported (through all of its incarnations, from VB3), you will see that its a considerable period of time (in computing terms). In fact, VB6 is still supported, even though VB.NET has been out for some years. Moreover (and this point is just as important), regardless of whether VB.NET remains supported, by learning VB.NET, you will pick up .NET framework experience, which is transferrable to the other languages in the .NET suite (C# for instance).
"KT" <no*****@noemail.com> wrote in message news:Oo**************@TK2MSFTNGP14.phx.gbl... Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based applications and have no need for web services, asp etc. I suspect the back will be broken in VB6 once the VB6 support date is met. So I have begun looking at VBNet. I like the sound of the VB 2005 Express edition as this almost sounds like it was designed for people like myself who have neither the time nor money to become gurus but clearly there is a lot of learning required to become just basically efficient in VBNet whatever the software package. This is going to be costly in time and materials. My concern is that a few years down the line VBNet will see a support end date and along comes something else. Also the newer versions of the dotnet framework dont seem to be compatiable with older versions of the VBNet software. To keep up, legally, requires more cash output in buying the upgraded VBNet software. Among other things this is all off-putting but if I knew VBNet was going to be around for a long enough length of time to justify the efforts might be helpful.
KT
Plus, i wouldnt worry about the learning curve so much. If youre
programming, chances are youre reasonably bright, and so it really shouldnt
be that much trouble to learn the move from VB to VB.NET
"Robin Tucker" <id*************************@reallyidont.com> wrote in
message news:cl*******************@news.demon.co.uk... If you look at how long VB has been supported (through all of its incarnations, from VB3), you will see that its a considerable period of time (in computing terms). In fact, VB6 is still supported, even though VB.NET has been out for some years. Moreover (and this point is just as important), regardless of whether VB.NET remains supported, by learning VB.NET, you will pick up .NET framework experience, which is transferrable to the other languages in the .NET suite (C# for instance).
"KT" <no*****@noemail.com> wrote in message news:Oo**************@TK2MSFTNGP14.phx.gbl... Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based applications and have no need for web services, asp etc. I suspect the back will be broken in VB6 once the VB6 support date is met. So I have begun looking at VBNet. I like the sound of the VB 2005 Express edition as this almost sounds like it was designed for people like myself who have neither the time nor money to become gurus but clearly there is a lot of learning required to become just basically efficient in VBNet whatever the software package. This is going to be costly in time and materials. My concern is that a few years down the line VBNet will see a support end date and along comes something else. Also the newer versions of the dotnet framework dont seem to be compatiable with older versions of the VBNet software. To keep up, legally, requires more cash output in buying the upgraded VBNet software. Among other things this is all off-putting but if I knew VBNet was going to be around for a long enough length of time to justify the efforts might be helpful.
KT
KT wrote: Do we have any idea how long VBNet is going to be supported?
fwiw, VB.Net (the name) is already obsolete. They've dropped the .Net
part from their next release.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
KT wrote: Do we have any idea how long VBNet is going to be supported?
fwiw, VB.Net (the name) is already obsolete. They've dropped the .Net
part from their next release.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
Waht does this have to do with the life expetancy of the product? It's
still .NET under the hood... and will be for quite some time if you read
Microsoft's Roadmaps... at this point, they have no intention of dropping
the .NET framework, just making it stronger
Until of course google sneaks in and takes over the world some how with
their crafty simple products...
"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
news:ez**************@TK2MSFTNGP15.phx.gbl... KT wrote: Do we have any idea how long VBNet is going to be supported?
fwiw, VB.Net (the name) is already obsolete. They've dropped the .Net part from their next release.
-- Ken Halter - MS-MVP-VB - http://www.vbsight.com Please keep all discussions in the groups..
Waht does this have to do with the life expetancy of the product? It's
still .NET under the hood... and will be for quite some time if you read
Microsoft's Roadmaps... at this point, they have no intention of dropping
the .NET framework, just making it stronger
Until of course google sneaks in and takes over the world some how with
their crafty simple products...
"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
news:ez**************@TK2MSFTNGP15.phx.gbl... KT wrote: Do we have any idea how long VBNet is going to be supported?
fwiw, VB.Net (the name) is already obsolete. They've dropped the .Net part from their next release.
-- Ken Halter - MS-MVP-VB - http://www.vbsight.com Please keep all discussions in the groups..
"KT" <no*****@noemail.com> wrote Do we have any idea how long VBNet is going to be supported?
No. How can anyone but the people at MSFT know for sure?
What we can expect, is that, like VB6, even after it life expectancy
has expired, the programs will still, (more or less) run on whatever
the next platform will be.
Due to the heavy investment MSFT is putting into including .Net
in their other offereings, it is a safe bet, they plan to keep that code
working for quite a while... How long is a while? Its anyone's guess!
LFS
"KT" <no*****@noemail.com> wrote Do we have any idea how long VBNet is going to be supported?
No. How can anyone but the people at MSFT know for sure?
What we can expect, is that, like VB6, even after it life expectancy
has expired, the programs will still, (more or less) run on whatever
the next platform will be.
Due to the heavy investment MSFT is putting into including .Net
in their other offereings, it is a safe bet, they plan to keep that code
working for quite a while... How long is a while? Its anyone's guess!
LFS
CJ Taylor wrote: Waht does this have to do with the life expetancy of the product? It's still .NET under the hood... and will be for quite some time if you read Microsoft's Roadmaps... at this point, they have no intention of dropping the .NET framework, just making it stronger
The framework... yes, B#, maybe. It's still a "toy language" as far as
MS is concerned.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote Waht does this have to do with the life expetancy of the product? It's still .NET under the hood... and will be for quite some time if you read Microsoft's Roadmaps... at this point, they have no intention of dropping the .NET framework, just making it stronger
The framework... yes, B#, maybe. It's still a "toy language" as far as MS is concerned.
Have you got a cite you can point to, or is that your own opinion?
LFS
> > The framework... yes, B#, maybe. It's still a "toy language" as far as MS is concerned.
Have you got a cite you can point to, or is that your own opinion?
LFS
ACK
I don't remember MS ever promoting it as a toy language. Given it has
almost identical functionality to C#. Sure C# has some cool features VB
doesn't, but then again, VB has some cool features C# doesn't.
If its a toy language, then I make a hell of a lot of money for getting to
"play". This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: cognite |
last post by:
This venue would surely appreciate the cool stuff being done in
python on bioinformatics and python's tools for info parsing and
extraction (like fulltext indexing, xml tools, parser builders,...
|
by: Showjumper |
last post by:
I cannot get the custom Tag Prefix to work in controls made w/ VBNET. Why???
It works just fine in controls made w/ c#. Is vbnet just buggy?
|
by: KT |
last post by:
Do we have any idea how long VBNet is going to be supported?
Being a hobbyist VB6 user I am only interested in creating windows based
applications and have no need for web services, asp etc. I...
|
by: Jim |
last post by:
Please don't laugh--I'm serious about this--
I finally got around to installing the copy of VBNet I bought last summer.
I didn't see any installation instructions in the box--just a bunch of...
|
by: Jon |
last post by:
I am trying to convert an application from VB to VB.Net. the application is
large (400 + Screens) and (175+ reports).
I am a visual learner meaning if I found examples how to do something in VB...
|
by: |
last post by:
I have written a VBNET sample service that uses FindWindow to find another
VBNET forms app HANDLE and send it a message via SendMessage. The service
runs under the local system account with...
|
by: Marek Wierzbicki |
last post by:
In my MSSQL server 2000 sp4, in performanece monito, buffer memory, page
life expectancy is equal to 0.00000 (average for 10 sec, auto update). I
think sth is wrong configured, but what?
Marek
|
by: bb |
last post by:
Hi,
Have a query regarding the life of temporaries. Here is the code...
class MyNumber {
public:
MyNumber(int n) : n(n) {
cout << "Object Constructed." << endl;
}
|
by: saidgg |
last post by:
i try to audit a specific folder in Unix using Vbnet.
In windows i can audit a sensitif folder using VBnet but folder in Unix(samba share) are not accessible.
Network is showing.
Can someone give...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, we are pleased to welcome back...
|
by: Vimpel783 |
last post by:
Hello!
Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
|
by: jfyes |
last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
|
by: ArrayDB |
last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Defcon1945 |
last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
|
by: af34tf |
last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome former...
| |