Home
ASP.Net
Interview FAQs

For most programmers, having a garbage collector (and using garbage collected objects) means that you never have to worry about deallocating memory, or reference counting objects, even if you use sophisticated data structures. It does require some changes in coding style, however, if you typically deallocate system resources (file handles, locks, and so forth) in the same block of code that releases the memory for an object. With a garbage collected object you should provide a method that releases the system resources deterministically (that is, under your program control) and let the garbage collector release the memory when it compacts the working set.
All languages that target the runtime allow you to allocate class objects from the garbage-collected heap. This brings benefits in terms of fast allocation, and avoids the need for programmers to work out when they should explicitly free each object.

The CLR also provides what are called ValueTypes—these are like classes, except that ValueType objects are allocated on the runtime stack (rather than the heap), and therefore reclaimed automatically when your code exits the procedure in which they are defined. This is how "structs" in C# operate.

Managed Extensions to C++ lets you choose where class objects are allocated. If declared as managed Classes, with the __gc keyword, then they are allocated from the garbage-collected heap. If they dont include the __gc keyword, they behave like regular C++ objects, allocated from the C++ heap, and freed explicitly with the "free" method.

Machine.Config:
1. This is automatically installed when you install Visual Studio. Net.
2. This is also called machine level configuration file.
3. Only one machine.config file exists on a server.
4. This file is at the highest level in the configuration hierarchy.

Web.Config:
1. This is automatically created when you create an ASP.Net web application project.
2. This is also called application level configuration file.
3. This file inherits setting from the machine.config

It is an optional XML File which stores configuration details for a specific ASP.Net web application.
Configuration files are used to control and manage the behavior of a web application.

1. Machine.config
2. Web.config

By default ASP.Net web application has only one web.config. but in sub folder you can create one web.cofing per sub folder to set configuration of that folder.

eg. - if your web application have 3 folder then 4 web.config can be in your web application

The .Net Framework provides an extensive system of types that allow you to store, manipulate and pass values between members of your application. The .Net Framework is strongly typed, meaning that objects of one type cannot be freely exchanged with objects from another type. Implicit and explicit conversions allow you to convert data types when necessary.

.Net data types can be broken down into the following subcategories:

1. Integer types
2. Floating-Point Types
3. Non-Numeric data types such as:
       Boolean
       Char
       String
       Object

Exceptions represent a breach of an implicit assumption made within code. For example, if your code tries to access a file that is assumed to exist, but the file is missing, an exception would be thrown. However, if your code does not assume that the file exists and checks for its presence first, this scenario would not necessarily generate an exception.

Exceptions are not necessarily errors. Whether or not an exception represents an error is determined by the application in which the exception occurred. An exception that is thrown when a file is not found may be considered an error in one scenario, but may not represent an error.

No you cannot. The .Net Framework must be installed in the machine on which you want to run .Net Application .
PreviousDisplaying 4 of 46Next
Need Help? Contact Us.

Log in

*
*

Forgot password?

*

New User

*
*
*
*