|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Re: Help needed in using FSO's, TextStreams, etc. --- Code Review and Advice requestedI fully understand your frustration. (By the way, "microsoft.com/vbasic" does go to the Visual Basic page; I agree that "microsoft.com/vb" should as well.) Concerning items #g through #i: I can tell you how to become rich beyond your wildest dreams. Start a company that fully supports those who wish to continue with VB6. Make a name for yourself, and then approach Microsoft about licensing the VB6 product and its source code for support and enhancement purposes. Everyone always says Microsoft only cares about money; go ahead and prove it. Convince them that it is in their financial best interest to allow your new company to extend Visual Basic Classic. You can draw a lot more flies with honey than you can with vinegar. Using the keyboard to constantly browbeat another product that, frankly, a lot of people actually like to use is insanity. These forums have no influence on Microsoft's business decisions. But a well-crafted business plan just might. ----- Tim Patrick - www.timaki.com Start-to-Finish Visual Basic 2005 Show quoteHide quote > well... i'll make you a deal buddy > > when microsoft does this: > > a) microsoft.com/vb should GO SOMEWHERE > b) NO vs crashes in a month for me > c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net > d) vb newsgroup should be public.microsoft.vb.. not this > 'microsoft.public.dotnet.languages.vb' crap > e) it isn't verbose like 2002,2003,2005 > f) i can copy and paste datasets in SSRS in between reports > g) they support vb6 > h) they support developing new COM components > i) they support existing ActiveX controls > if all those come true; I might lay off... > > but until then; their backwards ass crap; i've just about had enough > of it > > Tim Patrick wrote: > >> So when the next version of Visual Studio comes out and includes >> Visual Basic--and >> it will, since I've already tried out an early version of it--will >> you promise >> to leave these forums with the shame of a false prophet and never >> post again? >> One can only hope. people like to use VB.net?
ROFL what universe do you come from? show me some stats.. and I'll show you some stats that say '90% of vb developers still use VB6' I would notify the folks at Monster.com and craigslist.org/job because I sure don't see many VB.net _JOBS_ -Larry Tim Patrick wrote: Show quoteHide quote > Except for item #d (which is just a side effect of your overall bad feeling), > I fully understand your frustration. (By the way, "microsoft.com/vbasic" > does go to the Visual Basic page; I agree that "microsoft.com/vb" should > as well.) > > Concerning items #g through #i: I can tell you how to become rich beyond > your wildest dreams. Start a company that fully supports those who wish to > continue with VB6. Make a name for yourself, and then approach Microsoft > about licensing the VB6 product and its source code for support and enhancement > purposes. Everyone always says Microsoft only cares about money; go ahead > and prove it. Convince them that it is in their financial best interest to > allow your new company to extend Visual Basic Classic. > > You can draw a lot more flies with honey than you can with vinegar. Using > the keyboard to constantly browbeat another product that, frankly, a lot > of people actually like to use is insanity. These forums have no influence > on Microsoft's business decisions. But a well-crafted business plan just > might. > > ----- > Tim Patrick - www.timaki.com > Start-to-Finish Visual Basic 2005 > > > well... i'll make you a deal buddy > > > > when microsoft does this: > > > > a) microsoft.com/vb should GO SOMEWHERE > > b) NO vs crashes in a month for me > > c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net > > d) vb newsgroup should be public.microsoft.vb.. not this > > 'microsoft.public.dotnet.languages.vb' crap > > e) it isn't verbose like 2002,2003,2005 > > f) i can copy and paste datasets in SSRS in between reports > > g) they support vb6 > > h) they support developing new COM components > > i) they support existing ActiveX controls > > if all those come true; I might lay off... > > > > but until then; their backwards ass crap; i've just about had enough > > of it > > > > Tim Patrick wrote: > > > >> So when the next version of Visual Studio comes out and includes > >> Visual Basic--and > >> it will, since I've already tried out an early version of it--will > >> you promise > >> to leave these forums with the shame of a false prophet and never > >> post again? > >> One can only hope. But I like VB.NET, and I know others who do as well. I've attended conferences
with hundreds of people who are as excited about it as I am. Your 90% statistic seems high, but I wouldn't doubt that well over 50% of VB programmers still use VB6 or VBA. And it's that VBA component that is the key. Many who use VB don't "really" use VB at all. They use VBA, because they are not really interested in programming. They are interested in automating Office and other applications that house VBA. They are essentially business users who need enhanced macro capabilities. Personally, I wouldn't have a problem with Microsoft keeping VBA around as a macro tool. When they switched from WordBasic to VBA, it was quite an ordeal. But keeping VBA and promoting VB.NET are two different things. Like I said, if you (or anyone) were truly serious about the benefits of VB6 or VBA, you would do something about it from a business activity perspective. Anyone can gripe and moan and mock. Doing something positive about the situation would be something I could respect. Tell you what: If you agree to stop the bellyaching and instead come up with a serious business plan that engages the future of VB6/VBA, and dialog with Microsoft about it in a professional manner, I would be open to writing something (i.e., books or articles) for an enhanced Classic VB product. Other authors would do so as well. If you have a professional product with a viable future, then you will be able to post in the forums something that others will actually want to read. ----- Tim Patrick - www.timaki.com Start-to-Finish Visual Basic 2005 Show quoteHide quote > people like to use VB.net? > > ROFL > > what universe do you come from? > > show me some stats.. and I'll show you some stats that say '90% of vb > developers still use VB6' > > I would notify the folks at Monster.com and craigslist.org/job because > I sure don't see many VB.net _JOBS_ > > -Larry > > Tim Patrick wrote: > >> Except for item #d (which is just a side effect of your overall bad >> feeling), >> I fully understand your frustration. (By the way, >> "microsoft.com/vbasic" >> does go to the Visual Basic page; I agree that "microsoft.com/vb" >> should >> as well.) >> Concerning items #g through #i: I can tell you how to become rich >> beyond >> your wildest dreams. Start a company that fully supports those who >> wish to >> continue with VB6. Make a name for yourself, and then approach >> Microsoft >> about licensing the VB6 product and its source code for support and >> enhancement >> purposes. Everyone always says Microsoft only cares about money; go >> ahead >> and prove it. Convince them that it is in their financial best >> interest to >> allow your new company to extend Visual Basic Classic. >> You can draw a lot more flies with honey than you can with vinegar. >> Using the keyboard to constantly browbeat another product that, >> frankly, a lot of people actually like to use is insanity. These >> forums have no influence on Microsoft's business decisions. But a >> well-crafted business plan just might. >> >> ----- >> Tim Patrick - www.timaki.com >> Start-to-Finish Visual Basic 2005 >>> well... i'll make you a deal buddy >>> >>> when microsoft does this: >>> >>> a) microsoft.com/vb should GO SOMEWHERE >>> b) NO vs crashes in a month for me >>> c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net >>> d) vb newsgroup should be public.microsoft.vb.. not this >>> 'microsoft.public.dotnet.languages.vb' crap >>> e) it isn't verbose like 2002,2003,2005 >>> f) i can copy and paste datasets in SSRS in between reports >>> g) they support vb6 >>> h) they support developing new COM components >>> i) they support existing ActiveX controls >>> if all those come true; I might lay off... >>> but until then; their backwards ass crap; i've just about had enough >>> of it >>> >>> Tim Patrick wrote: >>> >>>> So when the next version of Visual Studio comes out and includes >>>> Visual Basic--and >>>> it will, since I've already tried out an early version of it--will >>>> you promise >>>> to leave these forums with the shame of a false prophet and never >>>> post again? >>>> One can only hope. I've seen movies of Nazi Germany.. does this mean that they are still
the most popular? I've seen movies of Nazi Germany.. does this mean that we should invade Russia? oh I saw three people; hudding in a corner once-- that liked VB.net SERIOUSLY BUD how are your VB.net books selling ROFL you do know it's not even called VB.net anymore? so why are we still posting in microsoft.public.dotnet.languages.vb Tim Patrick wrote: Show quoteHide quote > But I like VB.NET, and I know others who do as well. I've attended conferences > with hundreds of people who are as excited about it as I am. > > Your 90% statistic seems high, but I wouldn't doubt that well over 50% of > VB programmers still use VB6 or VBA. And it's that VBA component that is > the key. Many who use VB don't "really" use VB at all. They use VBA, because > they are not really interested in programming. They are interested in automating > Office and other applications that house VBA. They are essentially business > users who need enhanced macro capabilities. > > Personally, I wouldn't have a problem with Microsoft keeping VBA around as > a macro tool. When they switched from WordBasic to VBA, it was quite an ordeal. > But keeping VBA and promoting VB.NET are two different things. > > Like I said, if you (or anyone) were truly serious about the benefits of > VB6 or VBA, you would do something about it from a business activity perspective. > Anyone can gripe and moan and mock. Doing something positive about the situation > would be something I could respect. > > Tell you what: If you agree to stop the bellyaching and instead come up with > a serious business plan that engages the future of VB6/VBA, and dialog with > Microsoft about it in a professional manner, I would be open to writing something > (i.e., books or articles) for an enhanced Classic VB product. Other authors > would do so as well. If you have a professional product with a viable future, > then you will be able to post in the forums something that others will actually > want to read. > > ----- > Tim Patrick - www.timaki.com > Start-to-Finish Visual Basic 2005 > > > people like to use VB.net? > > > > ROFL > > > > what universe do you come from? > > > > show me some stats.. and I'll show you some stats that say '90% of vb > > developers still use VB6' > > > > I would notify the folks at Monster.com and craigslist.org/job because > > I sure don't see many VB.net _JOBS_ > > > > -Larry > > > > Tim Patrick wrote: > > > >> Except for item #d (which is just a side effect of your overall bad > >> feeling), > >> I fully understand your frustration. (By the way, > >> "microsoft.com/vbasic" > >> does go to the Visual Basic page; I agree that "microsoft.com/vb" > >> should > >> as well.) > >> Concerning items #g through #i: I can tell you how to become rich > >> beyond > >> your wildest dreams. Start a company that fully supports those who > >> wish to > >> continue with VB6. Make a name for yourself, and then approach > >> Microsoft > >> about licensing the VB6 product and its source code for support and > >> enhancement > >> purposes. Everyone always says Microsoft only cares about money; go > >> ahead > >> and prove it. Convince them that it is in their financial best > >> interest to > >> allow your new company to extend Visual Basic Classic. > >> You can draw a lot more flies with honey than you can with vinegar. > >> Using the keyboard to constantly browbeat another product that, > >> frankly, a lot of people actually like to use is insanity. These > >> forums have no influence on Microsoft's business decisions. But a > >> well-crafted business plan just might. > >> > >> ----- > >> Tim Patrick - www.timaki.com > >> Start-to-Finish Visual Basic 2005 > >>> well... i'll make you a deal buddy > >>> > >>> when microsoft does this: > >>> > >>> a) microsoft.com/vb should GO SOMEWHERE > >>> b) NO vs crashes in a month for me > >>> c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net > >>> d) vb newsgroup should be public.microsoft.vb.. not this > >>> 'microsoft.public.dotnet.languages.vb' crap > >>> e) it isn't verbose like 2002,2003,2005 > >>> f) i can copy and paste datasets in SSRS in between reports > >>> g) they support vb6 > >>> h) they support developing new COM components > >>> i) they support existing ActiveX controls > >>> if all those come true; I might lay off... > >>> but until then; their backwards ass crap; i've just about had enough > >>> of it > >>> > >>> Tim Patrick wrote: > >>> > >>>> So when the next version of Visual Studio comes out and includes > >>>> Visual Basic--and > >>>> it will, since I've already tried out an early version of it--will > >>>> you promise > >>>> to leave these forums with the shame of a false prophet and never > >>>> post again? > >>>> One can only hope. I have been informed by a headhunting agency that .Net
programmers have a 97.5% employment rate. That means there are only 2.5% unemployed, most of them by choice. Judging by the number of headhunters that continue to show up at my local .Net User Group meetings, I think your percentages are off, or a lot more VB6 programmers are going to move up to VB2005 to stay employed. Robin S. ---------------------------------------------- Show quoteHide quote "Larry Linson" <larrylinso***@hotmail.com> wrote in message news:1164649903.286926.246400@h54g2000cwb.googlegroups.com... > people like to use VB.net? > > ROFL > > what universe do you come from? > > show me some stats.. and I'll show you some stats that say '90% of vb > developers still use VB6' > > I would notify the folks at Monster.com and craigslist.org/job because > I sure don't see many VB.net _JOBS_ > > -Larry > > > Tim Patrick wrote: >> Except for item #d (which is just a side effect of your overall bad >> feeling), >> I fully understand your frustration. (By the way, "microsoft.com/vbasic" >> does go to the Visual Basic page; I agree that "microsoft.com/vb" should >> as well.) >> >> Concerning items #g through #i: I can tell you how to become rich beyond >> your wildest dreams. Start a company that fully supports those who wish >> to >> continue with VB6. Make a name for yourself, and then approach Microsoft >> about licensing the VB6 product and its source code for support and >> enhancement >> purposes. Everyone always says Microsoft only cares about money; go ahead >> and prove it. Convince them that it is in their financial best interest >> to >> allow your new company to extend Visual Basic Classic. >> >> You can draw a lot more flies with honey than you can with vinegar. Using >> the keyboard to constantly browbeat another product that, frankly, a lot >> of people actually like to use is insanity. These forums have no >> influence >> on Microsoft's business decisions. But a well-crafted business plan just >> might. >> >> ----- >> Tim Patrick - www.timaki.com >> Start-to-Finish Visual Basic 2005 >> >> > well... i'll make you a deal buddy >> > >> > when microsoft does this: >> > >> > a) microsoft.com/vb should GO SOMEWHERE >> > b) NO vs crashes in a month for me >> > c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net >> > d) vb newsgroup should be public.microsoft.vb.. not this >> > 'microsoft.public.dotnet.languages.vb' crap >> > e) it isn't verbose like 2002,2003,2005 >> > f) i can copy and paste datasets in SSRS in between reports >> > g) they support vb6 >> > h) they support developing new COM components >> > i) they support existing ActiveX controls >> > if all those come true; I might lay off... >> > >> > but until then; their backwards ass crap; i've just about had enough >> > of it >> > >> > Tim Patrick wrote: >> > >> >> So when the next version of Visual Studio comes out and includes >> >> Visual Basic--and >> >> it will, since I've already tried out an early version of it--will >> >> you promise >> >> to leave these forums with the shame of a false prophet and never >> >> post again? >> >> One can only hope. > dude that's the most ridiculous statistic I've ever heard of in my
life. I think that I could jam 98% of my cock in your mouth.. does that make you a girl? -Larry RobinS wrote: Show quoteHide quote > I have been informed by a headhunting agency that .Net > programmers have a 97.5% employment rate. That means > there are only 2.5% unemployed, most of them by choice. > Judging by the number of headhunters that continue to > show up at my local .Net User Group meetings, I think > your percentages are off, or a lot more VB6 programmers > are going to move up to VB2005 to stay employed. > > Robin S. > ---------------------------------------------- > > "Larry Linson" <larrylinso***@hotmail.com> wrote in message > news:1164649903.286926.246400@h54g2000cwb.googlegroups.com... > > people like to use VB.net? > > > > ROFL > > > > what universe do you come from? > > > > show me some stats.. and I'll show you some stats that say '90% of vb > > developers still use VB6' > > > > I would notify the folks at Monster.com and craigslist.org/job because > > I sure don't see many VB.net _JOBS_ > > > > -Larry > > > > > > Tim Patrick wrote: > >> Except for item #d (which is just a side effect of your overall bad > >> feeling), > >> I fully understand your frustration. (By the way, "microsoft.com/vbasic" > >> does go to the Visual Basic page; I agree that "microsoft.com/vb" should > >> as well.) > >> > >> Concerning items #g through #i: I can tell you how to become rich beyond > >> your wildest dreams. Start a company that fully supports those who wish > >> to > >> continue with VB6. Make a name for yourself, and then approach Microsoft > >> about licensing the VB6 product and its source code for support and > >> enhancement > >> purposes. Everyone always says Microsoft only cares about money; go ahead > >> and prove it. Convince them that it is in their financial best interest > >> to > >> allow your new company to extend Visual Basic Classic. > >> > >> You can draw a lot more flies with honey than you can with vinegar. Using > >> the keyboard to constantly browbeat another product that, frankly, a lot > >> of people actually like to use is insanity. These forums have no > >> influence > >> on Microsoft's business decisions. But a well-crafted business plan just > >> might. > >> > >> ----- > >> Tim Patrick - www.timaki.com > >> Start-to-Finish Visual Basic 2005 > >> > >> > well... i'll make you a deal buddy > >> > > >> > when microsoft does this: > >> > > >> > a) microsoft.com/vb should GO SOMEWHERE > >> > b) NO vs crashes in a month for me > >> > c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net > >> > d) vb newsgroup should be public.microsoft.vb.. not this > >> > 'microsoft.public.dotnet.languages.vb' crap > >> > e) it isn't verbose like 2002,2003,2005 > >> > f) i can copy and paste datasets in SSRS in between reports > >> > g) they support vb6 > >> > h) they support developing new COM components > >> > i) they support existing ActiveX controls > >> > if all those come true; I might lay off... > >> > > >> > but until then; their backwards ass crap; i've just about had enough > >> > of it > >> > > >> > Tim Patrick wrote: > >> > > >> >> So when the next version of Visual Studio comes out and includes > >> >> Visual Basic--and > >> >> it will, since I've already tried out an early version of it--will > >> >> you promise > >> >> to leave these forums with the shame of a false prophet and never > >> >> post again? > >> >> One can only hope. > > The agency who gave me that information provides employment
statistics to the government, who in turn use it in government reports. As for the second part, it doesn't surprise me that your personal parts are so small. It explains what you're trying to make up for by being a bully. Have a nice day! Robin S. ----------------------------------------------- Show quoteHide quote "Larry Linson" <larrylinso***@hotmail.com> wrote in message news:1164919508.410645.235440@16g2000cwy.googlegroups.com... > dude that's the most ridiculous statistic I've ever heard of in my > life. > > I think that I could jam 98% of my cock in your mouth.. does that make > you a girl? > > -Larry > > > > > > > > RobinS wrote: >> I have been informed by a headhunting agency that .Net >> programmers have a 97.5% employment rate. That means >> there are only 2.5% unemployed, most of them by choice. >> Judging by the number of headhunters that continue to >> show up at my local .Net User Group meetings, I think >> your percentages are off, or a lot more VB6 programmers >> are going to move up to VB2005 to stay employed. >> >> Robin S. >> ---------------------------------------------- >> >> "Larry Linson" <larrylinso***@hotmail.com> wrote in message >> news:1164649903.286926.246400@h54g2000cwb.googlegroups.com... >> > people like to use VB.net? >> > >> > ROFL >> > >> > what universe do you come from? >> > >> > show me some stats.. and I'll show you some stats that say '90% of vb >> > developers still use VB6' >> > >> > I would notify the folks at Monster.com and craigslist.org/job because >> > I sure don't see many VB.net _JOBS_ >> > >> > -Larry >> > >> > >> > Tim Patrick wrote: >> >> Except for item #d (which is just a side effect of your overall bad >> >> feeling), >> >> I fully understand your frustration. (By the way, >> >> "microsoft.com/vbasic" >> >> does go to the Visual Basic page; I agree that "microsoft.com/vb" >> >> should >> >> as well.) >> >> >> >> Concerning items #g through #i: I can tell you how to become rich >> >> beyond >> >> your wildest dreams. Start a company that fully supports those who >> >> wish >> >> to >> >> continue with VB6. Make a name for yourself, and then approach >> >> Microsoft >> >> about licensing the VB6 product and its source code for support and >> >> enhancement >> >> purposes. Everyone always says Microsoft only cares about money; go >> >> ahead >> >> and prove it. Convince them that it is in their financial best >> >> interest >> >> to >> >> allow your new company to extend Visual Basic Classic. >> >> >> >> You can draw a lot more flies with honey than you can with vinegar. >> >> Using >> >> the keyboard to constantly browbeat another product that, frankly, a >> >> lot >> >> of people actually like to use is insanity. These forums have no >> >> influence >> >> on Microsoft's business decisions. But a well-crafted business plan >> >> just >> >> might. >> >> >> >> ----- >> >> Tim Patrick - www.timaki.com >> >> Start-to-Finish Visual Basic 2005 >> >> >> >> > well... i'll make you a deal buddy >> >> > >> >> > when microsoft does this: >> >> > >> >> > a) microsoft.com/vb should GO SOMEWHERE >> >> > b) NO vs crashes in a month for me >> >> > c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net >> >> > d) vb newsgroup should be public.microsoft.vb.. not this >> >> > 'microsoft.public.dotnet.languages.vb' crap >> >> > e) it isn't verbose like 2002,2003,2005 >> >> > f) i can copy and paste datasets in SSRS in between reports >> >> > g) they support vb6 >> >> > h) they support developing new COM components >> >> > i) they support existing ActiveX controls >> >> > if all those come true; I might lay off... >> >> > >> >> > but until then; their backwards ass crap; i've just about had enough >> >> > of it >> >> > >> >> > Tim Patrick wrote: >> >> > >> >> >> So when the next version of Visual Studio comes out and includes >> >> >> Visual Basic--and >> >> >> it will, since I've already tried out an early version of it--will >> >> >> you promise >> >> >> to leave these forums with the shame of a false prophet and never >> >> >> post again? >> >> >> One can only hope. >> > > I'm not a bully, I am the savior of the unclean; I am the great eraser
I speak the truth. VB.net is going away it is now called VB 2005 ROFL -Larry Linson JR RobinS wrote: Show quoteHide quote > The agency who gave me that information provides employment > statistics to the government, who in turn use it in government > reports. > > As for the second part, it doesn't surprise me that your personal > parts are so small. It explains what you're trying to make up for > by being a bully. > > Have a nice day! > Robin S. > > ----------------------------------------------- > > "Larry Linson" <larrylinso***@hotmail.com> wrote in message > news:1164919508.410645.235440@16g2000cwy.googlegroups.com... > > dude that's the most ridiculous statistic I've ever heard of in my > > life. > > > > I think that I could jam 98% of my cock in your mouth.. does that make > > you a girl? > > > > -Larry > > > > > > > > > > > > > > > > RobinS wrote: > >> I have been informed by a headhunting agency that .Net > >> programmers have a 97.5% employment rate. That means > >> there are only 2.5% unemployed, most of them by choice. > >> Judging by the number of headhunters that continue to > >> show up at my local .Net User Group meetings, I think > >> your percentages are off, or a lot more VB6 programmers > >> are going to move up to VB2005 to stay employed. > >> > >> Robin S. > >> ---------------------------------------------- > >> > >> "Larry Linson" <larrylinso***@hotmail.com> wrote in message > >> news:1164649903.286926.246400@h54g2000cwb.googlegroups.com... > >> > people like to use VB.net? > >> > > >> > ROFL > >> > > >> > what universe do you come from? > >> > > >> > show me some stats.. and I'll show you some stats that say '90% of vb > >> > developers still use VB6' > >> > > >> > I would notify the folks at Monster.com and craigslist.org/job because > >> > I sure don't see many VB.net _JOBS_ > >> > > >> > -Larry > >> > > >> > > >> > Tim Patrick wrote: > >> >> Except for item #d (which is just a side effect of your overall bad > >> >> feeling), > >> >> I fully understand your frustration. (By the way, > >> >> "microsoft.com/vbasic" > >> >> does go to the Visual Basic page; I agree that "microsoft.com/vb" > >> >> should > >> >> as well.) > >> >> > >> >> Concerning items #g through #i: I can tell you how to become rich > >> >> beyond > >> >> your wildest dreams. Start a company that fully supports those who > >> >> wish > >> >> to > >> >> continue with VB6. Make a name for yourself, and then approach > >> >> Microsoft > >> >> about licensing the VB6 product and its source code for support and > >> >> enhancement > >> >> purposes. Everyone always says Microsoft only cares about money; go > >> >> ahead > >> >> and prove it. Convince them that it is in their financial best > >> >> interest > >> >> to > >> >> allow your new company to extend Visual Basic Classic. > >> >> > >> >> You can draw a lot more flies with honey than you can with vinegar. > >> >> Using > >> >> the keyboard to constantly browbeat another product that, frankly, a > >> >> lot > >> >> of people actually like to use is insanity. These forums have no > >> >> influence > >> >> on Microsoft's business decisions. But a well-crafted business plan > >> >> just > >> >> might. > >> >> > >> >> ----- > >> >> Tim Patrick - www.timaki.com > >> >> Start-to-Finish Visual Basic 2005 > >> >> > >> >> > well... i'll make you a deal buddy > >> >> > > >> >> > when microsoft does this: > >> >> > > >> >> > a) microsoft.com/vb should GO SOMEWHERE > >> >> > b) NO vs crashes in a month for me > >> >> > c) _EVERY_SINGLE_PROGRAMMING_EXAMPLE_ is in both C# and VB.net > >> >> > d) vb newsgroup should be public.microsoft.vb.. not this > >> >> > 'microsoft.public.dotnet.languages.vb' crap > >> >> > e) it isn't verbose like 2002,2003,2005 > >> >> > f) i can copy and paste datasets in SSRS in between reports > >> >> > g) they support vb6 > >> >> > h) they support developing new COM components > >> >> > i) they support existing ActiveX controls > >> >> > if all those come true; I might lay off... > >> >> > > >> >> > but until then; their backwards ass crap; i've just about had enough > >> >> > of it > >> >> > > >> >> > Tim Patrick wrote: > >> >> > > >> >> >> So when the next version of Visual Studio comes out and includes > >> >> >> Visual Basic--and > >> >> >> it will, since I've already tried out an early version of it--will > >> >> >> you promise > >> >> >> to leave these forums with the shame of a false prophet and never > >> >> >> post again? > >> >> >> One can only hope. > >> > > >
listbox's SelectedIndexChanged keep fire
Array Question, Out of Bounds how to save the textbox contents to sql server database Not understanding simple concept Newbie Display Outlook Recipient Window from vb.net Errors when running from LAN server. Form level focus monitor using file system in web site Setting Time property |
|||||||||||||||||||||||