No equivalent control

29 Aug 2006 8:41 PM

Al

VB6 is not supported or its support will be discontinued - I hear that
pretty often.
For VB 2005 development some controls from VB6 have no equivalent, for
instance DriveListBox and DirListBox.
MSDN says that OpenFileDialog and SaveFileDialog (.Net components) have all
the features to open or save the file.
Or DriveListBox and DirListBox can be used via
Microsoft.VisualBasic.Compatibility library.

I have 2 question:
1. If I use Microsoft.VisualBasic.Compatibility approach, what will happen
when VB6 will be discontinued totally? Will be
Microsoft.VisualBasic.Compatibility library discontinued as well? Or it's
independant from VB6 stuff and will be alive until something new comes?

2. If I use OpenFileDialog and SaveFileDialog then how do I make them work
as old DriveListBox and DirListBox worked, i.e. they are displayed on the
screen initially, not after click on the button or something like that?

Al

30 Aug 2006 3:04 AM

Mike McIntyre

There is an example - Doc Browser Form - in the Visual Basic Power Pack from
Got Dot Net that may meet your requirements.

The Power Pack can be downloaded at:
http://www.gotdotnet.com/workspaces/workspace.aspx?id=167542e0-e435-4585-ae4f-c111fe60ed58

--
Mike

Mike McIntyre [MVP]
http://www.getdotnetcode.com

Show quoteHide quote

"Al" <a*@newsgroups.com> wrote in message
news:uujHPu6yGHA.4396@TK2MSFTNGP04.phx.gbl...
> VB6 is not supported or its support will be discontinued - I hear that
> pretty often.
> For VB 2005 development some controls from VB6 have no equivalent, for
> instance DriveListBox and DirListBox.
> MSDN says that OpenFileDialog and SaveFileDialog (.Net components) have
> all the features to open or save the file.
> Or DriveListBox and DirListBox can be used via
> Microsoft.VisualBasic.Compatibility library.
>
> I have 2 question:
> 1. If I use Microsoft.VisualBasic.Compatibility approach, what will happen
> when VB6 will be discontinued totally? Will be
> Microsoft.VisualBasic.Compatibility library discontinued as well? Or it's
> independant from VB6 stuff and will be alive until something new comes?
>
> 2. If I use OpenFileDialog and SaveFileDialog then how do I make them work
> as old DriveListBox and DirListBox worked, i.e. they are displayed on the
> screen initially, not after click on the button or something like that?
>
> Al
>
>
>
>

30 Aug 2006 7:08 PM

Theo Verweij

The way I see it, is that you can use the compatibility assembly to
convert your projects without a lot of recoding.

After you have a stable release, you can replace the code that depends
on this assembly. You don't have to do this during the conversion
process, so this process will be easier.

But, in the end I think it is best to remove all depedencies to it.

Al wrote:
Show quoteHide quote

> VB6 is not supported or its support will be discontinued - I hear that
> pretty often.
> For VB 2005 development some controls from VB6 have no equivalent, for
> instance DriveListBox and DirListBox.
> MSDN says that OpenFileDialog and SaveFileDialog (.Net components) have all
> the features to open or save the file.
> Or DriveListBox and DirListBox can be used via
> Microsoft.VisualBasic.Compatibility library.
>
> I have 2 question:
> 1. If I use Microsoft.VisualBasic.Compatibility approach, what will happen
> when VB6 will be discontinued totally? Will be
> Microsoft.VisualBasic.Compatibility library discontinued as well? Or it's
> independant from VB6 stuff and will be alive until something new comes?
>
> 2. If I use OpenFileDialog and SaveFileDialog then how do I make them work
> as old DriveListBox and DirListBox worked, i.e. they are displayed on the
> screen initially, not after click on the button or something like that?
>
> Al
>
>
>
>