| Groups | Blog | Home |
vb.net : Capitalize Variable Names
When I type a variable name that already has been Dim'd, The IDE doesn't make the variable name Capitalized, even though the variable name definition in the Dim is capitalized. VB 6 will do this. Where is the setting so that this will happen. Someone else here at work uses VB.Net 2003, and his IDE does capitalize variables. Thanks in Advance,
[quoted text, click to view] "Larry" <bliff@Blifff.com> wrote in message news:OpCzRY6UGHA.5172@TK2MSFTNGP12.phx.gbl... > I am using VB.Net 2003, IDE. > > When I type a variable name that already has been Dim'd, > The IDE doesn't make the variable name Capitalized, > even though the variable name definition in the Dim is capitalized. > > VB 6 will do this. > > Where is the setting so that this will happen. Someone else here at work > uses VB.Net 2003, and his IDE does capitalize variables. Have you got Option Explicit on?
Hello, Larry,
It's nested fairly deeply. Select "Options" from the "Tools" menu. Then choose the "Text Editor" folder and under that the "Basic" sub-folder. In there, choose the "VB Specific" entry and look at the setting of the "Pretty Listing" check box. My recollection is that this setting also affects a number of other formatting related items. It took me a while to get used to them. But the only one that I still object to is the way it insists on repositioning comments that follow an in-line "If" statement. Cheers, Randy [quoted text, click to view] Larry wrote:
> I am using VB.Net 2003, IDE. > > When I type a variable name that already has been Dim'd, > The IDE doesn't make the variable name Capitalized, > even though the variable name definition in the Dim is capitalized. > > VB 6 will do this. > > Where is the setting so that this will happen. Someone else here at work > uses VB.Net 2003, and his IDE does capitalize variables. > > Thanks in Advance, >
[quoted text, click to view]
On Thu, 30 Mar 2006 03:14:10 -0500, "CMM" <cmm@nospam.com> wrote: >I have noticed this as well. "Auto-recognition" of declared variables has >been made stupider in VS2005. It worked great in VS2003. Option Strict and >Explicit all on here. I notice it all the time... but never bothered to >figure out why. > >I pretend "I didn't just see that".... considering this worked and has been >working great in VB for TEN years. And, now it doesn't. I haven't noticed it. I declare a variable with a certain case. Later on I use the variable using all lower case and when I leave the line
I have noticed this as well. "Auto-recognition" of declared variables has
been made stupider in VS2005. It worked great in VS2003. Option Strict and Explicit all on here. I notice it all the time... but never bothered to figure out why. I pretend "I didn't just see that".... considering this worked and has been working great in VB for TEN years. And, now it doesn't. -- -C. Moya www.cmoya.com [quoted text, click to view] "R. MacDonald" <scitec@NO-SP-AMcips.ca> wrote in message news:442b81e7$0$6030$dbd41001@news.wanadoo.nl... > Hello, Larry, > > It's nested fairly deeply. Select "Options" from the "Tools" menu. Then > choose the "Text Editor" folder and under that the "Basic" sub-folder. In > there, choose the "VB Specific" entry and look at the setting of the > "Pretty Listing" check box. > > My recollection is that this setting also affects a number of other > formatting related items. It took me a while to get used to them. But > the only one that I still object to is the way it insists on repositioning > comments that follow an in-line "If" statement. > > Cheers, > Randy > > > Larry wrote: >> I am using VB.Net 2003, IDE. >> >> When I type a variable name that already has been Dim'd, >> The IDE doesn't make the variable name Capitalized, >> even though the variable name definition in the Dim is capitalized. >> >> VB 6 will do this. >> >> Where is the setting so that this will happen. Someone else here at work >> uses VB.Net 2003, and his IDE does capitalize variables. >> >> Thanks in Advance, >> >> Larry
Hi Larry,
Usually VS does correct the case, but sometimes it "forgets". In such cases, just choose Edit -> Advanced -> Format Document, and that should correct it. Sometimes, saving the code also corrects the case. HTH, Regards, Cerebrus.
And a shortcut for that is Ctrl-K Ctrl-D
I tried it on and off, it didn't seem to make any difference.
[quoted text, click to view] Homer J Simpson wrote:
> "Larry" <bliff@Blifff.com> wrote in message > news:OpCzRY6UGHA.5172@TK2MSFTNGP12.phx.gbl... > >> I am using VB.Net 2003, IDE. >> >> When I type a variable name that already has been Dim'd, >> The IDE doesn't make the variable name Capitalized, >> even though the variable name definition in the Dim is capitalized. >> >> VB 6 will do this. >> >> Where is the setting so that this will happen. Someone else here at work >> uses VB.Net 2003, and his IDE does capitalize variables. > > Have you got Option Explicit on? > >
I have Whidbey (2005) on my another machine here at work,
and seems to work fine in regards to this issue. [quoted text, click to view] CMM wrote:
> I have noticed this as well. "Auto-recognition" of declared variables has > been made stupider in VS2005. It worked great in VS2003. Option Strict and > Explicit all on here. I notice it all the time... but never bothered to > figure out why. > > I pretend "I didn't just see that".... considering this worked and has been > working great in VB for TEN years. And, now it doesn't.
That did it, Thank You Randy.
[quoted text, click to view] R. MacDonald wrote:
> Hello, Larry, > > It's nested fairly deeply. Select "Options" from the "Tools" menu. Then > choose the "Text Editor" folder and under that the "Basic" sub-folder. > In there, choose the "VB Specific" entry and look at the setting of the > "Pretty Listing" check box. > > My recollection is that this setting also affects a number of other > formatting related items. It took me a while to get used to them. But > the only one that I still object to is the way it insists on > repositioning comments that follow an in-line "If" statement. > > Cheers, > Randy > > > Larry wrote: >> I am using VB.Net 2003, IDE. >> >> When I type a variable name that already has been Dim'd, >> The IDE doesn't make the variable name Capitalized, >> even though the variable name definition in the Dim is capitalized. >> >> VB 6 will do this. >> >> Where is the setting so that this will happen. Someone else here at work >> uses VB.Net 2003, and his IDE does capitalize variables. >> >> Thanks in Advance, >>
I wholeheartedly agree.
-- -C. Moya www.cmoya.com [quoted text, click to view] "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message news:OeV0ceAVGHA.4864@TK2MSFTNGP12.phx.gbl... > "Cerebrus" <zorg007@sify.com> schrieb: >> Usually VS does correct the case, but sometimes it "forgets". In such >> cases, just choose Edit -> Advanced -> Format Document, and that should >> correct it. Sometimes, saving the code also corrects the case. > > I've never needed this command in VB6, VB.NET 2002/2003. This is clearly > a bug that needs to be fixed! > > -- > M S Herfried K. Wagner > M V P <URL:http://dotnet.mvps.org/> > V B <URL:http://classicvb.org/petition/>
Hi Herfried,
I rarely need it too, (working in VS 2002/2003), but it occasionally happens when system memory is running low, and intellisense is taking its time to be intelligent. In those times, I just save all work, and run the Format command. Seems to work for me... Though I hope VS 2005 is much better in all respects. Through another recent post, I have come to know that VS 2005 is really slow except on very high config machines. Was quite disheartened to hear that. Regards, Cerebrus.
[quoted text, click to view]
> but just how much /more/ processing power is that going to chew up? :-) Considering it worked just fine on a 486 DX-66 and Pentium 60 back in 1994, I can't see why it should be a big deal today. -- -C. Moya www.cmoya.com [quoted text, click to view] "Phill W." <p-.a-.w-a-r-d@o-p-e-n.a-c.u-k> wrote in message news:e0gut2$hff$1@yarrow.open.ac.uk... > "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message > news:OeV0ceAVGHA.4864@TK2MSFTNGP12.phx.gbl... >> "Cerebrus" <zorg007@sify.com> schrieb: >>> Usually VS does correct the case, but sometimes it "forgets". In such >>> cases, just choose Edit -> Advanced -> Format Document, and that should >>> correct it. Sometimes, saving the code also corrects the case. >> >> I've never needed this command in VB6, VB.NET 2002/2003. This is clearly >> a bug that needs to be fixed! > > Agreed, > > but just how much /more/ processing power is that going to chew up? :-) > > [Option Paranoia On] > Or, perhaps, this is the Thin End of the Wedge that will finally make VB > a Case-Sensitive language ... > > ;-)) > > (I hope ...) > > Regards, > Phill W. > >
[quoted text, click to view]
>> I've convinced myself that VS is doing "lots of important stuff in the background >> becuase it's so great." He he, that's a nice way to think of it ! I guess I will have to wait before I can afford to buy a "top-of-the-line" PC, before I touch VS 2005. Regards, Cerebrus.
I think the background thread(s) that interpret code on-the-fly (whether it
be a compiler or just formatter) is not optimized at all.... especially in VS2005... and especially in ASP.NET. For instance, often on a WebForm of any moderate complexity it takes the Property Editor 3 seconds to catch up after you select a control on the form..... and that's on my top-of-the line (at least as of 5 months ago... before Duo) P-M-2Ghz (equiv of a 3.4 P4 but without HT) with 2GB of RAM. Scrolling around using the arrow keys is often a painful experience. I've gotten used to it though... and it doesn't bother me much nowadays. I've convinced myself that VS is doing "lots of important stuff in the background becuase it's so great." -- -C. Moya www.cmoya.com [quoted text, click to view] "Cerebrus" <zorg007@sify.com> wrote in message news:1143743932.452031.298690@i39g2000cwa.googlegroups.com... > Hi Herfried, > > I rarely need it too, (working in VS 2002/2003), but it occasionally > happens when system memory is running low, and intellisense is taking > its time to be intelligent. In those times, I just save all work, and > run the Format command. Seems to work for me... > > Though I hope VS 2005 is much better in all respects. Through another > recent post, I have come to know that VS 2005 is really slow except on > very high config machines. Was quite disheartened to hear that. > > Regards, > > Cerebrus. >
"CMM" <cmm@nospam.com> schrieb:
[quoted text, click to view] >I have noticed this as well. "Auto-recognition" of declared variables has >been made stupider in VS2005. It worked great in VS2003. Option Strict and >Explicit all on here. I notice it all the time... but never bothered to >figure out why. Same here. Sometimes VB 2005 doesn't automatically correct capitalization :-(((. -- M S Herfried K. Wagner M V P <URL:http://dotnet.mvps.org/> V B <URL:http://classicvb.org/petition/>
"Cerebrus" <zorg007@sify.com> schrieb:
[quoted text, click to view] > Usually VS does correct the case, but sometimes it "forgets". In such > cases, just choose Edit -> Advanced -> Format Document, and that should > correct it. Sometimes, saving the code also corrects the case. I've never needed this command in VB6, VB.NET 2002/2003. This is clearly a bug that needs to be fixed! -- M S Herfried K. Wagner M V P <URL:http://dotnet.mvps.org/> V B <URL:http://classicvb.org/petition/>
[quoted text, click to view]
"Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message news:OeV0ceAVGHA.4864@TK2MSFTNGP12.phx.gbl... > "Cerebrus" <zorg007@sify.com> schrieb: >> Usually VS does correct the case, but sometimes it "forgets". In such >> cases, just choose Edit -> Advanced -> Format Document, and that should >> correct it. Sometimes, saving the code also corrects the case. > > I've never needed this command in VB6, VB.NET 2002/2003. This is clearly > a bug that needs to be fixed! Agreed, but just how much /more/ processing power is that going to chew up? :-) [Option Paranoia On] Or, perhaps, this is the Thin End of the Wedge that will finally make VB a Case-Sensitive language ... ;-)) (I hope ...) Regards, Phill W.
[quoted text, click to view] "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message news:OeV0ceAVGHA.4864@TK2MSFTNGP12.phx.gbl... > "Cerebrus" <zorg007@sify.com> schrieb: >> Usually VS does correct the case, but sometimes it "forgets". In such >> cases, just choose Edit -> Advanced -> Format Document, and that should >> correct it. Sometimes, saving the code also corrects the case. > > I've never needed this command in VB6, VB.NET 2002/2003. This is clearly > a bug that needs to be fixed! And unless it's hidden, it's not in VB Express!
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
| home · blog · groups | Questions? Comments? Contact the dn |