cant get vb.net exec to run okay on w98

[desperate]

I created an vb.net exec on an xp machine. I've tried to
run it on a w98 machine. The program executes and
everthing is okay until i click on a command button. I
then get "systemIO file not found exception. File or
assembly name microsoft visualbasic compatibility or one
of its dependencies not found" What file(s) is the W98
looking for. I did download and install the net 1.1 on
the w98 machine but the error still pops up. ????????

[Dhaval Faria]

This error is occuring becasue you must have used System.IO namespace in
your application code, this will work fine with the Windows NT based OS,
becasue they are having File Services which are running and which are
accessible through System.IO namespace, whereas Windows 9x not having any
services running, so you won't be able to use System.IO namespace.

Dhaval Faria
Founder, Programmer
Hirdhav (http://www.hirdhav.com)
Microsoft India Community Star

"desperate" <an*******@discussions.microsoft.com> wrote in message
news:12*****************************@phx.gbl...

I created an vb.net exec on an xp machine. I've tried to
run it on a w98 machine. The program executes and
everthing is okay until i click on a command button. I
then get "systemIO file not found exception. File or
assembly name microsoft visualbasic compatibility or one
of its dependencies not found" What file(s) is the W98
looking for. I did download and install the net 1.1 on
the w98 machine but the error still pops up. ????????

[Armin Zingler]

"Dhaval Faria" <dh*****@hirdhav.com> schrieb

This error is occuring becasue you must have used System.IO namespace
in your application code, this will work fine with the Windows NT
based OS, becasue they are having File Services which are running and
which are accessible through System.IO namespace, whereas Windows 9x
not having any services running, so you won't be able to use
System.IO namespace.

Um.... I don't think this is true. System.IO encapsulates basic file i/o
functions that are definitely also available on previous OSes.

Apart from this, the availabilty is not determined by the namespace, but it
can be retrieved from the documentation of the specific class. For example,
the "Platforms" paragraph at the bottom of the File class is:

"Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows
2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003
family, .NET Compact Framework"

--
Armin

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

[Dhaval Faria]

hmm, thanks for lettming know, was not knowing about that stuff.. and sorry
for the wrong answer.

--
Dhaval Faria
Founder, Programmer
Hirdhav (http://www.hirdhav.com)
Microsoft India Community Star

"Armin Zingler" <az*******@freenet.de> wrote in message
news:Ot**************@tk2msftngp13.phx.gbl...

"Dhaval Faria" <dh*****@hirdhav.com> schrieb

This error is occuring becasue you must have used System.IO namespace
in your application code, this will work fine with the Windows NT
based OS, becasue they are having File Services which are running and
which are accessible through System.IO namespace, whereas Windows 9x
not having any services running, so you won't be able to use
System.IO namespace.
Um.... I don't think this is true. System.IO encapsulates basic file i/o
functions that are definitely also available on previous OSes.

Apart from this, the availabilty is not determined by the namespace, but

it can be retrieved from the documentation of the specific class. For example, the "Platforms" paragraph at the bottom of the File class is:

"Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family, .NET Compact Framework"

--
Armin

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