You can get this error if you are user who is trying to remotely debug and you are not a member of the Debugger Users group on the Microsoft Internet Information Server (IIS) server. To add the appropriate user to the Debugger Users group, follow these steps on the Web server:

1. From the Windows Start menu, point to Programs, point to Administrative Tools, and then click Computer Management.
2. In the left pane, click to expand the Computer Management, System Tools, and Local Users and Groups nodes.
3. Click Groups, and then double-click Debugger Users.
4. In the Debugger Users Properties dialog box, click Add.
5. In the Select Users or Groups dialog box, select the appropriate user, and then click OK.
6. Click OK to exit the Debugger Users Properties dialog box.
7. Close the Computer Management explorer.

Answered by Sharad Singh , an ibibo Master, at 7:20 PM on November 19, 2008

Yes. Since 1991 when it was first introduced by Microsoft, there have been nine versions of Visual Basic up to VB.NET 2005, the current version. The first six versions were all called Visual Basic. In 2002, Microsoft introduced Visual Basic .NET 1.0, a completely redesigned and rewritten version that was a key part of a much larger computer architecture. The first six versions were all "backward compatible". That means that later versions of VB could handle programs written with an earlier version. Because the .NET architecture was such a radical change, earlier versions of Visual Basic have to be rewritten before they can be used with .NET.

Answered by Shishir , an ibibo Master, at 10:56 PM on October 21, 2008

Yes, Starting from VB-1 to VB-6
Visual Basic 1.0 (May 1991) was released for Windows at the Comdex/Windows World trade show in Atlanta, Georgia.

Visual Basic for MS-DOSVisual Basic 1.0 for DOS was released in September 1992. The language itself was not quite compatible with Visual Basic for Windows, as it was actually the next version of Microsoft's DOS-based BASIC compilers, QuickBASIC and BASIC Professional Development System. The interface used the "COW" (Character Oriented Windows) interface, using extended ASCII characters to simulate the appearance of a GUI.
Visual Basic 2.0 was released in November 1992. The programming environment was easier to use, and its speed was improved. Notably, forms became instantiable objects, thus laying the foundational concepts of class modules as were later offered in VB4.
Visual Basic 3.0 was released in the summer of 1993 and came in Standard and Professional versions. VB3 included version 1.1 of the Microsoft Jet Database Engine that could read and write Jet (or Access) 1.x databases.
Visual Basic 4.0 (August 1995) was the first version that could create 32-bit as well as 16-bit Windows programs. It also introduced the ability to write non-GUI classes in Visual Basic. Incompatibilities between different releases of VB4 caused installation and operation problems. While previous versions of Visual Basic had used VBX controls, Visual Basic now used OLE controls (with files names ending in .OCX) instead. These were later to be named ActiveX controls.
With version 5.0 (February 1997), Microsoft released Visual Basic exclusively for 32-bit versions of Windows. Programmers who preferred to write 16-bit programs were able to import programs written in Visual Basic 4.0 to Visual Basic 5.0, and Visual Basic 5.0 programs can easily be converted with Visual Basic 4.0. Visual Basic 5.0 also introduced the ability to create custom user controls, as well as the ability to compile to native Windows executable code, speeding up calculation-intensive code execution. A free, downloadable Control Creation Edition was also released for creation of ActiveX controls. It was also used as an introductory form of Visual Basic: a regular .exe project could be created and run in the IDE, but not compiled.
Visual Basic 6.0 (Mid 1998) improved in a number of areas including the ability to create web-based applications. VB6 has entered Microsoft's "non-supported phase" as of March 2008.
Mainstream Support for Microsoft Visual Basic 6.0 ended on March 31, 2005. Extended support ended in March 2008. In response, the Visual Basic user community expressed its grave concern and lobbied users to sign a petition to keep the product alive. Microsoft has so far refused to change their position on the matter. Ironically, around this time (2005), it was exposed that Microsoft's new anti-spyware offering, Microsoft AntiSpyware (part of the GIANT Company Software purchase), was coded in Visual Basic 6.0. Its replacement, Windows Defender, was rewritten as C++/CLI code.

Answered by Hem@nt .... , an ibibo Master, at 5:29 PM on October 21, 2008

well,Yes. Since 1991 when it was first introduced by Microsoft, there have been nine versions of Visual Basic up to VB.NET 2005, the current version. The first six versions were all called Visual Basic. In 2002, Microsoft introduced Visual Basic .NET 1.0, a completely redesigned and rewritten version that was a key part of a much larger computer architecture. The first six versions were all "backward compatible". That means that later versions of VB could handle programs written with an earlier version. Because the .NET architecture was such a radical change, earlier versions of Visual Basic have to be rewritten before they can be used with .NET. Many programmers still prefer Visual Basic 6.0 and a few use even earlier versions.

Answered by Debashis , an ibibo Master, at 4:45 PM on October 21, 2008

well, VBx is the next version of Visual Basic, not a new version of Visual Basic.

Part of the confusion stems from the fact that there are TWO ways you can use Visual Basic in Silverlight, and one uses Orcas and one uses VBx. So let me see if I can clarify a little bit...

As everyone should be aware now, Silverlight is a cross-platform version of the CLR. This means that Silverlight, with some limitations, can run any compiled IL application or library that the desktop CLR can run. This also means that (again, with some limitations) Visual Basic applications or libraries that have been compiled into IL on the desktop can be downloaded and run on Silverlight. If you go and read Joe's VB on Silverlight entry, he points you to how you can do this today--build a VB application or library using Orcas Beta 1 and then run it on Silverlight.

You'll notice that what you have to do in this scenario, though, is compile your application or library on the desktop and then run it in Silverlight. You can't take your application or library in source code form, send it to Silverlight and have it compiled on demand within Silverlight itself, because the Orcas Visual Basic compiler isn't a part of Silverlight. So, for example, if I was to embed a Silverlight application in a web page viewable on the Mac, I have to build my libraries ahead of time and deploy them to the web server to be downloaded when someone hits the page.

What John and Jim demoed, and what the DLR enables, however, is a second scenario. Because the DLR is managed code, it can be run directly on Silverlight. This means that you can actually get a running instance of a DLR language within Silverlight itself. So instead of having to compile an application or library before you can use it in Silverlight, you can simply include the code as a part of the Silverlight application, and the code can be compiled by the DLR language on the fly. This enables the traditional style of client-side applications that you see in AJAX or other libraries. Instead of compiling the library ahead of time, you simply download the client code to the browser when it hits the page, and the code will be compiled and run within the browser in real time.

This is where VBx, the next version of Visual Basic, comes in. Part of VBx is a hostable managed component (written in Visual Basic, no less!) built on top of the DLR. Since Silverlight can host DLR languages, this enables you to send Visual Basic code to a Silverlight instance and have it dynamically compiled and run. So when the Mac hits your webpage, you don't have to send a binary at all, you can send just source code. When you want to modify your application.
source site: http://www.panopticoncentral.net/ar chive/2007/05/02/20395.aspx

Answered by Uttam , an ibibo Master, at 4:40 PM on October 21, 2008

YES THERE ARE MORE THAN ONE VERSIO OF VB.
LATEST VERSION OF VB ON WHICH I AM WORKING IS VB6.0 & VB7.0

Answered by sudarshan , an ibibo Citizen, at 4:34 PM on October 21, 2008

Yes. Since 1991 when it was first introduced by Microsoft, there have been nine versions of Visual Basic up to VB.NET 2005, the current version. The first six versions were all called Visual Basic. In 2002, Microsoft introduced Visual Basic .NET 1.0, a completely redesigned and rewritten version that was a key part of a much larger computer architecture. The first six versions were all "backward compatible". That means that later versions of VB could handle programs written with an earlier version. Because the .NET architecture was such a radical change, earlier versions of Visual Basic have to be rewritten before they can be used with .NET. Many programmers still prefer Visual Basic 6.0 and a few use even earlier

http://visualbasic.about.com/od /applications/a/whatisvb.htm

Answered by Koushik , an ibibo Specialist, at 4:32 PM on October 21, 2008

Well Vidya! Visual Basic had more than 9 versions. Since 1991 when it was first introduced by Microsoft, there have been nine versions of Visual Basic up to VB.NET 2005.

The current version is VB.NET 2005. The first six versions were all called Visual Basic. In 2002, Microsoft introduced Visual Basic .NET 1.0, a completely redesigned and rewritten version that was a key part of much larger computer architecture. The first six versions were all "backward compatible". That means that later versions of VB could handle programs written with an earlier version. Because the .NET architecture was such a radical change, earlier versions of Visual Basic have to be rewritten before they can be used with .NET. Many programmers still prefer Visual Basic 6.0 and a few use even earlier versions.

Answered by Kumaar , an ibibo Master, at 4:25 PM on October 21, 2008