Visual Basic .

Net
XII Science
Demo Lecture at Royal College Dombivli

By-
Mrs. Shubhangi
Topics Today include

 The .Net Framework

 Studio .Net Environment
 VB .Net
 Introduction to VB .Net
 Architecture of VB .Net
The .Net Framework

 What is the .Net Framework

 Common Language Runtime
 .Net Managed Assemblies
 Compilation of .Net Code
 .Net Framework Class Library
 .Net Languages
 The future of .Net
What is the .Net
Framework
 Primarily a development platform
(mostly effects application
development)
 Consists of two main parts
– Common Language Runtime
– .Net Framework Class Library
CLR (Common Language
Runtime)
 Provides a “runtime environment” for
the execution of code written in ANY
.Net Language
 “Manages”
– The overall execution of .Net code
– Inheritance, Memory, Debugging, and
application development across Multiple
languages
CLR (Continued)
 Languages that utilizes the .Net framework must follow the
CLS
– Common Language Specification
– Outlines the rules and standards required or needed by the CLR
to execute .Net code.
 The CLR will execute Managed Assemblies
 Intermediate Languages managed by the CLR are called
Managed Code
 The CLR will manage for the IL
– Garbage collection
– Object instantiation
– Memory allocation
 Components written in Managed Code by the CLR are called
.Net Managed assemblies
.Net Managed Assemblies
 Basic Unit of deployment of .Net
Applications
 Similar to the Microsoft COM Objects
 Each Managed Assembly contains a Manifest
– Hold definitions of other components required
for execution of the application
– Prevents the problems associated with
conflicting DLL’s
– Revision numbers and components are listed in
the manifest
– Two versions of the same DLL can then co-exist
Compilation of .Net code
 All .Net languages are first compiled into an
intermediate language called MSIL or IL (Microsoft
Intermediate Language)
 The MSIL is then “Just In Time” (JIT) compiled at
first execution of the code and managed by the CLR
 All MSIL or IL code can be compiled directly to
native code with the following
– Compiling native code will provide faster startup execution
of the code
– Performance during execution of the code will then be
sacrificed
– During JIT Optimization is placed on the Managed Code in
order to improve performance at the time of execution
.Net Framework Class
Library
 Provide a library of base classes that
developers can use in their own
applications written in ANY .Net
language
 Because of the use of these base
classes, Inheritance can then be
extensively used in languages that use
the .Net Framework
.Net Languages
 .Net applications can be written by any or a
combination of many .Net languages
 Languages include
– VB .Net
– C#
– J#
– Managed C++ (default in studio is set for managed C++)
 Applications can be developed without the use of
Studio .Net
– Applications can be developed still using a simple text
editor
– ASP .Net Applications as well as other apps can be still
developed using notepad
The future of the .Net
Framework
 Standards were release in 2000 from Microsoft to the community
 GNU .Net is a project in the Linux community that is presently developing a
CLR to run in the Linux environment
 Languages planned to include the CLS are
– APL
– COBOL
– Eifel
– Fortran
– Haskel
– Mercury
– Mondrian
– Oberon
– Pascal
– Perl
– Python
– RPG
– Scheme
Studio .Net Environment
The IDE

 Studio .Net
 The Start Page
 Problems with Studio .Net in the lab
environment
Studio .Net
 All present .Net languages are included under one
development environment
– When using any one of the languages, the studio must be
used (there is no longer an environment for each
language)
– You have to start a new solution/project
 Projects are containers that contain the files associated with
a particular project
 A solution is a container that contains one or more projects
or project containers
 When the IDE is started you have the Projects tab,
online resources, and My Profile
The Start Page

Profile and
environment settings
Tab for
Tab for Additional Help
this view
Previous Projects

Open a project
Start a new
in a diff. location
project
Problems with Studio .Net
environment in the lab
 .Net security must allow access to the J: drive or
the local intra net in order to work properly
 Problems arise when debugging apps on an ASP
.Net server that is not part of the current domain
(CLC) Basic apps will still work fine
 These problems are not present if IIS and remote
debugging tools are installed on the client machine
– This solution is fine for students but is not practical for a
lab
– Due to security holes of IIS you can have hundreds of
security risks on a given network.
– In the Real world situation, all apps will be placed on a
server anyway
Visual Basic .Net

 General Features
 Additional Features of VB .Net
 What has changed in VB .Net
General features
 It is an object oriented language
– Students do better with this subject when they have a firm understanding of objects
– In the past VB had objects but focus was not placed on them
– VB .Net use objects and inheritance with everything
 Uses exception handling extensively
– New techniques are shown to the student for providing feedback from their
programs in order to help trouble shoot errors
– Like with most OOP languages, exceptions that are not handled will cause programs
to abnormally end or exit
 Uses “generics” with creating classes and Sub programs
– Can use the top data type on inheritance of type Object
– Used for late binding of data types and is quite useful when implementing stacks or
queues of any data type (.Net 2.0)
 Provides a quick way to develop heavy duty applications in a windowing
environment
 It is a useful tool for developing event driven programs
Additional Feature of VB
.Net
 Can create both windows applications and web applications at
the click of a mouse button
 The interface between the Databases and applications
– Are the same between web apps and windows apps
– All data are transferred between the apps in XML format
regardless if it is a web application or a windows application
– A copy of the data from the database is loaded into a data set.
– Persistent connections between the application and the database
no longer exists
 Every form is a class and new forms now have to be
instantiated
 VB .Net is still not case sensitive
What is Not in VB .Net
 Data Controls
– Because of the different way that the apps connect to the
database, there is no longer the support of data controls
in VB .Net
– Persistent connections with the database is no longer
present
 Object instantiation is now done differently
 Garbage collection for references that lose there
objects are done periodically not when the
reference lose its scope
 Periodic changes throughout the language making
it vastly different from VB 6.0 in order to make it
compliant to the .Net Framework and the CLS
The Introduction to
VB .Net
 Data Types in VB .Net
 Functions and Sub Procedures
 Practice Examples
Data Types in VB .Net
 Data Types and possible values
– Integer -> -2,147,483,648 (4 bytes)
– Double -> floating point numbers with 14 digits of accuracy
(8
Bytes)
– Decimal -> decimal values ( 16 bytes replaced currency in 6.0)
– Date -> the date (8 Bytes)
– Byte -> 0 to 255 (1 Byte)
– Char -> Unicode character (2 Bytes)
– Boolean ->True or false value (2 Bytes)
– Single -> floating point number with 6 digits of accuracy (4 bytes)
– Short -> 2 byte integer
– Long -> 8 byte integer
– String -> an arrangement of alpha-numeric characters varies in
length
– Object -> any data type 4 bytes
Functions and Sub
procedures / Programs in
VB .Net (Methods)
 Functions and sub procedures must either have a sub or
function keyword in the function or sub procedure heading
 They can be either public or private (following the same
conventions in OOP languages such as C++ or Java)
 All parameters are passed by value by default in VB .Net
 Parameters of any data type may be passed by reference
 All Objects and arrays are passed by reference not value
 All events are handled by a sub procedure in VB .Net
 Functions return a value and Sub Procedures do Not
.NET Infrastructure

VB C# VJ#

Portable Executable

Application Manifest MSIL

CLR

.NET Framework
ASP.NET Architecture

HTTP Request In IIS HTTP Response Out

ASP HTML

DATABASE
ASP.NET

CLR

.NET Framework