Visual Basic Dot Net Homework Help, Assignment Help, Online Tutor, Tutoring

Submit Assignment

Payment Online Assignment Help

Asp dot net Project Homework

Homework Help

sfsf

Visual Basic Dot Net

Introduction

One of the primary goals of Visual Basic® .NET is to perform faster than previous versions. But performance still depends on how you design your program. This article describes some important considerations that can help you optimize your application's performance. The remainder of this introduction reviews the conditions and assumptions underlying these optimization recommendations.

Intermediate Language

Visual Basic .NET and C#™ both compile to Microsoft intermediate language (MSIL). Equivalent source code in the two languages usually compiles to the same MSIL code and results in the same performance for your application. Performance should not be a criterion in choosing between the two languages.

Execution Frequency

Some of the recommendations in this article might represent a negligible difference within one statement, but the performance gain can be greatly amplified inside a loop or a frequently called procedure. Therefore, code blocks that are executed many times are good candidates for optimization.

Bottlenecks

The most productive approach to optimization is to identify the bottlenecks, or slow places, in your application and work to improve them. Common bottlenecks are long loops and accesses to databases. Micro-optimizing every expression and procedure call is not an efficient use of development effort.

Application Dependency

Performance is highly dependent on the characteristics of each individual application. There are no guarantees. The recommendations in this article are guidelines only. It is possible that you might need to make some adjustments to optimize your particular application.

Platform

Visual Studio® .NET is optimized for the recommended system hardware configuration, both for the integrated development environment (IDE) and for the runtime. If you have less than the recommended amount of RAM, your performance is likely to suffer. This is especially true if you are running large or multiple applications.

Testing Conditions

Some specialized testing for this article was performed using Visual Studio .NET 2002 on Microsoft® Windows® 2000 Professional, running on a 600 MHz Pentium III with 256 MB of RAM. The specialized testing consisted of tight loops that did nothing more than exercise the code elements being compared. In other words, the loops contained the code elements and nothing else. Therefore, the timing differences represent the most extreme cases, and you should not expect such large differences in a normal application.

Preliminary Information

This article is based on preliminary information. The recommendations are subject to change as experience provides updated and more refined information. Also, some of the underlying considerations might change in future releases.