I download a couple of controls that look VERY interesting--but they are for
VB6.

When I look through MSVS's help, all I can find on the subject tells that
their is a compatiblity library and what it's purpose is. But can't seem to
find anything on HOW to access it.

Any ideas?

TIA

If you have used previous versions of Visual Basic, you will notice that
Visual Basic .NET introduces several changes to the Visual Basic language
and that some familiar functions have seemingly disappeared. These changes
were necessary in order to make Visual Basic compliant with the .NET
Platform and the common language specification (CLS).

When a Visual Basic 6.0 application is upgraded to Visual Basic .NET, the
conversion of some code is impossible due to syntactical or architectural
differences. For this reason, functions in the Visual Basic 6.0
Compatibility library (Microsoft.VisualBasic.Compatibility) are used to
allow the code to run in Visual Basic .NET without the need for extensive
modification. These functions mimic Visual Basic 6.0 behavior while
remaining compliant with the common language specification.

Caution Functions in the Visual Basic 6.0 Compatibility library are
provided only for use by the upgrading tools. Although it is possible to use
this library when writing new code, there is no guarantee that it will be
supported in future versions of Visual Basic.
See Also

--

RDI

(remove the exclamation from the email address)

I was able to find a walk-through for upgrading VB6 app to VB.Net. BUT--it
requires VB6 be installed on my PC.

UGH! If I had VB6, I wouldn't need to upgrade!

--

RDI

(remove the exclamation from the email address)

"RDI" <RDI!@!WriteMe.com> wrote in message
news:(E-Mail Removed)...
> I download a couple of controls that look VERY interesting--but they are
for
> VB6.
>
> When I look through MSVS's help, all I can find on the subject tells that
> their is a compatiblity library and what it's purpose is. But can't seem
to
> find anything on HOW to access it.
>
> Any ideas?
>
> TIA
>
> If you have used previous versions of Visual Basic, you will notice that
> Visual Basic .NET introduces several changes to the Visual Basic language
> and that some familiar functions have seemingly disappeared. These changes
> were necessary in order to make Visual Basic compliant with the .NET
> Platform and the common language specification (CLS).
>
> When a Visual Basic 6.0 application is upgraded to Visual Basic .NET, the
> conversion of some code is impossible due to syntactical or architectural
> differences. For this reason, functions in the Visual Basic 6.0
> Compatibility library (Microsoft.VisualBasic.Compatibility) are used to
> allow the code to run in Visual Basic .NET without the need for extensive
> modification. These functions mimic Visual Basic 6.0 behavior while
> remaining compliant with the common language specification.
>
> Caution Functions in the Visual Basic 6.0 Compatibility library are
> provided only for use by the upgrading tools. Although it is possible to
use
> this library when writing new code, there is no guarantee that it will be
> supported in future versions of Visual Basic.
> See Also
>
> --
>
> RDI
>
> (remove the exclamation from the email address)
>
>

"RDI" <RDI!@!WriteMe.com> schrieb
> I was able to find a walk-through for upgrading VB6 app to VB.Net.
> BUT--it requires VB6 be installed on my PC.
>
> UGH! If I had VB6, I wouldn't need to upgrade!


If you don't have VB6, you won't have projects to upgrade. ;-) Kidding
only, I know you have the source from somewhere else.

I think some minimum requirements must be met to be able to upgrade a
project. I'm not sure whether VB6 really needs to be installed, but I think
that projects are obviously not upgradable if referenced COM-libraries are
missing.

Concerning the compatibility library: Has it really not been installed if
VB6 was not installed at the time you installed VB/VS.NET? In the "add
reference" dialog, there is no "Microsoft Visual Basic .NET compatibility
runtime"?


--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

* "RDI" <RDI!@!WriteMe.com> scripsit:
> I was able to find a walk-through for upgrading VB6 app to VB.Net. BUT--it
> requires VB6 be installed on my PC.
>
> UGH! If I had VB6, I wouldn't need to upgrade!

Forget the updrade wizard. You application will still use old
ActiveX components even if there is a managed replacement in the
framework available.

;->

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

I found a "Microsoft Visual Basic.Net Runtime" but no "Microsoft Visual
Basic.Net Compatibility Runtime".

TIA

--

RDI

(remove the exclamation from the email address)

"Armin Zingler" <(E-Mail Removed)> wrote in message
news:OlR$aK%(E-Mail Removed)...
> "RDI" <RDI!@!WriteMe.com> schrieb
> > I was able to find a walk-through for upgrading VB6 app to VB.Net.
> > BUT--it requires VB6 be installed on my PC.
> >
> > UGH! If I had VB6, I wouldn't need to upgrade!
>
>
> If you don't have VB6, you won't have projects to upgrade. ;-) Kidding
> only, I know you have the source from somewhere else.
>
> I think some minimum requirements must be met to be able to upgrade a
> project. I'm not sure whether VB6 really needs to be installed, but I
think
> that projects are obviously not upgradable if referenced COM-libraries are
> missing.
>
> Concerning the compatibility library: Has it really not been installed if
> VB6 was not installed at the time you installed VB/VS.NET? In the "add
> reference" dialog, there is no "Microsoft Visual Basic .NET compatibility
> runtime"?
>
>
> --
> Armin
>
> http://www.plig.net/nnq/nquote.html
> http://www.netmeister.org/news/learn2quote.html
>

I don't think it's using any ActiveX components.

Thanks.

--

RDI

(remove the exclamation from the email address)

"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> * "RDI" <RDI!@!WriteMe.com> scripsit:
> > I was able to find a walk-through for upgrading VB6 app to VB.Net.
BUT--it
> > requires VB6 be installed on my PC.
> >
> > UGH! If I had VB6, I wouldn't need to upgrade!
>
> Forget the updrade wizard. You application will still use old
> ActiveX components even if there is a managed replacement in the
> framework available.
>
> ;->
>
> --
> Herfried K. Wagner [MVP]
> <http://www.mvps.org/dotnet>

I do have the runtime and design time references and all the source code. I
just don't have a compiled version--which if I DID have, I assume (HOPE) I
would be able to include as a reference somehow.

--

RDI

(remove the exclamation from the email address)

"Armin Zingler" <(E-Mail Removed)> wrote in message
news:OlR$aK%(E-Mail Removed)...
> "RDI" <RDI!@!WriteMe.com> schrieb
> > I was able to find a walk-through for upgrading VB6 app to VB.Net.
> > BUT--it requires VB6 be installed on my PC.
> >
> > UGH! If I had VB6, I wouldn't need to upgrade!
>
>
> If you don't have VB6, you won't have projects to upgrade. ;-) Kidding
> only, I know you have the source from somewhere else.
>
> I think some minimum requirements must be met to be able to upgrade a
> project. I'm not sure whether VB6 really needs to be installed, but I
think
> that projects are obviously not upgradable if referenced COM-libraries are
> missing.
>
> Concerning the compatibility library: Has it really not been installed if
> VB6 was not installed at the time you installed VB/VS.NET? In the "add
> reference" dialog, there is no "Microsoft Visual Basic .NET compatibility
> runtime"?
>
>
> --
> Armin
>
> http://www.plig.net/nnq/nquote.html
> http://www.netmeister.org/news/learn2quote.html
>

Also, this is the control I'm after (you posted a link to it in another
thread).

http://www.vbaccelerator.com/home/VB...logs/index.asp

TIA

--

RDI

(remove the exclamation from the email address)

"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> * "RDI" <RDI!@!WriteMe.com> scripsit:
> > I was able to find a walk-through for upgrading VB6 app to VB.Net.
BUT--it
> > requires VB6 be installed on my PC.
> >
> > UGH! If I had VB6, I wouldn't need to upgrade!
>
> Forget the updrade wizard. You application will still use old
> ActiveX components even if there is a managed replacement in the
> framework available.
>
> ;->
>
> --
> Herfried K. Wagner [MVP]
> <http://www.mvps.org/dotnet>

"RDI" <RDI!@!WriteMe.com> schrieb
> I was able to find a walk-through for upgrading VB6 app to VB.Net.
> BUT--it requires VB6 be installed on my PC.
>
> UGH! If I had VB6, I wouldn't need to upgrade!

It should have been my first question: Did you try to upgrade the project?
What happened? What failed?


--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

No--not yet. I was trying to use this "Walk Through" to learn HOW to
upgrade the project. When I tried to run it, I got a message VB6 must be
installed first.

--

RDI

(remove the exclamation from the email address)

"Armin Zingler" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "RDI" <RDI!@!WriteMe.com> schrieb
> > I was able to find a walk-through for upgrading VB6 app to VB.Net.
> > BUT--it requires VB6 be installed on my PC.
> >
> > UGH! If I had VB6, I wouldn't need to upgrade!
>
> It should have been my first question: Did you try to upgrade the project?
> What happened? What failed?
>
>
> --
> Armin
>
> http://www.plig.net/nnq/nquote.html
> http://www.netmeister.org/news/learn2quote.html
>