Is Microsoft.VisualBasic.Compatibility Library installed by .NET Framework?

  • Thread starter Thread starter Howard Kaikow
  • Start date Start date
H

Howard Kaikow

In order to determine whether my sister could run VB or VB .NET on her
recently installed Win 2000 system, I created a trivial VB 6 app, and
corresponding VB .NET 2003 version.

See the HelloWorld-2.zip at http://www.standards.com/index.html#Temporary.

The .zip includes:

1. The VB 6 code and project.
2. The automatically upgraded VB .NET 2003 code and project.
3. The VB 6 and VB.NET 2003 executables that I sent to my sister.

The VB 6 code is given below.

Option Explicit

Public Sub Main()
Dim datNow As Date
datNow = Now()
MsgBox Format(datNow, "h:mm:ss") & " on " & Format(datNow, "d mmm
yyyy"), vbInformation, _
"In case you did not know, it is now"
End Sub

All I did was import the .vbp into both versions of VB .NET and build each
..exe. I wanted to use the upgraded code without doing a full conversion to
VB ..NET.

Both .exe files work on my system.
I have .NET 2002 and .NET 2003 installed in separate OS.

She was able to run the VB 6 version.

Note that she does not have VS .NET, but she tells me that she installed
..NET Framework 1.1 using Windows Update.
As expected, the VB 6 .exe worked.

However, when she ran the VB .NET 2003 .exe, she got the following message:

HelloWorld2003.exe - Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.
Process id=0x538(1364), Thread id=0x150(596).

Is this a problem on her system, or do I need to do something more when
creating the .exe?

Is Microsoft.VisualBasic.Compatibility Library installed by .NET Framework?
 
I sent my sister another VB .NET 2003 .exe that does not uses "Format"
instead of "VB6.Format".
Hopefully, that will turn out to be the problem.
She might not get a chance to try the .exe until this evening.
 
I've just sent her a .exe without a reference to the VB compatibility
library.
Hope that works.

--
http://www.standards.com/; See Howard Kaikow's web site.
Howard Kaikow said:
I sent my sister another VB .NET 2003 .exe that does not uses "Format"
instead of "VB6.Format".
Hopefully, that will turn out to be the problem.
She might not get a chance to try the .exe until this evening.
 
I meant to say"

I sent my sister another VB .NET 2003 .exe that uses "Format"
instead of "VB6.Format".


--
http://www.standards.com/; See Howard Kaikow's web site.
Howard Kaikow said:
I sent my sister another VB .NET 2003 .exe that does not uses "Format"
instead of "VB6.Format".
Hopefully, that will turn out to be the problem.
She might not get a chance to try the .exe until this evening.
 
Howard,
Is Microsoft.VisualBasic.Compatibility Library installed by .NET
Framework?

No the Microsoft.VisualBasic.Compatibility is not installed by the
Framework. It is there to support VB.NET projects that have been upgraded
from VB6. I normally go though such projects and update all code to use
either Microsoft.VisualBasic or the Framework classes themselves. (with a
preference for Framework classes).

If you distribute a VB.NET project that uses
Microsoft.VisualBasic.Compatibility you will need to be certain that
Microsoft.VisualBasic.Compatibility is properly installed to the GAC with
your setup program.

Unfortunately I cannot find the specific URL on MSDN that states the above
right now.

Hope this helps
Jay
 
It would appear that at least 3 messages got removed from this thread.
Will the messages be restored, or are they lost due to the virus shenanigans
going on?

--
http://www.standards.com/; See Howard Kaikow's web site.
Howard Kaikow said:
I sent my sister another VB .NET 2003 .exe that does not uses "Format"
instead of "VB6.Format".
Hopefully, that will turn out to be the problem.
She might not get a chance to try the .exe until this evening.
 
Howard,
As far as I can tell they are lost.

Hope this helps
Jay

Howard Kaikow said:
It would appear that at least 3 messages got removed from this thread.
Will the messages be restored, or are they lost due to the virus shenanigans
going on?

--
http://www.standards.com/; See Howard Kaikow's web site.
Howard Kaikow said:
I sent my sister another VB .NET 2003 .exe that does not uses "Format"
instead of "VB6.Format".
Hopefully, that will turn out to be the problem.
She might not get a chance to try the .exe until this evening.
conversion
 
Thanx for the response.
Outlook Express has been losing posts lately.
I had to unsubscribe twice to get back the postings in this thread.

I sent my sister such a .exe but have not yet heard from her.

I guess that I'll need to install the Framework on a system that does not
have VS .NET so I can test such things myself.

My primary concern is Office, so maybe I need to stick with VB 6 DLLs and
forget about VB .NET.
--
http://www.standards.com/; See Howard Kaikow's web site.
Jay B. Harlow said:
Howard,
Is Microsoft.VisualBasic.Compatibility Library installed by .NET
Framework?

No the Microsoft.VisualBasic.Compatibility is not installed by the
Framework. It is there to support VB.NET projects that have been upgraded
from VB6. I normally go though such projects and update all code to use
either Microsoft.VisualBasic or the Framework classes themselves. (with a
preference for Framework classes).

If you distribute a VB.NET project that uses
Microsoft.VisualBasic.Compatibility you will need to be certain that
Microsoft.VisualBasic.Compatibility is properly installed to the GAC with
your setup program.

Unfortunately I cannot find the specific URL on MSDN that states the above
right now.

Hope this helps
Jay
 
My sister was able to run the version of the code that used "Format" instead
of "VB6.Format", even tho a reference to Microsoft.VisualBasic.Compatibility
is referenced.

She has Office XP, Windows 2000 and .NET 1.1 (from Windoze update). Dunno
if any of those install Microsoft.VisualBasic.Compatibility.

--
http://www.standards.com/; See Howard Kaikow's web site.
Jay B. Harlow said:
Howard,
Is Microsoft.VisualBasic.Compatibility Library installed by .NET
Framework?

No the Microsoft.VisualBasic.Compatibility is not installed by the
Framework. It is there to support VB.NET projects that have been upgraded
from VB6. I normally go though such projects and update all code to use
either Microsoft.VisualBasic or the Framework classes themselves. (with a
preference for Framework classes).

If you distribute a VB.NET project that uses
Microsoft.VisualBasic.Compatibility you will need to be certain that
Microsoft.VisualBasic.Compatibility is properly installed to the GAC with
your setup program.

Unfortunately I cannot find the specific URL on MSDN that states the above
right now.

Hope this helps
Jay
 
They came back after I unsubscribed, resubscribed, unsubscribed,
resubscribed and killed all the old headers and message bodies.

I have a feeling that the MSFT newsgroups are under attack by the
Swen/Automat virus and this may be causing problems.

--
http://www.standards.com/; See Howard Kaikow's web site.
Jay B. Harlow said:
Howard,
As far as I can tell they are lost.

Hope this helps
Jay
 
Back
Top