Visual Basic .NET Forums  
Click here to advertise with us

Go Back   Visual Basic .NET Forums > Visual Studio .NET > IDE

IDE Anything concerning the Visual Studio IDE

VB.NET Forums Newsletter Signup:
Email address:


Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-03-2009, 6:43 AM
VB.NET Forum Enthusiast
.NET Framework: .NET 3.0 (VS 2005/2008)
 
Join Date: May 2008
Location: Spain
Posts: 82
Reputation: 25
J Trahair is on a distinguished programming path ahead
Default Find And Replace in VB2005 compared to VB6

First, apologies if you've 'done' comparisons with VB6, but some of us are just catching up.

The behaviour of the 'Find And Replace' tool (VB2005): in old VB6, if I want to find all occurrences of (for example)
HTML Code:
mstrThisString = ""
in all forms, it would start somewhere and go through until the whole project had been searched. If you stopped the Find to change something, it would start afresh from that point and search through the project normally,without repeating or back-tracking.

In VB2005, if you stop the Find in (for example) the frmInvoicing form at the fifth occurrence to change something, what happens is this:
you restart the Find cycle, you're in frmInvoicing at the fifth occurrence, so it finds occurrences 6 then 7 (the last in this form), then starts again at the top of frmInvoicing!!. I'd expect to move to the next form. Consequently I don't know where I am.

Is there a setting I can change to improve this?

Thank you.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 07-03-2009, 7:08 AM
Robert_Zenz's Avatar
VB.NET Forum Idol
.NET Framework: .NET 2.0
 
Join Date: Jun 2008
Location: Vienna, Austria
Age: 22
Posts: 503
Reputation: 289
Robert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NETRobert_Zenz master of VB.NET
Default

Ahm...the dialog has a combobox on it labeled 'Look in', which does change this behaviour.

Bobby
__________________
Don't give TypeCasting Errors a chance, turn ON Option Strict!
Greatest Obfuscator ever: EazFuscator (Freeware)
Greatest Reflection Tool ever: .NET Reflector (Freeware) with Add-Ins
Greatest Introspection Tool ever: Gendarme (GPL)
Greatest MySQL FrontEnd ever: MySQL-Front (Shareware), HeidiSQL (GPL)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 07-03-2009, 8:22 AM
VB.NET Forum Enthusiast
.NET Framework: .NET 3.0 (VS 2005/2008)
 
Join Date: May 2008
Location: Spain
Posts: 82
Reputation: 25
J Trahair is on a distinguished programming path ahead
Default

Yes, I know about the Look In combobox. Whichever setting the Look In is set to (in my example it was Entire Solution), the behaviour of the Find routine is less than predictable, and certainly not what VB6 does.

Perhaps this is another of Microsoft's improvements that I shall have to live with.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 07-06-2009, 4:45 AM
jmcilhinney's Avatar
VB.NET Forum Moderator
.NET Framework: .NET 3.5 (VS 2008)
 
Join Date: Aug 2004
Location: Sydney, Australia
Age: 40
Posts: 6,006
Reputation: 538
jmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalistjmcilhinney VB.NET gold medalist
Default

Quote:
Originally Posted by J Trahair View Post
Yes, I know about the Look In combobox. Whichever setting the Look In is set to (in my example it was Entire Solution), the behaviour of the Find routine is less than predictable, and certainly not what VB6 does.

Perhaps this is another of Microsoft's improvements that I shall have to live with.
The fact that the behaviour of the Find & Replace tool is not what you're used to does not mean that it's unpredictable. It's completely predictable. Personally, I find the current implementation more sensible than what you're describing, although that doesn't mean what was was wrong. That said, if you change what you're looking for then it makes sense to treat it as a new search and ignore whatever went before. Whatever seems more intuitive to the individual, what is is and, as far as I can see, there's no way to make VS.NET behave the way you describe.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





All times are GMT -4. The time now is 1:10 PM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.3.2


For advertising opportunities click here.