Posted by : Rhyf Ahmad Wednesday, May 13, 2015

You started with a quick jump straight into getting your hands on Visual Studio. Most developers want to feel something, but before you start diving into syntax this chapter is going to take a look at the bigger picture of how .NET runs in relation to the operating system (OS). While at really low levels for graphics some implementations of the common language runtime (CLR) and the OS may be indistinguishable, at its core the CLR provides the environment in which your application runs.

The architects of .NET realized that all procedural languages require certain base functionality. For example, many languages ship with their own runtime that provides features runtime implementation, all languages used a common runtime? This would provide languages with a standard environment and access to all of the same features. This is exactly what the CLR provides. The CLR manages the execution of code on the .NET platform. Its common features provide support for many advanced features, including operator overloading, implementation inheritance, threading, and the ability to marshal objects. Building such features is not trivial. The CLR enabled Microsoft to concentrate on building this plumbing one time and then reuse it across different programming languages. As a result the runtime environment used by Visual Basic is the equal of every other .NET language, with the CLR eliminating many of the shortcomings of the previous versions of Visual Basic. Visual Basic developers can view the CLR as a better Visual Basic runtime. However, this runtime, unlike the old standalone Visual Basic runtime, is common across all of .NET regardless of the underlying operating system. Thus, the functionality exposed by the CLR is available to all .NET languages; more important, all of the features available to other .NET languages via the CLR are available to Visual Basic developers. Additionally, as long as you develop using managed code — code that runs in the CLR — you’ll find that it doesn’t matter whether your application is installed on a Windows XP client, a Vista client, or a Windows 7 client; your application will run. The CLR provides an abstraction layer separate from the details of the operating system.


Framework Profiles and Platforms
  1. Client and Full Framework Profiles
  2. Framework for Metro
  3. Silverlight, Windows Phone, and Others
  4. .NET 4.5 Portable Class Library

Elements of a .NET Application
  1. Types
  2. Modules
  3. Assemblies

Cross-Language Integration
  1. The Common Type System
  2. Metadata
  3. The Refl ection API

IL Disassembler
Memory Management
  1. Traditional Garbage Collection
  2. Faster Memory Allocation for Objects
  3. Garbage Collector Optimizations

  1. What Is a Namespace?
  2. Namespaces and References
  3. Common Namespaces
  4. Importing and Aliasing Namespaces
  5. Aliasing Namespaces
  6. Referencing Namespaces in ASP.NET

Creating Your Own Namespaces
The My Keyword
  1. My.Application
  2. My.Computer
  3. My.Resources
  4. My.User

Extending the My Namespace 

Ebook Preview
Get the ebook now (1.58 MB)

If the link above doesn't work, try the link below

Mirror: Get the ebook now (1.58 MB)

Leave a Reply

You can leave a comment to request any article(s), software(s), ebook(s) or report the dead link.
Then I will reply as soon as I can :)

Subscribe to Posts | Subscribe to Comments

Welcome to My Blog

Recent Post

Recent Posts Widget

- Copyright © Madriva -Robotic Notes- Powered by Blogger - Designed by Johanes Djogan -