How many languages .NET is supporting now?
When .NET was introduced it came with several languages.
VB.NET, C#, COBOL and Perl, etc. 44 languages are
How is .NET able to support multiple languages?
A language should comply with the Common Language
Runtime standard to become a .NET language. In .NET,
code is compiled to Microsoft Intermediate Language (MSIL
for short). This is called as Managed Code. This Managed
code is run in .NET environment. So after compilation to
this IL the language is not a barrier. A code can call
or use a function written in another language.
How ASP .NET different from ASP?
Scripting is separated from the HTML, Code is compiled
as a DLL, these DLLs can be executed on the server.
What is smart navigation?
The cursor position is maintained when the page gets
refreshed due to the server side validation and the page
What is view state?
The web is stateless. But in ASP.NET, the state of a
page is maintained in the in the page itself
automatically. How? The values are encrypted and saved
in hidden controls. this is done automatically by the
ASP.NET. This can be switched off / on for a single
How do you validate the controls in an ASP .NET page?
Using special validation controls that are meant for
this. We have Range Validator, Email Validator.
Can the validation be done in the server side? Or this
can be done only in the Client side?
Client side is done by default. Server side validation
is also possible. We can switch off the client side and
server side can be done.
How to manage pagination in a page?
Using pagination option in DataGrid control. We have to
set the number of records for a page, then it takes care
of pagination by itself.
What is ADO .NET and what is difference between ADO and
ADO.NET is stateless mechanism. I can treat the ADO.Net
as a separate in-memory database where in I can use
relationships between the tables and select insert and
updates to the database. I can update the actual
database as a batch.
Explain the differences between Server-side and
Server side scripting means that all the script will be
executed by the server and interpreted as needed. ASP
doesn’t have some of the functionality like sockets,
uploading, etc. For these you have to make a custom
components usually in VB or VC++. Client side scripting
means that the script will be executed immediately in
the browser such as form field validation, clock, email
validation, etc. Client side scripting is usually done
VBScript code is included in the HTML page, then anyone
can see the code by viewing the page source. Also a
possible security hazards for the client computer.
What type of code (server or client) is found in a
Should validation (did the user enter a real date) occur
server-side or client-side? Why?
Client-side validation because there is no need to
request a server side date when you could obtain a date
from the client machine.
What does the "EnableViewState" property do? Why would I
want it on or off?
Enable ViewState turns on the automatic state management
feature that enables server controls to re-populate
their values on a round trip without requiring you to
write any code. This feature is not free however, since
the state of a control is passed to and from the server
in a hidden form field. You should be aware of when
ViewState is helping you and when it is not. For
example, if you are binding a control to data on every
round trip (as in the datagrid example in tip #4), then
you do not need the control to maintain it’s view state,
since you will wipe out any re-populated data in any
case. ViewState is enabled for all server controls by
default. To disable it, set the EnableViewState property
of the control to false.
What is the difference between Server.Transfer and
Why would I choose one over the other? Server.Transfer()
: client is shown as it is on the requesting page only,
but the all the content is of the requested page. Data
can be persist across the pages using Context.Item
collection, which is one of the best way to transfer
data from one page to another keeping the page state
alive. Response.Dedirect() :client know the physical
location (page name and query string as well).
Context.Items loses the persistence when navigate to
destination page. In earlier versions of IIS, if we
wanted to send a user to a new Web page, the only option
we had was Response.Redirect. While this method does
accomplish our goal, it has several important drawbacks.
The biggest problem is that this method causes each page
to be treated as a separate transaction. Besides making
it difficult to maintain your transactional integrity,
Response.Redirect introduces some additional headaches.
First, it prevents good encapsulation of code. Second,
you lose access to all of the properties in the Request
object. Sure, there are workarounds, but they’re
difficult. Finally, Response.Redirect necessitates a
round trip to the client, which, on high-volume sites,
causes scalability problems. As you might suspect,
Server.Transfer fixes all of these problems. It does
this by performing the transfer on the server without
requiring a roundtrip to the client.
Can you give an example of when it would be appropriate
to use a web service as opposed to a non-serviced .NET
When to Use Web Services:
* Communicating through a Firewall When building a
distributed application with 100s/1000s of users spread
over multiple locations, there is always the problem of
communicating between client and server because of
firewalls and proxy servers. Exposing your middle tier
components as Web Services and invoking the directly
from a Windows UI is a very valid option.
* Application Integration When integrating applications
written in various languages and running on disparate
systems. Or even applications running on the same
platform that have been written by separate vendors.
* Business-to-Business Integration This is an enabler
for B2B integration which allows one to expose vital
business processes to authorized supplier and customers.
An example would be exposing electronic ordering and
invoicing, allowing customers to send you purchase
orders and suppliers to send you invoices
* Software Reuse This takes place at multiple levels.
Code Reuse at the Source code level or binary component-based
reuse. The limiting factor here is that you can reuse
the code but not the data behind it. Webservice overcome
this limitation. A scenario could be when you are
building an app that aggregates the functionality of
several other Applications. Each of these functions
could be performed by individual apps, but there is
value in perhaps combining the multiple apps to
present a unified view in a Portal or Intranet.
* When not to use Web Services: Single machine
Applications When the apps are running on the same
machine and need to communicate with each other use a
native API. You also have the options of using component
technologies such as COM or .NET Components as there is
very little overhead.
* Homogeneous Applications on a LAN If you have Win32 or
Winforms apps that want to communicate to their server
counterpart. It is much more efficient to use DCOM in
the case of Win32 apps and .NET Remoting in the case of
Page Numbers :