Following are the disadvantage of VB :
1. VB is not object oriented.
2. VB DLL does not support side-by-side execution
3. Deployment is time consuming as all the components must 
be registered in the Windows registry.

1.The VB support OOP concepts,but not support fully.

2.VB does not support exception handling.

3.No multithreading mechanism.

kamal....

The dlls of the VB is mapped with the Registry so the 
overhead on the registry is increased.
Vb is not Object oriented bcoz it don't hv classes
it hv only the functions so we hv to learn the functions 
for the programing we can't import the classs.
vb is only for the application programing but nw the 
scenario is for web applications?

VB dosent use magic

1,supports Threading
2,powerful Exception handling
mechanism
3,having support for the
console based applications
4,More than one version of
dll is supported

1. VB is object based while Vb.net is Object oriented
2. VB.net using OO functionality like inheritenca, 
Excepetional handling, etc
3.VB .net is strong type casting whicv VB lack
4.VB.net supports multi threading....

1. vb.net support Multi-Threading.
2. vb.net is used as language in asp.net
3. vb.net is OO while vb is object based.
4. vb.net support exception handling.

1. VB.net is object oriented
2. VB.Net can be used in Managed Code
3. It supports inheritance, implement

1.supports Threading
2.powerful Exception handling mechanism
3.having support for the console based applications
4.vb has its own interpreter and vb.net has compiler(CLR).
5.VB is object based while Vb.net is Object oriented

yes VB.NET ia an object oriented.

vb.net is object oriented concept.it is supports to 
inheritence but it donot support to multiple inheritance.

Vb.net supports all inheritance

1)single inheritance
It means Single class inheriting to single child classes
2)multiple inheritance
multiple classess inherits to single classes
3)Multilevel  Inheritance
Single class inherits to one class that class inheritd to 
single another class
4)Heirarichal inheritance 
Single class inherits to Multiple classes
5)Hybrid Inheritance
Single class inherits to different classess and that 
classes inherits to one class

With respect to Answer 3 of this Question.
I think following are still not clear-

4)Heirarichal inheritance 
Single class inherits to Multiple classes

This is not possible in .NET.
5)Hybrid Inheritance
Single class inherits to different classes and that class 
inherits to one class

It should be Single class inherits to different class (not,
classes) and that class inherits to one class

yes,vb.net is object oriented.
vb.net supports only
1)single level inheritance/simple inheritance
2) multi level inheritance
3)hierachical inheritance

vb.net doesn't supports
multiple,hybrid inheritance.

vb.net is not a object oriented. its a compiled language.

vb.net is not pure object oriented as compare C#.it is 
support inheritance concepts but not supports to multiple 
inheritance

Answer 4 & 5 is the correct one. Pls ignore all other answers.

VB.Net is an Object Oriented Language.
It doesn't support multiple inheritance. For this purpose, 
interfaces are introduced. 
VB.Net supports multiple interfaces

vb.net is not a object oriented. its a compiled language.

- the most dumbest answer. Please don't give wrong answers 
when you are not sure. It will misguide the readers.

hey hari,i have faced the interview Question what are 
interfaces?
  I answer Vb.net doesn't supports multiple inheritance,but 
it can be achieved in .net using interfaces. Interfaces are 
silmilar to class,that contain methods.
  but they do not provide any implementation for these 
methods. 

Then they asked WHY VB.NET DOESN't SUPPORTS MULTIPLE 
INHERITANCE??
If u know Can u plz answer!!!!!!!!!

assemblies contain more then one dll an exe and executable 
code

BOTH VB DLL AND ASSEMBLIES ARE REUSEABLE CODE
BUT WHEN YOU CREATE TWO DLLS WITH SAME NAME IN VB
VERSIONING PROBLEM OCCURS IN VB

IN ASSEMBLES ARE INTRODUCED TO AVOID VISIONIG PROBLEM
IN .NET

Assemblies can contain DLL and EXE both. Different versions 
of one DLL can be handeled by assemblies. They overcome the 
DLL Hell problem. Assemblies Contain Manifest and MetaData 
files. These are the seprate files that describes the 
Assembly and its attributes. 

VB DLL is inprocess.DLL run with an exe                   
where as DLL are not self executable. 
we can reuse DLLs .DLL are not platform independent
If we have more then one Versions of a DLL we can face DLL 
Hell Problem.

Assemblies can contain morethan one dll,exe and html file 
and they represents the resources,type definition and 
implementation of those types.

All most all languages support VB DLL(COM DLL).But
assemblies can support only in .Net frameworks..

Orcle9i Data Provider for DotNet using this provider we can
connect to Orcle DB.

You use gacutil if I remember correctly.

we have to register in the GAk.

remotimg is an internet and webservices is an intranet 
aplication.remotimg is fast wen compared to webservices

Remoting is a technology used to communcate between 
applications of same platform and encoding will be in the 
form of binary. 
 In the case of web service  applications in different 
platforms can communicate and data will get transferred as 
xml files

Re: About remoting and web services. Difference between 
them? 
Answer
# 1 remotimg is an internet and webservices is an intranet 
aplication.remotimg is fast wen compared to webservices
 gopinath k
 
   
   Re: About remoting and web services. Difference between 
them? 
Answer
# 2 Remoting is a technology used to communcate between 
applications of same platform and encoding will be in the 
form of binary. asp.net 3.0 onwards its applications in 
different platforms .. 
 In the case of web service  applications in different 
platforms can communicate and data will get transferred as 
xml files
  gopinath k

totally incorrect answer

http://venkysnotebook.blogspot.com/2008/10/net-remoting.html

What is .NET Remoting?

.NET Remoting is an enabler for application communication.
It is a generic system for different applications to use to
communicate with one another. .NET objects are exposed to
remote processes, thus allowing interprocess communication.
The applications can be located on the same computer,
different computers on the same network, or even computers
across separate networks.
.NET Remoting versus Distributed COM

In the past interprocess communication between applications
was handled through Distributed COM, or DCOM. DCOM works
well and the performance is adequate when applications exist
on computers of similar type on the same network. However,
DCOM has its drawbacks in the Internet connected world. DCOM
relies on a proprietary binary protocol that not all object
models support, which hinders interoperability across
platforms. In addition, have you tried to get DCOM to work
through a firewall? DCOM wants to communicate over a range
of ports that are typically blocked by firewalls. There are
a ways to get it to work, but they either decrease the
effectiveness of the firewall (why bother to even have the
firewall if you open up a ton of ports on it), or require
you to get a firewall that allows support for binary traffic
over port 80.

.NET Remoting eliminates the difficulties of DCOM by
supporting different transport protocol formats and
communication protocols. This allows .NET Remoting to be
adaptable to the network environment in which it is being used.
.NET Remoting versus Web Services

Unless you have been living in a cave, or are way behind in
your reading, you have probably read something about Web
services. When you read the description of .NET Remoting it
may remind you a lot of what you're read about Web services.
That is because Web services fall under the umbrella of .NET
Remoting, but have a simplified programming model and are
intended for a wide target audience.

Web services involve allowing applications to exchange
messages in a way that is platform, object model, and
programming language independent. Web services are stateless
and know nothing about the client that is making the
request. The clients communicate by transferring messages
back and forth in a specific format known as the Simple
Object Access Protocol, or SOAP. (Want to get some funny
looks in the hallway? Stand around in the hallway near the
marketing department with your colleagues and discuss the
benefits of using SOAP).

The following list outlines some of the major differences
between .NET Remoting and Web services that will help you to
decide when to use one or the other:

* ASP.NET based Web services can only be accessed over HTTP.
.NET Remoting can be used across any protocol.

* Web services work in a stateless environment where each
request results in a new object created to service the
request. .NET Remoting supports state management options and
can correlate multiple calls from the same client and
support callbacks.

* Web services serialize objects through XML contained in
the SOAP messages and can thus only handle items that can be
fully expressed in XML. .NET Remoting relies on the
existence of the common language runtime assemblies that
contain information about data types. This limits the
information that must be passed about an object and allows
objects to be passed by value or by reference.

* Web services support interoperability across platforms and
are good for heterogeneous environments. .NET Remoting
requires the clients be built using .NET, or another
framework that supports .NET Remoting, which means a
homogeneous environment.


Channels

Remote objects are accessed through Channels. Channels
physically transport the messages to and from remote
objects. There are two existing channels TcpChannel and
HttpChannel. Their names give away the protocols that they
use. In addition, the TcpChannel or HttpChannel can be
extended, or a new channel created if you determine the
existing channels do not meet your needs.
Create a Remotable Object
A remotable object is nothing more than an object that
inherits from MarshalByRefObject. The following sample
demonstrates a simple class to expose the omnipresent hello
world. This object exposes a single method HelloWorld that
will return a string. The only values that can be returned
from methods are the classes in the .NET Framework that are
serializable such as string and DataSet. In addition, if you
need to return a user-defined object then the object needs
to be marked as serializable.

Create a new C# class library project. Add a class called
SampleObject and put in the following code. Add a reference
to System.Runtime.Remoting in the project, otherwise the
TcpChannel will not be found. Compile the class to make sure
you have everything correct.

using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Tcp;

namespace CodeGuru.Remoting
{
///
/// Sample object to demonstrate the use of .NET Remoting.
///
public class SampleObject : MarshalByRefObject
{
///
/// Constructor
///
public SampleObject()
{
}

///
/// Return a hello message
///
/// Hello world message
public string HelloWorld()
{
return "Hello World!";
}
}
}

Create a Server To Expose the Remotable Object

We need to create a server object that will act as a
listener to accept remote object requests. For this example
we will use the TCP/IP channel. We first create an instance
of the channel and then register it for use by clients at a
specific port. The service can be registered as
WellKnownObjectMode.SingleCall, which results in a new
instance of the object for each client, or as
WellKnownObjectMode.Singleton, which results in one instance
of the object used for all clients.

It is not necessary to create the server listener if you are
planning to use IIS. For obvious reasons, IIS only supports
the use of the HttpChannel. Create a virtual directory for
your application and then put code to register your service
in the Application_Start event.

For our example, we'll go ahead and create a server listener
in case you don't have IIS. Since the service needs to be
bound to an available port, for our example I chose 8080,
which is a port that I know to be unused on my computer. You
may need to choose a different port depending upon what
ports you have available. To see a list of the used ports on
your computer open a command prompt and issue the command
"netstat --a". It may produce a long listing so make sure
the command prompt buffer sizes are set to allow scrolling.
Compile the class to make sure you have everything correct.

Create a new C# console application project. Add a class
called SampleServer and paste in the following code. Add a
reference to System.Runtime.Remoting in the project,
otherwise the TcpChannel will not be found. In addition, add
a reference to the project containing the SampleObject,
otherwise the code will not compile because it won't know
how to find a reference to SampleObject.

using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Tcp;

namespace CodeGuru.Remoting
{
///
/// Sample server to demonstrate the use of .NET Remoting.
///
public class SampleServer
{
public static int Main(string [] args)
{
// Create an instance of a channel
TcpChannel channel = new TcpChannel(8080);
ChannelServices.RegisterChannel(channel);

// Register as an available service with the name HelloWorld
RemotingConfiguration.RegisterWellKnownServiceType(
typeof(SampleObject),
"HelloWorld",
WellKnownObjectMode.SingleCall );

System.Console.WriteLine("Press the enter key to exit...");
System.Console.ReadLine();
return 0;
}

}
}

Create a Client To Use the Remotable Object

Now that we have our remotable object and a server object to
listen for requests, let's create a client to use it. Our
client will be very simple. It will connect to the server,
create an instance of the object using the server, and then
execute the HelloWorld method.

Create a new C# console application project. Add a class
called SampleClient and paste in the following code. Add a
reference to System.Runtime.Remoting in the project,
otherwise the TcpChannel will not be found. In addition, add
a reference to the project containing the SampleObject,
otherwise the code will not compile because it won't know
how to find a reference to SampleObject. Compile the class
to make sure you have everything correct.

using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Tcp;

namespace CodeGuru.Remoting
{
///
/// Sample client to demonstrate the use of .NET Remoting.
///
public class SampleClient
{
public static int Main(string [] args)
{
// Create a channel for communicating w/ the remote object
// Notice no port is specified on the client
TcpChannel chan = new TcpChannel();
ChannelServices.RegisterChannel(chan);

// Create an instance of the remote object
SampleObject obj = (SampleObject) Activator.GetObject(
typeof(CodeGuru.Remoting.SampleObject),
"tcp://localhost:8080/HelloWorld" );

// Use the object
if( obj.Equals(null) )
{
System.Console.WriteLine("Error: unable to locate server");
}
else
{
Console.WriteLine(obj.HelloWorld());
}
return 0;
}
}
}

Test the Remoting Sample

Once you have created the projects and successfully compiled
each of them you are ready to try it out. Assuming you chose
a free TCP/IP port for the service, start the server
executable. After the server successfully starts it will
result in a console window being displayed with the message
"Press the enter key to exit". The server is listening so
you are now ready to run the client. Executing the client
should result in "Hello World!" being displayed in a
separate console window. The client window will then close
while the server remains open and available.

If you have multiple computers available to you on a network
you could execute the server on one machine and the client
on another just to prove to yourself that it really is
remoting. In order to run on separate machines you would
need to change the reference to localhost in the sample
client to point to the appropriate location.
Summary

.NET Remoting is a powerful way to enable interprocess
communication. It is more complicated to program against
than Web services. You need to decide for yourself whether
your standard architecture is to use .NET Remoting or Web
services.
Future Columns

The next column will be on the use of encryption in the .NET
framework. We'll take a look at some of the encryption
algorithms available in the framework and ways to use them.

Third party can able to see your query and also there can 
be SQL Injection if the query is SQL statement.

Query should be encrypted before sending from application.

IIS 6.0 supports the following authentication methods: 

? Anonymous authentication. This authentication method 
allows everyone access to the public areas of your Web 
sites, without asking for a user name or password.
 
? Basic authentication. This authentication method prompts 
the user for a user name and a password, also called 
credentials, which are sent unencrypted over the network.
 
? Digest authentication. This authentication method 
operates much like Basic authentication, except that 
passwords are sent across the network as a hash value for 
additional security. Digest authentication is available 
only on domains with domain controllers running Windows 
server operating systems.
 
? Advanced Digest authentication. This authentication 
method is identical to Digest authentication, except 
Advanced Digest authentication stores the client 
credentials as a Message Digest (MD5) hash in Active 
Directory on your domain controller running Windows Server 
2003.
 
? Integrated Windows authentication. This authentication 
method uses hashing technology to scramble user names and 
passwords before sending them over the network.
 
? UNC authentication. This authentication method passes 
users' credentials through to the computer with the 
Universal Naming Convention (UNC) share.
 
? .NET Passport Authentication. This authentication method 
is a user-authentication service that lets Web site users 
create a single sign-in name and password for access to 
all .NET Passport?enabled Web sites and services. .NET 
Passport?enabled sites rely on the .NET Passport central 
server to authenticate users; .NET Passport?enabled sites 
do not host and maintain their own proprietary 
authentication systems.
 
? Certificate authentication. This authentication method 
uses Secure Sockets Layer (SSL) certificates to 
authenticate servers and clients.
 

IIS 6.0 supports the following authentication methods: 

? Anonymous authentication. This authentication method 
allows everyone access to the public areas of your Web 
sites, without asking for a user name or password.
 
? Basic authentication. This authentication method prompts 
the user for a user name and a password, also called 
credentials, which are sent unencrypted over the network.
 
? Digest authentication. This authentication method 
operates much like Basic authentication, except that 
passwords are sent across the network as a hash value for 
additional security. Digest authentication is available 
only on domains with domain controllers running Windows 
server operating systems.
 
? Advanced Digest authentication. This authentication 
method is identical to Digest authentication, except 
Advanced Digest authentication stores the client 
credentials as a Message Digest (MD5) hash in Active 
Directory on your domain controller running Windows Server 
2003.
 
? Integrated Windows authentication. This authentication 
method uses hashing technology to scramble user names and 
passwords before sending them over the network.
 
? UNC authentication. This authentication method passes 
users' credentials through to the computer with the 
Universal Naming Convention (UNC) share.
 
? .NET Passport Authentication. This authentication method 
is a user-authentication service that lets Web site users 
create a single sign-in name and password for access to 
all .NET Passport?enabled Web sites and services. .NET 
Passport?enabled sites rely on the .NET Passport central 
server to authenticate users; .NET Passport?enabled sites 
do not host and maintain their own proprietary 
authentication systems.
 
? Certificate authentication. This authentication method 
uses Secure Sockets Layer (SSL) certificates to 
authenticate servers and clients.

IIS 6.0 supports the following authentication methods: 

? Anonymous authentication. This authentication method 
allows everyone access to the public areas of your Web 
sites, without asking for a user name or password.
 
? Basic authentication. This authentication method prompts 
the user for a user name and a password, also called 
credentials, which are sent unencrypted over the network.
 
? Digest authentication. This authentication method 
operates much like Basic authentication, except that 
passwords are sent across the network as a hash value for 
additional security. Digest authentication is available 
only on domains with domain controllers running Windows 
server operating systems.
 
? Advanced Digest authentication. This authentication 
method is identical to Digest authentication, except 
Advanced Digest authentication stores the client 
credentials as a Message Digest (MD5) hash in Active 
Directory on your domain controller running Windows Server 
2003.
 
? Integrated Windows authentication. This authentication 
method uses hashing technology to scramble user names and 
passwords before sending them over the network.
 
? UNC authentication. This authentication method passes 
users' credentials through to the computer with the 
Universal Naming Convention (UNC) share.
 
? .NET Passport Authentication. This authentication method 
is a user-authentication service that lets Web site users 
create a single sign-in name and password for access to 
all .NET Passport?enabled Web sites and services. .NET 
Passport?enabled sites rely on the .NET Passport central 
server to authenticate users; .NET Passport?enabled sites 
do not host and maintain their own proprietary 
authentication systems.
 
? Certificate authentication. This authentication method 
uses Secure Sockets Layer (SSL) certificates to 
authenticate servers and clients.

COM was not designed to be extensible whereas .Net 
component are run within COM+ applications so no COM 
callable wrapper is required. Hence it runs as a .Net 
component.

Com component needs registeration and .Net component 
doesn't require it.

.NET applications are managed by .NET Runtime so it is 
useful for memory management,security,caching,versioning) 
and so it is said as Managed.But COM Components are said as 
Unmanaged.

.These are not directly access to the .NET.
.These are not supporting Distribute network,only DCOM will 
support it.

Boxing is an implicit conversion of a value type to the 
type object
 	int i = 123; // A value type 
 	Object box = i // Boxing 
CASTING: casting is the process of converting a variable 
from one type to another (from a string to an integer)
Unboxing is an explicit conversion from the type object to 
a value type 
 	int i = 123; // A value type 
 	object box = i; // Boxing 
 	int j = (int) box; // Unboxing

Boxing is the conversion value type to ref. type.

int i=5 -- value type
Object obj;  -- Referance type
obj=i;    -- Boxing


int j =(int) obj  -- Unboxing

Boxing is an implicit conversion of a value type to the 
type object
 	int i = 123; // A value type 
 	Object box = i // Boxing 

In case of value type ,value is stored in the stack but 
after boxing process value is stored in to heap.

using css

There are mainly three types of authentication types in
.NET. These are
i)  Forms Authentication.
ii) Windows Authentication.
iii)Passport Authentication.

Two types of authentications.

1. Windows Authentication
2. Mixed Authentication

to retrieve user id in case of windows authentication

if from a ASP.Net page following code
  
Dim username As String
username = User.Identity.Name 

if it is from a class or business object following code

Dim User As System.Security.Principal.IPrincipal
User = System.Web.HttpContext.Current.User

Different types windows authentications are 
1. Windows Authentication
2. IIS Authentication.
3. Forms Authentication.
4. Passport Authentication.

Windows Authentication
2. IIS Authentication.
3. Forms Authentication.
4. Passport Authentication.

It consists assembly version info

It contains the version information that will go into your 
app or 
assembly - things like the company name, copyright notices 
etc., and 
the assembly version number, of course. 

You can inspect those values in Windows Explorer by right-
clicking on 
an .EXE or .DLL, go "Properties", and then go to 
the "Version" tab - 
those pieces of info in there come from whatever you fill 
into 
"AssemblyInfo.cs" in your project.