Dot Net Complete

C Programming Topic wise learning

2009-07-28T18:29:00.000-07:00

Learning C programming is generally a primary target for any technical student and here is an attempt to organize it topic wise. It will help the process of learning the c Programming.

INTRODUCTION TO C PROGRAMMING

Programming with C an introduction part two

Data types for C programming

C PROGRAMMING CHARACTER SET

CONSTANTS IN C PROGRAMMING

PROGRAMMING C VARIABLES

C PROGRAM INSTRUCTIONS

COMPILATION AND EXECUTION OF C PROGRAM

C PROGRAMMING RULES PART ONE

C PROGRAMMING RULES PART TWO

COMPILATION AND EXECUTION OF C PROGRAM

INSTRUCTIONS TO WRITE C PROGRAM

ARITHMETIC INSTRUCTIONS TO WRITE C PROGRAM

CONVERSION OF CONSTANTS IN C PROGRAM

PRIORITY OF AR THEMATIC OPERATIONS IN C

OPERATORS ASSOCIATIVITY IN C

IF STATEMENT

MULTIPLE STATEMENTS IN IF

IF AND ELSE

NESTED IF AND ELSE

BREAK

CONTINUE AND DO WHILE IN C LANGUAGE

SWITCH IN C PROGRAMMING

FUNCTIONS IN C PROGRAMMING

Functions and usage in C part two

Coding in C functions

OTHER PROGRAMMING COURSES:

Dot Net Complete Course Part one and two

ASP.NET part one and two

Programming with C and C Sharp

Interview Questions in dot net

asp.net part one part two

Software Testing Complete course part one two and Interview Questions

XML Parsing

2008-12-23T03:33:00.000-08:00

A parser for a programming language knows only that one programming language. to parse a program, the parser has to consult the grammar of the language. But XML parsers are different on both counts. The same parser can do all XML languages, and, to parse a document, the parser does not need to know the grammar of its markup language. A general XML requirement is that the elements of an XML document must form a tree and that the tree structure of elements must be clearly shown in markup.

Tree conditions must be met in XML parsing is

There must be an element that contains all other elements. This is the root of the element tree .
Start and end tags must be properly nested; overlapping elements are not allowed.
All elements, including empty elements, must have both the start tag and the end tag.

All the parser needs to construct the syntactical tree is a stack to push a start tag on and pop it off when the matching end tag is found. If in the end the stack is empty, the document is well formed.

Procedure :

Start by creating the root node and make it the current node.
When a start tag is encountered, create a child of the current node and make it the current node. Put the start tag name on stack.
When an end tag is encountered, check to see that its tag name is the same as the name on top of the stack. If it is not the same, declare failure and exit. If it is the same, close the current node (that is, pop the tag name off the stack) and make its parent the current node.
If in the end the stack is empty, declare success, and return the tree. If it is not empty, declare failure and exit.

XML parsers within XML-aware browsers follow this procedure.

Why Is XML Great ?

1. XML makes it easy to agree on a common language or data format. A common language is the main prerequisite for cooperation.

2. Iit is very easy to switch between the linear text and the syntax tree view of an XML document. XML parsers are standard, high quality, ubiquitous, and free, and they can perform the switch both ways without any loss of significant information.

3. With XML, it is easy to construct networks of cooperating computer programs that receive XML text over the network, parse it into its internal representation, perform some computations on it, convert it back into linear text and send it over the network to another program for further processing.

4. XML is a major enabling technology for cooperation, both between human agents and between computer programs (interoperability).

Problems with programming language parsers :

Parsers for programming languages are difficult to write.
The resulting binary objects are parser and platform specific.
Transition from binary to textual form (disassembly) is hard and frequently illegal; certainly, no standard APIs are available for doing that.

But simple XML parsers that only check for well-formedness and construct a syntax tree are easy to write, and their output is standard, platform independent, and easy to convert back to linear text form.(28)

The previous post is about the introduction of XML.

Software Testing Topics

Recovery testing technique Execution testing Structural software testing Static and dynamic testing Functional and structural testing Testing verification and validation Test Process Independent Software Testing and part two Testing metrics and Life cycle testing c programming break statement Compliance software testing V model Software Testing

Other Programming Courses :

ASP.NET part one and two
Programming with C and C Sharp
Dot Net Complete Course Part one and two
Interview Questions in dot net and asp.net part one part two
Software Testing Complete course part one and two
Interview Questions in software Testing

Thank you for visiting PROGRAMMING BLOG. If you liked the post, please subscribe to my blog via email or RSS FEED.You can contact me here for any specific feed back .

COMMENT HERE and thank you for sparing your valuable time.

I will be very glad if you share this page on your social book marking site with the below link.

What is XML ?

2008-12-21T03:15:00.000-08:00

XML stands for eXtensible Markup Language is not really a language but a framework for defining and using markup languages. Markup languages are used for creating units of information called XML documents, which have two standard representations: as a linear text with markup and as a tree data structure.

A tree is a connected set of nodes and a parent-child relationship defined on them. One special node is called the root. Every node except the root has exactly one parent node, and the root is the only node that doesn’t have a parent.

Trees are always drawn upside down, with the root on top and leaves at the bottom. If you start from any node that is not a root, go up to its parent, and continue up the tree, sooner or later you get to the root.

The nodes you encounter along the way are called the ancestors of the node you started from. The root is an ancestor of all nodes in the tree, and all nodes in the tree are its descendants. If node P is the parent of node C, then C is usually called a child of P. Children of the same node are called siblings. Nodes that have no children are called leaves.

A program that takes a text and checks the correctness of its syntax is called a parser. A parser does not simply return a Boolean answer (“correct” or “not correct”): if the text is grammatically correct, it builds an internal representation of its syntactical structure. Such internal representations are called syntax diagrams. For XML documents (as well as computer programs), syntax diagrams form a tree structure.

An XML document consists of text data and markup. The markup indicates the syntactical structure of the document.

This XML document contains three elements: encounter, greeting, and response. Here is the greeting element.An element consists of a start tag, the element’s content (which can be empty), and an end tag. A start tag minimally consists of the “<” character, a tag name, and the “>” character. The tag name can be followed by attribute declarations. An end tag consists of the character sequence “

An element consists of a start tag, the element’s content (which can be empty), and an end tag. A start tag minimally consists of the “<” character, a tag name, and the “>” character. The tag name can be followed by attribute declarations. An end tag consists of the character sequence “

What is the tree structure of the document shown . In XML, the parent-child tree relationship corresponds to how elements are nested within each other in the linear text. In our example, encounter properly contains greeting and response; therefore, in the tree, encounter is the parent of greeting and response, whereas greeting and response are children of encounter and siblings to each other. Leaf elements are either empty or contain only text. (24.5)
Previous post deals with ASP.NET.

Related Posts

Recovery testing technique Execution testing Structural software testing Static and dynamic testing Functional and structural testing Testing verification and validation Test Process
Independent Software Testing and part two Testing metrics and Life cycle testing
c programming break statement Compliance software testing V model Software Testing

Other Programming Courses :

ASP.NET part one and two
Programming with C and C Sharp
Dot Net Complete Course Part one and two
Interview Questions in dot net and asp.net part one part two
Software Testing Complete course part one and two
Interview Questions in software Testing

Thank you for visiting PROGRAMMING BLOG. If you liked the post, please subscribe to my blog via email or RSS FEED.You can contact me here for any specific feed back .

COMMENT HERE and thank you for sparing your valuable time.

I will be very glad if you share this page on your social book marking site with the below link.

ASP.NET INTRODUCTION

2008-09-09T09:15:00.000-07:00

Unlike the ASP runtime, ASP.NET uses the Common Language Runtime (CLR) provided by the .NET Framework. The CLR is the .NET runtime, which manages the execution of code. The CLR allows the objects, which are created in different languages, to interact with each other and hence removes the language barrier. CLR thus makes Web application development more efficient.

In addition to simplifying the designing of Web applications, the .NET CLR offers many advantages. Some of these advantages are listed as follows.

Improved performance:

The ASP.NET code is a compiled CLR code instead of an interpreted code. The CLR provides just-in-time compilation, native optimization, and caching. Here, it is important to note that compilation is a two-stage process in the .NET Framework. First, the code is compiled into

the Microsoft Intermediate Language (MSIL).

Then, at the execution time, the MSIL is compiled into native code. Only the portions of the code that are actually needed will be compiled into native code. This is called Just In Time compilation. These features lead to an overall improved performance of ASP.NET applications.

Flexibility:

The entire .NET class library can be accessed by ASP.NET applications. You can use the language that best applies to the type of functionality you want to implement, because ASP.NET is language independent.

Configuration settings:

The application-level configuration settings are stored in an Extensible Markup Language (XML) format. The XML format is a hierarchical text format, which is easy to read and write. This format makes it easy to apply new settings to applications without the aid of any local administration tools.

Security:

ASP.NET applications are secure and use a set of default authorization and authentication schemes. However, you can modify these schemes according to the security needs of an application.

In addition to this list of advantages, the ASP.NET framework makes it easy to migrate from ASP applications.

Creating an ASP.NET Application

Use a text editor:

In this method, you can write the code in a text editor, such as Notepad, and save the code as an ASPX file. You can save the ASPX file in the directory C:inetpubwwwroot. Then, to display the output of the Web page in Internet Explorer, you simply need to type http://localhost/.aspx in the Address box. If the IIS server is installed on some other machine on the network, replace "localhost" with the name of the server. If you save the file in some other directory, you need to add the file to a virtual directory in the Default WebSite directory on the IIS server. You can also create your own virtual directory and add the file to it.

Use the VS.NET IDE:

In this method, you use the IDE of Visual Studio .NET to create a Web page in a WYSIWYG manner. Also, when you create a Web application, the application is automatically created on a Web server (IIS server). You do not need to create a separate virtual directory on the IIS server.

From the preceding discussion, it is obvious that the development of ASP.NET Web applications is much more convenient and efficient in Visual Studio .NET.

ASP.NET Web pages consist of HTML text and the code. The HTML text and the code can be separated in two different files. You can write the code in Visual Basic or C# . This separate file is called the code behind file. In this section, you'll create simple Web pages by using VB as well as C#.

Before you start creating a Web page, you should be familiar with basic ASP.NET syntax. At the top of the page, you must specify an @ Page directive to define page specific attributes, such as language.

To specify the language as VB for any code output to be rendered on the page.

This line indicates that any code in the block, <% %>, on the page is compiled by using VB.

To render the output on your page, you can use the Response.Write() method.

Creating a Visual Basic Web Application

You can create an ASP.NET application using Visual Basic by creating a Visual Basic

Web Application project. To do so, complete the following steps:

1. Select File ® New ® Project. The New Project dialog box appears.

2. Select Visual Basic Projects from the Project Types pane.

3. Select ASP.NET Web Application from the Templates pane. The Name box contains a default name of the application. The Location box contains the name of a Web server where the application will be created. However, you can change the default name and location. In this case, the name of the sample application is SampleVB.

Deploying an ASP.NET Web Application

After creating and testing your ASP.NET Web applications, the next step is deployment.

Deployment is the process of distributing the finished applications (without the source code) to be installed on other computers.

In Visual Studio .NET, the deployment mechanism is the same irrespective of the programming language and tools used to create applications. In this section, you'll deploy the "Hello World" Web application that you created. You can deploy any of the application that was created by using VB or C#. Here, you'll deploy the application created by using VB. To do so, follow these steps:

1. Open the Web application project that you want to deploy. In this case, open the SampleVB project.

2. Select File ® Add Project ® New Project to open the Add New Project dialog box.

3. From the Project Types pane, select Setup and Deployment Projects.

From the Templates pane, select Web Setup Project.

4. Change the default name of the project. In this case, change it to "SampleVBDeploy."

5. Click OK to complete the process. The project is added in the Solution Explorer window.

Assemblies in Dot Net

2008-09-09T04:17:00.000-07:00

Assemblies are the fundamental building blocks of a .NET Framework application. They contain the types and resources that make up an application and describe those contained types to the common language runtime. Assemblies enable code reuse, version control, security, and deployment.
Put simply, an assembly is a project that compiles to an EXE or a DLL file. Although .NET EXE and DLL files resemble their predecessors externally, the internal structure of an assembly is quite different from that of an EXE or DLL created with earlier development tools. An assembly consists of four internal parts:
The assembly manifest, or metadata. This contains information about the assembly that the common language runtime uses to obtain information about the assembly. The type metadata, which exposes information about the types contained within the assembly.
The intermediate language code for your assembly.
Resource files, which are non-executable bits of data, such as strings or images for a specific culture. The assembly manifest contains the metadata that describes the assembly to the common language runtime. The common language runtime then uses the information in the assembly manifest to make decisions about the assembly's execution. An assembly manifest contains the following information: Identity.
It contains the name and version number of the assembly, and can contain optional information such as locale and signature information. Types and resources. It contains a list of all the types that will be exposed to the common language runtime as well as information about how those types can be accessed. Files: It contains a list of all files in the assembly as well as dependency information for those files. Security permissions
The manifest describes the security permissions required by the assembly. If the permissions required conflict with the local security policy, the assembly will fail to execute. For the most part, the developer does not have to be concerned with the contents of the assembly manifest. It is compiled and presented to the common language runtime automatically. The developer does, however, need to explicitly set the metadata that describes the identity of the assembly. The identity of the assembly is contained in the AssemblyInfo.vb or .cs file for your project. You can set identity information for your assembly by right-clicking the AssemblyInfo icon and choosing View Code from the drop-down menu. The code window will open to the AssemblyInfo code page, which contains default null values for several assembly identity attributes. The following code example shows an excerpt from the AssemblyInfo file.
Creating Class Library Assemblies
You will frequently want to create class library assemblies. These represent sets of types that can be referenced and used in other assemblies. For example, you might have a custom control that you want to use in several applications or a component that exposes higher math functions. Such an assembly is not executable itself, but rather must be referenced by an executable application to be used. You can create class library assemblies and control library assemblies by using the templates provided by Microsoft Visual Studio .NET.
The class library template is designed to help you create an assembly of types that can be exposed to other applications, and the Microsoft Windows control library template is provided to assist you in building assemblies of custom controls.
Creating Resource Files
The .NET Framework includes a sample application called ResEditor that can be used for creating text and image resource files. The ResEditor application is not integrated with Visual Studio .NET-it must be run separately. In fact, it is supplied as source code files and must be compiled before it can be used.
The ResEditor source files are located in the FrameworkSDKSamplesTutorialsresourcesandlocalizationreseditor folder, which is in the folder that Visual Studio .NET is installed in. You can build the application using either the batch file supplied in that folder or by adding the source files to an empty Visual Studio project, configuring, and then building them.
Embedding Resources
Once you have created resource files, you can embed them in your assembly. This allows you to package resources into the same assembly as the code files, thus increasing the portability of your code and reducing its dependence on additional files. To embed an externally created resource into your assembly, all you have to do is add the file to your project. When the project is built, the resource file will be compiled into the assembly.
Creating Resource Assemblies
You can create assemblies that only contain resources. You might find this useful in situations where you expect to have to update the data contained in resource files, but do not want to have to recompile your application to update it.
Creating Satellite Assemblies
When creating international applications, you might want to provide different sets of resources for different cultures. Satellite assemblies allow different sets of resources to automatically be loaded based on the CurrentUICulture setting of the thread. You learned how to automatically generate applications for localization in Chapter 8. In this section, you will learn how to create additional satellite assemblies and incorporate them into your application.
Visual Studio .NET allows you to effortlessly create satellite assemblies. All you need to do to create a satellite assembly is to incorporate alternate sets of resource files that are appropriately named into your application. Visual Studio .NET does the rest upon compilation.
To be incorporated into a satellite assembly, your resource file must follow a specific naming scheme based on the culture it is designed for. The name of a resource file for a specific culture is the same as the name of the resource file for the invariant culture, and the culture code is inserted between the base name and the extension. Thus, if we had a resource file named MyResources.resx, a resource file containing alternate resources for neutral German UIs would be named MyResources.de.resx. And a version of the file containing German resources specific for Luxembourg would be named MyResources.de-LU.resx.
Once these alternate versions of the file are added to your solution, they will automatically be compiled by Visual Studio .NET into satellite assemblies, and a directory structure for them will be created. At run time, the culture-specific resources contained in these files will automatically be located by the common language runtime.
Retrieving Resources at Run Time
At run time, you can use the ResourceManager class to retrieve embedded resources. A ResourceManager, as the name implies, manages access and retrieval of resources embedded in assemblies. Each instance of a ResourceManager is associated with an assembly that contains resources.
You can create a ResourceManager by specifying two parameters: the base name of the embedded resource file and the assembly in which that file is found. The new ResourceManager will be dedicated to the embedded resource file that you specify. The base name of the file is the name of the namespace that contains the file and the file without any extensions.
The assembly parameter refers to the assembly that the resource file is located in. If the assembly that contains the resources is the same assembly that contains the object that is creating the ResourceManager, you can get a reference to the assembly from the type object of your object.
Understanding Private and Shared Assemblies
Most of the assemblies you create will be private assemblies. Private assemblies are the most trouble free for developers and are the kind of assembly created by default. A private assembly is an assembly that can be used by only one application. It is an integral part of the application, is packaged with the application, and is only available to that application. Because private assemblies are used by one application only, they do not have versioning or identity issues. Up to this point, you have only created private assemblies.
When you add a reference to a private assembly to your project, Visual Studio .NET creates a copy of the DLL containing that assembly and writes it to your project folder. Thus, multiple projects can reference the same DLL and use the types it contains, but each project has its own copy of the DLL and therefore has its own private assembly.
Only one copy of shared assemblies, on the other hand, is present per machine. Multiple applications can reference and use a shared assembly. You can share an assembly by installing it to the Global Assembly Cache. There are several reasons why you might want to install your assembly to the Global Assembly Cache. For example:
Shared location. If multiple applications need to access the same copy of an assembly, it should be shared.
Security. The Global Assembly Cache is located in the C:WINNT (Microsoft Windows 2000) or WINDOWS (Microsoft Windows XP) folder, which is given the highest level of security by default.
Side-by-side versioning. You can install multiple versions of the same assembly to the Global Assembly Cache, and applications can locate and use the appropriate version.
For the most part, however, assemblies that you create should be private. You should only share an assembly when there is a valid reason to do so. Sharing an assembly and installing it to the Global Assembly Cache requires that your assembly be signed with a strong name.

c sharp and vb.net a compariosn

2008-09-08T04:04:00.000-07:00

Advantages VB.NET:

Has support for optional parameters which makes COM interoperability much easy.

With Option Strict off late binding is supported.Legacy VB functionalities can be used by using Microsoft.VisualBasic namespace.

Has the WITH construct which is not in C#.

The VB.NET part of Visual Studio .NET compiles your code in the background.

While this is considered an advantage for small projects, people creating very large projects have found that the IDE slows down considerably as the project gets larger.

Advantages of C#

XML documentation is generated from source code but this is now been incorporated in Whidbey.

Operator overloading which is not in current VB.NET but is been introduced in Whidbey.

Use of this statement makes unmanaged resource disposal simple.

Access to Unsafe code. This allows pointer arithmetic etc, and can improve performance in some situations. However, it is not to be used lightly, as a lot of the normal safety of C# is lost (as the name implies).This is the major difference that you can access unmanaged code in C# and not in VB.NET.

System exceptions and application exceptions:

All exception derives from Exception Base class. Exceptions can be generated programmatically or can be generated by system. Application Exception serves as the base class for all application specific exception classes. It derives from Exception but does not provide any extended functionality.

You should derive your custom application exceptions from Application Exception. Application exception is used when we want to define user defined exception, while system exception is all which is defined by .NET.

Preventing de compilation of dot net DLL:

By design .NET embeds rich Meta data inside the executable code using MSIL. Any one can easily decompile your DLL back using tools like ILDASM (owned by Microsoft) or Reflector for .NET which is a third party. Secondly there are many third party tools which make this decompiling process a click away.

So any one can easily look in to your assemblies and reverse engineer them back in to actual source code and understand some real good logic which can make it easy to crack your application.

The process by which you can stop this reverse engineering is using "obfuscation". It's a technique which will foil the decompilers. There are many third parties (XenoCode, Demeanor for .NET) which provide .NET obfuscation solution. Microsoft includes one that is Dotfuscator Community Edition with Visual Studio.NET.

asp.net Validation Controls

2008-08-26T05:45:00.000-07:00

A validation control enables us to validate an input and display an error message if necessary. It is very much like other server-side controls with certain additional methods and properties. First, the server treats it as an invisible control.

After the user has entered erroneous data, it becomes visible. It is a powerful, rapid application development feature; however, a developer needs to understand its behavior and the methods thoroughly before he or she can appreciate it.

There are certain rough edges in the Beta 2 version, which hopefully will be polished in the final product.The best strategy to learn the family of controls is to learn them one at a time, and finally to apply the summary validation.

Various types of validation controls are as follows:

1. RequiredFieldValidator Checks if the input control has any value.
2. RegularExpressionValidator Checks the value against a regular expression (pattern).
3. CompareValidator Checks if the value is acceptable compared to a given value or compared to the content of another control.
4. RangeValidator Checks if the input control’s value is within a specified range.
5. CustomValidator Allows you to develop custom validation.
6. ValidationSummary Reports a summary of all errors.

By default, each of the validation controls performs the validation task at the client-side as well as at the server-side. Except for the RequiredFieldValidator, all other validation controls treat an empty field as a valid field.Therefore, we will need to apply a RequiredFieldValidator to every input field that we want to validate.

You can attach more than one validation control to an input.

For example we may use a RequiredFieldValidator and a RangeValidator to ensure that an input
is not empty and falls within a specified range.

There are a number of common properties in these controls.The major ones are:

1. ErrorMessage In case of an error, the system displays this message at the location of the control, and in the summary report, if any.

2. Display A validation control is kept invisible until a bad input is entered. In case of a bad input, the system has to display the error message.

The display mechanism can be handled in one of three ways.

1. Display= “static” Initially, enough room in the page is reserved for the expected error message.

2. Display= “dynamic” No room is initially reserved. In case of an error, the message is displayed by displacing existing contents of the page.

3. Display=“none” The message won’t be displayed at the location of the control; however, it will be reported in the summary report, if any.

PROGRAMMING WITH ASP.NET PART TWO

2008-08-24T09:35:00.001-07:00

This is the series of posts which discuss the advanced topics of active server pages.
The initial list of asp basics part one can be learned here.The present list is the second part of the asp series which will give detailed insight of asp.net.

Here is the list of different topics of asp.

CREATING ASSEMBLIES WITH ASP.NET

BUILDING HANDLERS IN ASP.NET

INTERFACES AND CLASSES CREATION IN ASP.NET

CACHING IN ASP.NET

CACHING IN ASP.NET PART TWO

WIRE LESS APPLICATION WITH ASP.NET

SECURITY IN ASP.NET PART ONE

SECURITY IN ASP.NET PART TWO

LOCALIZING ASP.NET APPLICATIONS

DEPLOYING ASP.NET APPLICATIONS

ASP.NET CONFIGURATION SYSTEM

WEB SERVICES IN ASP.NET

WEB SERVICES PART TWO

WEB SERVICE INFRASTRUCTURE

WEB SERVICE INFRASTRUCTURE PART TWO

EXCHANGING MESSAGES IN ASP.NET

MICROSOFT HAIL STORM

SOAP AND DOT NET PART ONE

SOAP AND DOT NET PART TWO

Wish you a wonderful reading and gaining of the knowledge and further comments to improve the site are most welcome.

asp.net complete

2008-08-23T09:05:00.001-07:00

This is the list of ASP.NET and related posts where you can learn the concept completely topic by topic.

Here you can find every thing regarding ASP.NET right from basics to most advanced concepts.

You can also have a look at complete concepts like

Interview Questions and Answers on concept of ASP.NET and Frame work here.

Here is the ASP.NET concepts.

ASP.NET INTRODUCTION

BUILDING FORMS WITH WEB CONTROLS PART ONE

BUILDING FORMS WITH WEB CONTROLS PART TWO

TABLE CONTROL AND EVENTS IN ASP.NET

JDBC AND ODBC

WEB CONTROLS IN ASP.NET

CUSTOM CONTROLS IN ASP.NET

VALIDATING USER INPUTS

DEBUGGING ASP.NET PAGES

DEBUGGING PART TWO

DATA BINDING IN ASP.NET PART ONE

DATA BINDING IN ASP.NET PART TWO

DATA BINDING IN ASP.NET AND XML PART ONE

DATA BINDING IN ASP.NET AND XML PART TWO

WORKING WITH DATA GRIDS IN ASP

USING TEMP LETS IN ASP.NET

DATA GRID CONTROL IN ASP

SQL SERVER AND ASP.NET

STORED PROCEDURES IN SQL SERVER

ASP.NET CONFIGURATION

DEVELOPMENTS OF BUSINESS OBJECTS FOR ASP

ADO.NET INTRODUCTION

ADO.NET OBJECT MODEL

COMMUNICATION WITH DATA BASE SOURCES

ASP.NET INTERVIEW QUESTIONS AND ANSWERS

2008-08-22T19:14:00.000-07:00

Questions and Answers dot net basics

2008-08-22T11:38:00.000-07:00

This is the list of interview questions and answers for microsoft dot net technology.

This series includes questions and detailed answers on basic concepts of dot net like the functioning and architecture of the new technology.

Here is the list.

DOT NET BASIC CONCEPTS PART ONE

DOT NET BASIC CONCEPTS PART TWO

DOT NET BASIC CONCEPTS PART THREE

C SHARP BASICS

ADO.NET BASICS

ADO.NET BASICS PART TWO

ADO.NET BASICS PART THREE

ADO.NET QUESTIONS AND ANSWERS PART FOUR

ADO.NET QUESTIONS AND ANSWERS PART FIVE

ADO.NET PART SIX

DOT NET REAL TIME QUESTIONS

ASP.NET BASIC QUESTIONS PART ONE

ASP.NET INTERVIEW QUESTIONS PART TWO

FAQ'S ON DATA SET

IIS

EVENT HANDLING QUESTIONS AND ANSWERS

BOX CONTROLS

WINFORM APPLICATIONS

DOT NET REAL TIME QUESTIONS AND ANSWERS PART ONE

DOT NET REAL TIME QUESTIONS AND ANSWERS PART TWO

DOT NET REAL TIME QUESTIONS AND ANSWERS PART THREE

DOT NET COMPLETE COURSE PART TWO

2008-08-22T04:21:00.000-07:00

This is in continuation with DOT NET COURSE PART ONE 21 DAYS.This deals with the further aspects of Microsoft dot net technology like assemblies,data and application accessing,configuring and optimizing a web application using the dot net technology.

DAY 22 BINDING ,VIEWING AND FILTERING DATA IN DOT NET,

DAY 23 XML IN ADO.NET

DAY24 GDI

DAY25 AUTHORING CONTROLS IN DOT NET

DAY 26 COMMON TASKS AND CONTROLS IN DOT NET

DAY 27 PRINT FUNCTIONALITY IN DOT NET

DAY 28 ACCESSING AND INVOKING COMPONENTS IN DOT NET

DAY29 IMPLEMENTING ACCESSIBILITY

DAY 30 HELP IMPLEMENTATION IN DOT NET

DAY 31 GLOBALIZATION AND LOCALIZATION

DAY 32 ASSEMBLIES OVER VIEW

DAY 33 OPTIMIZING APPLICATION IN DOT NET

DAY 34 SECURITY IN DOT NET APPLICATION

DAY 35 DEPLOYMENT OF DOT NET APPLICATION

DAT 36 CONFIGURING SET UP PROJECT IN DOT NET

DOTNET COMPLETE COURSE PART ONE

2008-08-22T03:56:00.000-07:00

This is the twenty one days Microsoft dot net course for a beginner.If you are all ready an expert and looking for a particular topic then browse for it and get the knowledge in depth and understanding.

Here is the list.

DAY 1 MICROSOFT DOT NET FRAME WORK

DAY 2 MICROSOFT DOT NET BASE CLASS LIBRARY

DAY 3 MICROSOFT DOT NET CLASSES AND STRECTURES

DAY 4 METHODS IN FRAME WORK

DAY 5 INPUT VALIDATIONS IN DOT NET PART ONE

DAY 6 INPUT VALIDATIONS IN DOT NET PART TWO

DAY 7 DATA TYPES IN DOT NET

DAY 8 DATA TYPES IN DOT NET PART TWO

DAY 9 IMPLEMENTING PROPERTIES IN DOT NET

DAY 10 DELEGATES AND EVENTS

DAY 11 OOPS INTRODUCTION

DAY 12 POLYMORPHISM

DAY 13 INHERITANCE AND POLYMORPHISM

DAY 14 EBUGGING TOOLS IN DOT NET

DAY 15 DEBUG AND TRACE IN CLASSES

DAY 16 UNIT TEST PLAN

DAY 17 EXCEPTIONS IN VISUAL STUDIO

DAY 19 ADO.NET INTRODUCTION

DAY 20 DATA ACCESSING IN DOT NET

DAY 21 DATA BASE OBJECTS

On MOVE

2008-08-12T00:35:00.000-07:00

This blog is further going to be published at

http://www.testingcorner.net

And its feed is avilable at

http://www.testingcorner.net/feeds/posts/default

This integration makes the blog more compernhensive with avilability of SOFTWARE TESTING,JAVA AND MICROSFT DOT NET.

To be honest to say it makes my passion towarrds the blogging more interasting.

Thanks alot for all the visiting my blog and i expect the same at the new blog

http://www.testingcorner.net