Peter,
The Microsoft.VisualBasic namespace is an integral part of VB.NET (and
..NET), types here will not be "cut".
The Microsoft.VisualBasic.Compatibility namespace is used in converted
projects, types here "should" only be used for projects converted from VB6.
I would not expect types here to be "cut" either.
http://msdn.microsoft.com/library/de...eReference.asp
The Microsoft.VisualBasic.Compatibility namespace is wholly contained in the
Microsoft.VisualBasic.Compatibility.dll, this dll is not normally deployed,
hence using it requires you to include it in your setup project. Where as
the Microsoft.VisualBasic namespace is wholly contained in the
Microsoft.VisualBasic.dll, which is installed as part of the framework
itself...
Beep is in the Interaction module in the Microsoft.VisualBasic namespace.
Ergo its safe to use.
Hope this helps
Jay
"Peter Stojkovic" <Pe*************@gmx.net> wrote in message
news:%2********************@TK2MSFTNGP14.phx.gbl.. .
The idea was not use OLD (OUTDATED) parts of VB.NET, that are cutted in
next release by microsoft.
Peter
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... "Peter Stojkovic" <Pe*************@gmx.net> schrieb:I am now using Beep to make a short warning-sound in my VB-Project
What is the aeqivalent command in VS.70, if i dont want use Visual Basic
Run-Time Library Members
There is no managed replacement available. BTW: I strongly recommend to
rethink the decision to use only a part of Visual Basic .NET.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>