Loading a data set and creating a data pipeline

Preprocessing data in ML.NET is unique and different from other frameworks because it requires an explicit class of our data structure. To do so, we create a class called InputModel, and we will state all the columns of our data set.

For this article, we have used the Credit Card Fraud Detection data set from Kaggle. This data set contains 31 columns. The class of the transaction, either 0 or 1, the amount of the transaction, the time the transaction occurred, and 28 other columns.

Now that we have our data modeled, we need also to model what our output should look like; The below script can achieve this.

The next step should be loading downloaded .csv data; Having defined model input and datafile path, and other constructor options.

Afterward, we will define the data process configuration with pipeline data transformations.

Training and saving the Model

Next, setting the training algorithm and evaluating the quality of the Model.

Usage of the saved model and prediction of credit card fraud are included in program.cs on Github page.

Loading a data set and creating a data pipeline

Preprocessing data in ML.NET is unique and different from other frameworks because it requires an explicit class of our data structure. To do so, we create a class called InputModel, and we will state all the columns of our data set.

For this article, we have used the Credit Card Fraud Detection data set from Kaggle. This data set contains 31 columns. The class of the transaction, either 0 or 1, the amount of the transaction, the time the transaction occurred, and 28 other columns.

Now that we have our data modeled, we need also to model what our output should look like; The below script can achieve this.

The next step should be loading downloaded .csv data; Having defined model input and datafile path, and other constructor options.

Afterward, we will define the data process configuration with pipeline data transformations.

Training and saving the Model

Next, setting the training algorithm and evaluating the quality of the Model.

Usage of the saved model and prediction of credit card fraud are included in program.cs on Github page.

Loading a data set and creating a data pipeline

Preprocessing data in ML.NET is unique and different from other frameworks because it requires an explicit class of our data structure. To do so, we create a class called InputModel, and we will state all the columns of our data set.

For this article, we have used the Credit Card Fraud Detection data set from Kaggle. This data set contains 31 columns. The class of the transaction, either 0 or 1, the amount of the transaction, the time the transaction occurred, and 28 other columns.

Now that we have our data modeled, we need also to model what our output should look like; The below script can achieve this.

The next step should be loading downloaded .csv data; Having defined model input and datafile path, and other constructor options.

Afterward, we will define the data process configuration with pipeline data transformations.

Training and saving the Model

Next, setting the training algorithm and evaluating the quality of the Model.

Usage of the saved model and prediction of credit card fraud are included in program.cs on Github page.

Creational patterns are ones that create objects, rather than having to instantiate objects directly. This gives the program more flexibility in deciding which objects need to be created for a given case.

Abstract factory

Groups object factories that have a common theme.

The abstract factory pattern is a design pattern that allows for the creation of groups of related objects without the requirement of specifying the exact concrete classes that will be used. One of a number of factory classes generates the object sets.

Builder

Constructs complex objects by separating construction and representation.

The builder pattern is a design pattern that allows for the step-by-step creation of complex objects using the correct sequence of actions. The construction is controlled by a director object that only needs to know the type of object it is to create.

Factory method

The factory method pattern is a design pattern that allows for the creation of objects without specifying the type of object that is to be created in code. A factory class contains a method that allows determination of the created type at run-time.

Prototype

Creates objects by cloning an existing object.

The prototype design pattern is a design pattern that is used to instantiate a class by copying, or cloning, the properties of an existing object. The new object is an exact copy of the prototype but permits modification without altering the original.

Singleton

Restricts object creation for a class to only one instance.

The singleton pattern is a design pattern that is used to ensure that a class can only have one concurrent instance. Whenever additional objects of a singleton class are required, the previously created, single instance is provided.

Structural

These concern class and object composition. They use inheritance to compose interfaces and define ways to compose objects to obtain new functionality.

Adapter

Allows classes with incompatible interfaces to work together by wrapping its own interface around that of an already existing class.

The adapter pattern is a design pattern that is used to allow two incompatible types to communicate. Where one class relies upon a specific interface that is not implemented by another class, the adapter acts as a translator between the two types.

Bridge

Decouples an abstraction from its implementation so that the two can vary independently.

The bridge pattern is a design pattern that separates the abstract elements of a class from its technical implementation. This provides a cleaner implementation of real-world objects and allows the implementation details to be changed easily.

Composite

Composes zero-or-more similar objects so that they can be manipulated as one object.

The composite pattern is a design pattern that is used when creating hierarchical object models. The pattern defines a manner in which to design recursive tree structures of objects, where individual objects and groups can be accessed in the same manner.

Decorator

Dynamically adds/overrides behaviour in an existing method of an object.

The decorator pattern is a design pattern that extends the functionality of individual objects by wrapping them with one or more decorator classes. These decorators can modify existing members and add new methods and properties at run-time.

Facade

provides a simplified interface to a large body of code.

The facade pattern is a design pattern that is used to simplify access to functionality in complex or poorly designed subsystems. The facade class provides a simple, single-class interface that hides the implementation details of the underlying code.

Flyweight

reduces the cost of creating and manipulating a large number of similar objects.

The flyweight pattern is a design pattern that is used to minimize resource usage when working with very large numbers of objects. When creating many thousands of identical objects, stateless flyweights can lower the memory used to a manageable level.

Proxy

provides a placeholder for another object to control access, reduce cost, and reduce complexity.

Proxy in a most general form is an interface to something else (Subject class). Proxy can be used when we don’t want to access to the resource or subject directly because of some base of permissions or if we don’t want to expose all of the methods of subject class. In some cases, proxies can add some extra functionality. Using proxies is very helpful when we need to access resources which are hard to instantiate, are slow to execute or are resource sensitive.

Behavioral

Most of these design patterns are specifically concerned with communication between objects.

Chain of responsibility

delegates commands to a chain of processing objects.

The chain of responsibility pattern is a design pattern that defines a linked list of handlers, each of which is able to process requests. When a request is submitted to the chain, it is passed to the first handler in the list that is able to process it.

Command

creates objects that encapsulate actions and parameters.

The command pattern is a design pattern that enables all of the information for a request to be contained within a single object. The command can then be invoked as required, often as part of a batch of queued commands with rollback capabilities.

Iterator

accesses the elements of an object sequentially without exposing its underlying representation.

The iterator pattern is a design pattern that provides a means for the elements of an aggregate object to be accessed sequentially without knowledge of its structure. This allows traversing of lists, trees and other structures in a standard manner.

Mediator

allows loose coupling between classes by being the only class that has detailed knowledge of their methods.

The mediator pattern is a design pattern that promotes loose coupling of objects by removing the need for classes to communicate with each other directly. Instead, mediator objects are used to encapsulate and centralize the interactions between classes.

Memento

provides the ability to restore an object to its previous state (undo).

The memento pattern is a design pattern that permits the current state of an object to be stored without breaking the rules of encapsulation. The originating object can be modified as required but can be restored to the saved state at any time.

Observer

is a publish/subscribe pattern, which allows a number of observer objects to see an event.

The observer pattern is a design pattern that defines a link between objects so that when one object's state changes, all dependent objects are updated automatically. This pattern allows communication between objects in a loosely coupled manner.

State

allows an object to alter its behavior when its internal state changes.

The state pattern is a design pattern that allows an object to completely change its behavior depending upon its current internal state. By substituting classes within a defined context, the state object appears to change its type at run-time.

Strategy

Allows one of a family of algorithms to be selected on-the-fly at runtime.

The strategy pattern is a design pattern that allows a set of similar algorithms to be defined and encapsulated in their own classes. The algorithm to be used for a particular purpose may then be selected at run-time according to your requirements.

Template

method defines the skeleton of an algorithm as an abstract class, allowing its subclasses to provide concrete behavior.

The template method pattern is a design pattern that allows a group of interchangeable, similarly structured, multi-step algorithms to be defined. Each algorithm follows the same series of actions but provides a different implementation of the steps.

Visitor

separates an algorithm from an object structure by moving the hierarchy of methods into one object.

The visitor pattern is a design pattern that separates a set of structured data from the functionality that may be performed upon it. This promotes loose coupling and enables additional operations to be added without modifying the data classes.

References:

• Design Patterns - Wikipedia
• Gang of Four Design Patterns - Spring Framework Guru

Creational patterns are ones that create objects, rather than having to instantiate objects directly. This gives the program more flexibility in deciding which objects need to be created for a given case.

Abstract factory

Groups object factories that have a common theme.

The abstract factory pattern is a design pattern that allows for the creation of groups of related objects without the requirement of specifying the exact concrete classes that will be used. One of a number of factory classes generates the object sets.

Builder

Constructs complex objects by separating construction and representation.

The builder pattern is a design pattern that allows for the step-by-step creation of complex objects using the correct sequence of actions. The construction is controlled by a director object that only needs to know the type of object it is to create.

Factory method

The factory method pattern is a design pattern that allows for the creation of objects without specifying the type of object that is to be created in code. A factory class contains a method that allows determination of the created type at run-time.

Prototype

Creates objects by cloning an existing object.

The prototype design pattern is a design pattern that is used to instantiate a class by copying, or cloning, the properties of an existing object. The new object is an exact copy of the prototype but permits modification without altering the original.

Singleton

Restricts object creation for a class to only one instance.

The singleton pattern is a design pattern that is used to ensure that a class can only have one concurrent instance. Whenever additional objects of a singleton class are required, the previously created, single instance is provided.

Structural

These concern class and object composition. They use inheritance to compose interfaces and define ways to compose objects to obtain new functionality.

Adapter

Allows classes with incompatible interfaces to work together by wrapping its own interface around that of an already existing class.

The adapter pattern is a design pattern that is used to allow two incompatible types to communicate. Where one class relies upon a specific interface that is not implemented by another class, the adapter acts as a translator between the two types.

Bridge

Decouples an abstraction from its implementation so that the two can vary independently.

The bridge pattern is a design pattern that separates the abstract elements of a class from its technical implementation. This provides a cleaner implementation of real-world objects and allows the implementation details to be changed easily.

Composite

Composes zero-or-more similar objects so that they can be manipulated as one object.

The composite pattern is a design pattern that is used when creating hierarchical object models. The pattern defines a manner in which to design recursive tree structures of objects, where individual objects and groups can be accessed in the same manner.

Decorator

Dynamically adds/overrides behaviour in an existing method of an object.

The decorator pattern is a design pattern that extends the functionality of individual objects by wrapping them with one or more decorator classes. These decorators can modify existing members and add new methods and properties at run-time.

Facade

provides a simplified interface to a large body of code.

The facade pattern is a design pattern that is used to simplify access to functionality in complex or poorly designed subsystems. The facade class provides a simple, single-class interface that hides the implementation details of the underlying code.

Flyweight

reduces the cost of creating and manipulating a large number of similar objects.

The flyweight pattern is a design pattern that is used to minimize resource usage when working with very large numbers of objects. When creating many thousands of identical objects, stateless flyweights can lower the memory used to a manageable level.

Proxy

provides a placeholder for another object to control access, reduce cost, and reduce complexity.

Proxy in a most general form is an interface to something else (Subject class). Proxy can be used when we don’t want to access to the resource or subject directly because of some base of permissions or if we don’t want to expose all of the methods of subject class. In some cases, proxies can add some extra functionality. Using proxies is very helpful when we need to access resources which are hard to instantiate, are slow to execute or are resource sensitive.

Behavioral

Most of these design patterns are specifically concerned with communication between objects.

Chain of responsibility

delegates commands to a chain of processing objects.

The chain of responsibility pattern is a design pattern that defines a linked list of handlers, each of which is able to process requests. When a request is submitted to the chain, it is passed to the first handler in the list that is able to process it.

Command

creates objects that encapsulate actions and parameters.

The command pattern is a design pattern that enables all of the information for a request to be contained within a single object. The command can then be invoked as required, often as part of a batch of queued commands with rollback capabilities.

Iterator

accesses the elements of an object sequentially without exposing its underlying representation.

The iterator pattern is a design pattern that provides a means for the elements of an aggregate object to be accessed sequentially without knowledge of its structure. This allows traversing of lists, trees and other structures in a standard manner.

Mediator

allows loose coupling between classes by being the only class that has detailed knowledge of their methods.

The mediator pattern is a design pattern that promotes loose coupling of objects by removing the need for classes to communicate with each other directly. Instead, mediator objects are used to encapsulate and centralize the interactions between classes.

Memento

provides the ability to restore an object to its previous state (undo).

The memento pattern is a design pattern that permits the current state of an object to be stored without breaking the rules of encapsulation. The originating object can be modified as required but can be restored to the saved state at any time.

Observer

is a publish/subscribe pattern, which allows a number of observer objects to see an event.

The observer pattern is a design pattern that defines a link between objects so that when one object's state changes, all dependent objects are updated automatically. This pattern allows communication between objects in a loosely coupled manner.

State

allows an object to alter its behavior when its internal state changes.

The state pattern is a design pattern that allows an object to completely change its behavior depending upon its current internal state. By substituting classes within a defined context, the state object appears to change its type at run-time.

Strategy

Allows one of a family of algorithms to be selected on-the-fly at runtime.

The strategy pattern is a design pattern that allows a set of similar algorithms to be defined and encapsulated in their own classes. The algorithm to be used for a particular purpose may then be selected at run-time according to your requirements.

Template

method defines the skeleton of an algorithm as an abstract class, allowing its subclasses to provide concrete behavior.

The template method pattern is a design pattern that allows a group of interchangeable, similarly structured, multi-step algorithms to be defined. Each algorithm follows the same series of actions but provides a different implementation of the steps.

Visitor

separates an algorithm from an object structure by moving the hierarchy of methods into one object.

The visitor pattern is a design pattern that separates a set of structured data from the functionality that may be performed upon it. This promotes loose coupling and enables additional operations to be added without modifying the data classes.

References:

• Design Patterns - Wikipedia
• Gang of Four Design Patterns - Spring Framework Guru

• Do-Factory version of Gang Of Four E-book and examples for C# with Visio UML Diagrams
• O'reilly Head First Design Patterns E-book and examples for C#
• Refactoring-Guru Dive Into Design Patterns E-book and examples for C# and Dive Into Refactoring offline E-book.
• Two complete set of C# projects for design patterns.

Click here Download

Ask for the password through the Contact Me page. I'll reply ASAP.

• Do-Factory version of Gang Of Four E-book and examples for C# with Visio UML Diagrams
• O'reilly Head First Design Patterns E-book and examples for C#
• Refactoring-Guru Dive Into Design Patterns E-book and examples for C# and Dive Into Refactoring offline E-book.
• Two complete set of C# projects for design patterns.

Click here Download

Ask for the password through the Contact Me page. I'll reply ASAP.

• Do-Factory version of Gang Of Four E-book and examples for C# with Visio UML Diagrams
• O'reilly Head First Design Patterns E-book and examples for C#
• Refactoring-Guru Dive Into Design Patterns E-book and examples for C# and Dive Into Refactoring offline E-book.
• Two complete set of C# projects for design patterns.

Click here Download

Ask for the password through the Contact Me page. I'll reply ASAP.

Compilation And Execution Of .Net

Database Access Types

1.Programming Concepts

1.1 Assemblies

1.1.1 Assembly Contents

1.1.2 Metadata and Self-Describing Components

1.1.3 Friend Assemblies

1.1.4 Global Assembly Cache

1.2 Asynchronous Programming with Async and Await

1.3 Attributes

1.3.1 Attribute Modifier

1.3.2 Serializable

1.3.3 DllImportAttribute

1.3.4 MarshalAsAttribute

1.3.5 Assembly Identity Attributes

1.3.6 Informational Attributes

1.3.7 Assembly Manifest Attributes

1.3.8 Strong Name Attributes

1.3.9 Obsolete

1.3.10 Conditional

1.3.11 Using Multiple Identifiers

1.3.12 Documentation

1.3.13 Caller Info

1.3.14 Visual Basic

1.3.15 Extension

1.4 Reflection

1.5 Dynamic Language Runtime (DLR) And Expresstion Trees

1.6 Language Integrated Query (LINQ)

1.6.1 Queries

1.6.2 Lambda Expressions

1.7 Object-Oriented Programming

1.7.1 Classes and objects

1.7.2 Scope

1.7.3 Access Levels

1.7.4 Class members

1.7.5 Shared Classes and Members

1.7.6 Partial

1.7.7 Anonymous types

1.7.8 Inheritance

1.7.9 Overriding

1.7.10 Overloading

1.7.11 Interfaces

1.7.12 Generics

1.7.13 Delegates

1.7.14 Predicate(Of T) Delegate

1.7.15 Serialization

1.8 Threading

2.Program Structure and Code

2.1 Error Types

2.1.1 Syntax Errors

2.1.2 Run-Time Errors

2.1.3 Logic Errors

2.2 File-Level Programming Elements

2.2.1 Option statements

2.2.2 Imports Statement

2.2.3 Namespace statements

2.3 Early and Late Binding

2.4 Implicit Line Continuation

2.5 Disposing external resources with Garbage Collector

2.6 Component vs. Control

2.7 Naming Conventions

2.8 Layout Conventions

2.9 Commenting Conventions

2.10 Language Guidelines

2.11 Secure Coding Guidelines

2.12 Commenting Guidelines

2.13 Me, My, MyBase, and MyClass

2.13.1 Me

2.13.2 My

2.13.3 MyBase

2.13.4 MyClass

3.Language Reference

3.1 Runtime Library Members

3.1.1 Runtime Classes

3.1.2 Runtime Enums

3.2 COM Interop

3.2.1 Reference COM Objects

3.2.2 Work with ActiveX Controls

3.2.3 API Calls Using Declare

3.2.4 API Calls Using DllImport

3.3 Directives

3.3.1 #Const

3.3.2 #ExternalSource

3.3.3 #If...Then...#Else

3.3.4 #Region

3.3.5 #Disable, #Enable

3.4 Data Types

3.4.1 Types

3.4.2 Arrays

3.4.3 Erase Statement

3.4.4 Collections

3.4.5 Tuples

3.4.6 Type characters

3.5 Type Conversion

3.5.1 Widening and Narrowing Conversions

3.5.2 Implicit and Explicit Conversions

3.5.3 CType

3.5.4 Type.Parse

3.5.5 System.Convert

3.6 String Functions

3.7 Math

3.7.1 Math Functions

3.7.2 Help

3.8 Operators

3.8.1 Operator Precedence in Visual Basic

3.8.2 Arithmetic Operators

3.8.3 Assignment Operators

3.8.4 Comparison Operators

3.8.5 Logical/Bitwise Operators

3.8.6 Concatenation Operators

3.8.7 Bit Shift Operators

3.8.8 Miscellaneous Operators

3.8.9 DirectCast Operator

3.8.10 TryCast Operator

3.9 Parameter List And Arguments

3.9.1 Passing Arguments

3.10 Declaring Elements

3.10.1 Declare Statement

3.10.2 Dim Statement

3.10.3 Const Statement

3.10.4 Enum Statement

3.10.5 Class Statement

3.10.6 Structure Statement

3.10.7 Module Statement

3.10.8 Interface Statement

3.10.9 Function Statement

3.10.10 Sub Statement

3.10.11 Property Statement

3.10.12 Operator Statement

3.10.13 Event Statement

3.10.14 Delegate Statement

3.11 Control Flow

3.11.1 Decision Structures

3.11.2 Loop Structures

3.11.3 Other Control Structures

3.12 Error Handling

3.12.1 Error Statement

3.12.2 On Error Statement

3.12.3 GoTo Statement

3.13 Statements

3.13.1 Call Statement

3.13.2 SyncLock Statement

3.13.3 Exit Statement

3.13.4 Stop Statement

3.13.5 End Statement

3.13.6 End <keyword> Statement

3.13.7 Resume Statement

3.14 XML Tags for Documentation Comments

3.14.1 <c>

3.14.2 <code>

3.14.3 <example>

3.14.4 <exception>

3.14.5 <include>

3.14.6 <list>

3.14.7 <para>

3.14.8 <param>

3.14.9 <paramref>

3.14.10 <permission>

3.14.11 <remarks>

3.14.12 <returns>

3.14.13 <see>

3.14.14 <seealso>

3.14.15 <summary>

3.14.16 <typeparam>

3.14.17 <value>

3.15 XML

3.15.1 Literals

3.15.2 Axis Properties

3.16 Walkthroughs

Click to Download

Compilation And Execution Of .Net

Database Access Types

1.Programming Concepts

1.1 Assemblies

1.1.1 Assembly Contents

1.1.2 Metadata and Self-Describing Components

1.1.3 Friend Assemblies

1.1.4 Global Assembly Cache

1.2 Asynchronous Programming with Async and Await

1.3 Attributes

1.3.1 Attribute Modifier

1.3.2 Serializable

1.3.3 DllImportAttribute

1.3.4 MarshalAsAttribute

1.3.5 Assembly Identity Attributes

1.3.6 Informational Attributes

1.3.7 Assembly Manifest Attributes

1.3.8 Strong Name Attributes

1.3.9 Obsolete

1.3.10 Conditional

1.3.11 Using Multiple Identifiers

1.3.12 Documentation

1.3.13 Caller Info

1.3.14 Visual Basic

1.3.15 Extension

1.4 Reflection

1.5 Dynamic Language Runtime (DLR) And Expresstion Trees

1.6 Language Integrated Query (LINQ)

1.6.1 Queries

1.6.2 Lambda Expressions

1.7 Object-Oriented Programming

1.7.1 Classes and objects

1.7.2 Scope

1.7.3 Access Levels

1.7.4 Class members

1.7.5 Shared Classes and Members

1.7.6 Partial

1.7.7 Anonymous types

1.7.8 Inheritance

1.7.9 Overriding

1.7.10 Overloading

1.7.11 Interfaces

1.7.12 Generics

1.7.13 Delegates

1.7.14 Predicate(Of T) Delegate

1.7.15 Serialization

1.8 Threading

2.Program Structure and Code

2.1 Error Types

2.1.1 Syntax Errors

2.1.2 Run-Time Errors

2.1.3 Logic Errors

2.2 File-Level Programming Elements

2.2.1 Option statements

2.2.2 Imports Statement

2.2.3 Namespace statements

2.3 Early and Late Binding

2.4 Implicit Line Continuation

2.5 Disposing external resources with Garbage Collector

2.6 Component vs. Control

2.7 Naming Conventions

2.8 Layout Conventions

2.9 Commenting Conventions

2.10 Language Guidelines

2.11 Secure Coding Guidelines

2.12 Commenting Guidelines

2.13 Me, My, MyBase, and MyClass

2.13.1 Me

2.13.2 My

2.13.3 MyBase

2.13.4 MyClass

3.Language Reference

3.1 Runtime Library Members

3.1.1 Runtime Classes

3.1.2 Runtime Enums

3.2 COM Interop

3.2.1 Reference COM Objects

3.2.2 Work with ActiveX Controls

3.2.3 API Calls Using Declare

3.2.4 API Calls Using DllImport

3.3 Directives

3.3.1 #Const

3.3.2 #ExternalSource

3.3.3 #If...Then...#Else

3.3.4 #Region

3.3.5 #Disable, #Enable

3.4 Data Types

3.4.1 Types

3.4.2 Arrays

3.4.3 Erase Statement

3.4.4 Collections

3.4.5 Tuples

3.4.6 Type characters

3.5 Type Conversion

3.5.1 Widening and Narrowing Conversions

3.5.2 Implicit and Explicit Conversions

3.5.3 CType

3.5.4 Type.Parse

3.5.5 System.Convert

3.6 String Functions

3.7 Math

3.7.1 Math Functions

3.7.2 Help

3.8 Operators

3.8.1 Operator Precedence in Visual Basic

3.8.2 Arithmetic Operators

3.8.3 Assignment Operators

3.8.4 Comparison Operators

3.8.5 Logical/Bitwise Operators

3.8.6 Concatenation Operators

3.8.7 Bit Shift Operators

3.8.8 Miscellaneous Operators

3.8.9 DirectCast Operator

3.8.10 TryCast Operator

3.9 Parameter List And Arguments

3.9.1 Passing Arguments

3.10 Declaring Elements

3.10.1 Declare Statement

3.10.2 Dim Statement

3.10.3 Const Statement

3.10.4 Enum Statement

3.10.5 Class Statement

3.10.6 Structure Statement

3.10.7 Module Statement

3.10.8 Interface Statement

3.10.9 Function Statement

3.10.10 Sub Statement

3.10.11 Property Statement

3.10.12 Operator Statement

3.10.13 Event Statement

3.10.14 Delegate Statement

3.11 Control Flow

3.11.1 Decision Structures

3.11.2 Loop Structures

3.11.3 Other Control Structures

3.12 Error Handling

3.12.1 Error Statement

3.12.2 On Error Statement

3.12.3 GoTo Statement

3.13 Statements

3.13.1 Call Statement

3.13.2 SyncLock Statement

3.13.3 Exit Statement

3.13.4 Stop Statement

3.13.5 End Statement

3.13.6 End <keyword> Statement

3.13.7 Resume Statement

3.14 XML Tags for Documentation Comments

3.14.1 <c>

3.14.2 <code>

3.14.3 <example>

3.14.4 <exception>

3.14.5 <include>

3.14.6 <list>

3.14.7 <para>

3.14.8 <param>

3.14.9 <paramref>

3.14.10 <permission>

3.14.11 <remarks>

3.14.12 <returns>

3.14.13 <see>

3.14.14 <seealso>

3.14.15 <summary>

3.14.16 <typeparam>

3.14.17 <value>

3.15 XML

3.15.1 Literals

3.15.2 Axis Properties

3.16 Walkthroughs

Click to Download

Compilation And Execution Of .Net

Database Access Types

1.Programming Concepts

1.1 Assemblies

1.1.1 Assembly Contents

1.1.2 Metadata and Self-Describing Components

1.1.3 Friend Assemblies

1.1.4 Global Assembly Cache

1.2 Asynchronous Programming with Async and Await

1.3 Attributes

1.3.1 Attribute Modifier

1.3.2 Serializable

1.3.3 DllImportAttribute

1.3.4 MarshalAsAttribute

1.3.5 Assembly Identity Attributes

1.3.6 Informational Attributes

1.3.7 Assembly Manifest Attributes

1.3.8 Strong Name Attributes

1.3.9 Obsolete

1.3.10 Conditional

1.3.11 Using Multiple Identifiers

1.3.12 Documentation

1.3.13 Caller Info

1.3.14 Visual Basic

1.3.15 Extension

1.4 Reflection

1.5 Dynamic Language Runtime (DLR) And Expresstion Trees

1.6 Language Integrated Query (LINQ)

1.6.1 Queries

1.6.2 Lambda Expressions

1.7 Object-Oriented Programming

1.7.1 Classes and objects

1.7.2 Scope

1.7.3 Access Levels

1.7.4 Class members

1.7.5 Shared Classes and Members

1.7.6 Partial

1.7.7 Anonymous types

1.7.8 Inheritance

1.7.9 Overriding

1.7.10 Overloading

1.7.11 Interfaces

1.7.12 Generics

1.7.13 Delegates

1.7.14 Predicate(Of T) Delegate

1.7.15 Serialization

1.8 Threading

2.Program Structure and Code

2.1 Error Types

2.1.1 Syntax Errors

2.1.2 Run-Time Errors

2.1.3 Logic Errors

2.2 File-Level Programming Elements

2.2.1 Option statements

2.2.2 Imports Statement

2.2.3 Namespace statements

2.3 Early and Late Binding

2.4 Implicit Line Continuation

2.5 Disposing external resources with Garbage Collector

2.6 Component vs. Control

2.7 Naming Conventions

2.8 Layout Conventions

2.9 Commenting Conventions

2.10 Language Guidelines

2.11 Secure Coding Guidelines

2.12 Commenting Guidelines

2.13 Me, My, MyBase, and MyClass

2.13.1 Me

2.13.2 My

2.13.3 MyBase

2.13.4 MyClass

3.Language Reference

3.1 Runtime Library Members

3.1.1 Runtime Classes

3.1.2 Runtime Enums

3.2 COM Interop

3.2.1 Reference COM Objects

3.2.2 Work with ActiveX Controls

3.2.3 API Calls Using Declare

3.2.4 API Calls Using DllImport

3.3 Directives

3.3.1 #Const

3.3.2 #ExternalSource

3.3.3 #If...Then...#Else

3.3.4 #Region

3.3.5 #Disable, #Enable

3.4 Data Types

3.4.1 Types

3.4.2 Arrays

3.4.3 Erase Statement

3.4.4 Collections

3.4.5 Tuples

3.4.6 Type characters

3.5 Type Conversion

3.5.1 Widening and Narrowing Conversions

3.5.2 Implicit and Explicit Conversions

3.5.3 CType

3.5.4 Type.Parse

3.5.5 System.Convert

3.6 String Functions

3.7 Math

3.7.1 Math Functions

3.7.2 Help

3.8 Operators

3.8.1 Operator Precedence in Visual Basic

3.8.2 Arithmetic Operators

3.8.3 Assignment Operators

3.8.4 Comparison Operators

3.8.5 Logical/Bitwise Operators

3.8.6 Concatenation Operators

3.8.7 Bit Shift Operators

3.8.8 Miscellaneous Operators

3.8.9 DirectCast Operator

3.8.10 TryCast Operator

3.9 Parameter List And Arguments

3.9.1 Passing Arguments

3.10 Declaring Elements

3.10.1 Declare Statement

3.10.2 Dim Statement

3.10.3 Const Statement

3.10.4 Enum Statement

3.10.5 Class Statement

3.10.6 Structure Statement

3.10.7 Module Statement

3.10.8 Interface Statement

3.10.9 Function Statement

3.10.10 Sub Statement

3.10.11 Property Statement

3.10.12 Operator Statement

3.10.13 Event Statement

3.10.14 Delegate Statement

3.11 Control Flow

3.11.1 Decision Structures

3.11.2 Loop Structures

3.11.3 Other Control Structures

3.12 Error Handling

3.12.1 Error Statement

3.12.2 On Error Statement

3.12.3 GoTo Statement

3.13 Statements

3.13.1 Call Statement

3.13.2 SyncLock Statement

3.13.3 Exit Statement

3.13.4 Stop Statement

3.13.5 End Statement

3.13.6 End <keyword> Statement

3.13.7 Resume Statement

3.14 XML Tags for Documentation Comments

3.14.1 <c>

3.14.2 <code>

3.14.3 <example>

3.14.4 <exception>

3.14.5 <include>

3.14.6 <list>

3.14.7 <para>

3.14.8 <param>

3.14.9 <paramref>

3.14.10 <permission>

3.14.11 <remarks>

3.14.12 <returns>

3.14.13 <see>

3.14.14 <seealso>

3.14.15 <summary>

3.14.16 <typeparam>

3.14.17 <value>

3.15 XML

3.15.1 Literals

3.15.2 Axis Properties

3.16 Walkthroughs

Click to Download