Adv Faqs
Adv Faqs
Adv Faqs
The current property settings of an ASP.NET page and those of any ASP.NET server controls
contained within the page. ASP.NET can detect when a form is requested for the first time versus
when the form is posted (sent to the server), which allows you to program accordingly.
User Controls:
In ASP.NET: A user-authored server control that enables an ASP.NET page to be re-used as a
server control. An ASP.NET user control is authored declaratively and persisted as a text file with
an .ascx extension. The ASP.NET page framework compiles a user control on the fly to a class
that derives from the System.Web.UI.UserControl class.
Where does the Web page belong in the .NET Framework class hierarchy?
System.Web.UI.Page
CachingOutput Caching: Caches the dynamic output generated by a request. Some times it
is useful to cache the output of a website even for a minute, which will result in a
better performance. For caching the whole page the page should have OutputCache
directive.<%@ OutputCache Duration="60" VaryByParam="state" %>
Fragment Caching: Caches the portion of the page generated by the request. Some times it is
not practical to cache the entire page, in such cases we can cache a portion of page<%@
OutputCache Duration="120" VaryByParam="CategoryID;SelectedID"%>
Data Caching: Caches the objects programmatically. For data caching asp.net provides a
cache object for eg: cache["States"] = dsStates;
How do I debug an ASP.NET application that wasn't written with Visual Studio.NET and
that doesn't use code-behind?
Start the DbgClr debugger that comes with the .NET Framework SDK, open the file containing
the code you want to debug, and set your breakpoints. Start the ASP.NET application. Go back to
DbgClr, choose Debug Processes from the Tools menu, and select aspnet_wp.exe from the list
of processes. (If aspnet_wp.exe doesn't appear in the list,check the "Show system processes"
box.) Click the Attach button to attach to aspnet_wp.exe and begin debugging.
Be sure to enable debugging in the ASPX file before debugging it with DbgClr. You can enable
tell ASP.NET to build debug executables by placing a
<%@ Page Debug="true" %> statement at the top of an ASPX file or a <COMPILATION
debug="true" />statement in a Web.config file.
Do ASP.NET forms authentication cookies provide any protection against replay attacks? Do they,
for example, include the client's IP address or anything else that would distinguish the real client
from an attacker?
No. If an authentication cookie is stolen, it can be used by an attacker. It's up to you to prevent
this from happening by using an encrypted communications channel (HTTPS). Authentication
cookies issued as session cookies, do, however,include a time-out valid that limits their
lifetime. So a stolen session cookie can only be used in replay attacks as long as the ticket inside
the cookie is valid. The default time-out interval is 30 minutes.You can change that by modifying
the timeout attribute accompanying the <forms> element in Machine.config or a local Web.config
file. Persistent authentication cookies do not time-out and therefore are a more serious security
threat if stolen.
MailMessage and SmtpMail are classes defined in the .NET Framework Class Library's
System.Web.Mail namespace. Due to a security change made to ASP.NET just before it shipped,
you need to set SmtpMail's SmtpServer property to "localhost" even though "localhost" is the
default. In addition, you must use the IIS configuration applet to enable localhost (127.0.0.1) to
relay messages through the local SMTP service.
VSDISCO files are DISCO files that support dynamic discovery of Web services. If you place the
following VSDISCO file in a directory on your Web server, for example, it returns references to
all ASMX and DISCO files in the host directory and any subdirectories not noted in
<exclude> elements:
<?xml version="1.0" ?>
<dynamicDiscovery
xmlns="urn:schemas-dynamicdiscovery:disco.2000-03-17">
<exclude path="_vti_cnf" />
<exclude path="_vti_pvt" />
<exclude path="_vti_log" />
<exclude path="_vti_script" />
<exclude path="_vti_txt" />
</dynamicDiscovery>
SetNoStore works by returning a Cache-Control: private, no-store header in the HTTP response.
In this example, it prevents caching of a Web page that shows the current time.
Setting AspCompat to true does two things. First, it makes intrinsic ASP objects available to
the COM components by placing unmanaged wrappers around the equivalent ASP.NET objects.
Second, it improves the performance of calls that the page places to apartment- threaded COM
objects by ensuring that the page (actually, the thread that processes the request for the page)
and the COM objects it creates share an apartment. AspCompat="true" forces ASP.NET request
threads into single-threaded apartments (STAs). If those threads create COM objects marked
ThreadingModel=Apartment, then the objects are created in the same STAs as the threads that
created them. Without AspCompat="true," request threads run in a multithreaded apartment
(MTA) and each call to an STA-based COM object incurs a performance hit when it's marshaled
across apartment boundaries.
Do not set AspCompat to true if your page uses no COM objects or if it uses COM objects that
don't access ASP intrinsic objects and that are registered ThreadingModel=Free or
ThreadingModel=Both.
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 are ASP.NET Web Forms? How is this technology different than what is available
though ASP?
Web Forms are the heart and soul of ASP.NET. Web Forms are the User Interface (UI) elements
that give your Web applications their look and feel. Web Forms are similar to Windows Forms in
that they provide properties, methods, and events for the controls that are placed onto them.
However, these UI elements render themselves in the appropriate markup language required by
the request, e.g. HTML. If you use Microsoft Visual Studio .NET, you will also get the familiar
drag-and-drop interface used to create your UI for your Web application.
Which template must you provide, in order to display data in a Repeater control?
ItemTemplate
If I'm developing an application that must accomodate multiple security levels though secure login
and my ASP.NET web appplication is spanned across three web-servers (using round-robbin load
balancing) what would be the best approach to maintain login-in state for the users?
Use the state server or store the state in the database. This can be easily done through simple
setting change in the web.config.
<SESSIONSTATE
StateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1; user id=sa; password="
cookieless="false"
timeout="30"
/>
How do you turn off cookies for one page in your site?
Since no Page Level directive is present, I am afraid that cant be done.
Which method do you use to redirect the user to another page without performing a round
trip to the client?
Server.Transfer and Server.Execute
What property do you have to set to tell the grid which page to go to when using the Pager
object?
CurrentPageIndex
Should validation (did the user enter a real date) occur server-side or client-side? Why?
It should occur both at client-side and Server side.By using expression validator control with the
specified expression ie.. the regular expression provides the facility of only validatating the date
specified is in the correct format or not. But for checking the date where it is the real data or not
should be done at the server side, by getting the system date ranges and checking the date
whether it is in between that range or not.
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, 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.
Response.Dedirect() :client know the physical location (page name and query string as well).
Context.Items loses the persisitance when nevigate 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 component?
Can you give an example of what might be best suited to place in the Application_Start
and Session_Start subroutines?
The Application_Start event is guaranteed to occur only once throughout the lifetime of the
application. It's a good place to initialize global variables. For example, you might want to retrieve
a list of products from a database table and place the list in application state or the Cache object.
SessionStateModule exposes both Session_Start and Session_End events.
1. Simplicity. There is no need to write possibly complex code to store form data between page
submissions.
2. Flexibility. It is possible to enable, configure, and disable ViewState on a control-by-control
basis, choosing to persist the values of some fields but not others.
There are, however a few disadvantages that are worth pointing out:
1. Does not track across pages. ViewState information does not automatically transfer from page
to page. With the session
approach, values can be stored in the session and accessed from other pages. This is not
possible with ViewState, so storing
data into the session must be done explicitly.
2. ViewState is not suitable for transferring data for back-end systems. That is, data still has to be
transferred to the back
end using some form of data object.
Describe session handling in a webfarm, how does it work and what are the limits?
ASP.NET Session supports storing of session data in 3 ways, i] in In-Process ( in the same
memory that ASP.NET uses) , ii] out-of-process using Windows NT Service )in separate memory
from ASP.NET ) or iii] in SQL Server (persistent storage). Both the Windows Service and SQL
Server solution support a webfarm scenario where all the web-servers can be configured to share
common session state store.
1. Windows Service :
We can start this service by Start | Control Panel | Administrative Tools | Services | . In that we
service names ASP.NET State Service. We can start or stop service by manually or configure to
start automatically. Then we have to configure our web.config file
<CONFIGURATION><configuration>
<system.web>
<SessionState
mode = “StateServer”
stateConnectionString = “tcpip=127.0.0.1:42424”
stateNetworkTimeout = “10”
sqlConnectionString=”data source = 127.0.0.1; uid=sa;pwd=”
cookieless =”Flase”
timeout= “20” />
</system.web>
</configuration> </SYSTEM.WEB>
</CONFIGURATION>
Here ASP.Net Session is directed to use Windows Service for state management on local server
(address : 127.0.0.1 is TCP/IP loop-back address). The default port is 42424. we can configure to
any port but for that we have to manually edit the registry.
Follow these simple steps
- In a webfarm make sure you have the same config file in all your web servers.
- Also make sure your objects are serializable.
- For session state to be maintained across different web servers in the webfarm, the application
path of the web-site in the IIS Metabase should be identical in all the web-servers in the webfarm.
Which template must you provide, in order to display data in a Repeater control?
You have to use the ItemTemplate to Display data. Syntax is as follows,
< ItemTemplate >
< div class =”rItem” >
< img src=”images/<%# Container.DataItem(“ImageURL”)%>” hspace=”10” />
< b > <% # Container.DataItem(“Title”)%>
< /div >
< ItemTemplate >
ASP.NET automatically deletes a user's Session object, dumping its contents, after it has been
idle for a configurable timeout interval. This interval, in minutes, is set in the
<SESSIONSTATE>section of the web.config file. The default is 20 minutes.
How do you turn off cookies for one page in your site?
Use Cookie.Discard property, Gets or sets the discard flag set by the server. When true, this
property instructs the client application not to save the Cookie on the user's hard disk when a
session ends.
What tags do you need to add within the asp:datagrid tags to bind columns manually?
Which method do you use to redirect the user to another page without performing a round
trip to the client?
Server.transfer
What is the transport protocol you use to call a Web service SOAP ?
HTTP Protocol
What tags do you need to add within the asp:datagrid tags to bind columns manually?
Set AutoGenerateColumns Property to false on the datagrid tag and then use Column tag and an
ASP:databound tag
Which control would you use if you needed to make sure the values in two different
controls matched?
CompareValidator is used to ensure that two fields are identical.
What are the various ways of securing a web site that could prevent from hacking etc .. ?
1) Authentication/Authorization
2) Encryption/Decryption
3) Maintaining web servers outside the corporate firewall. etc.,
When you’re running a component within ASP.NET, what process is it running within on
Windows XP? Windows 2000? Windows 2003?
On Windows 2003 (IIS 6.0) running in native mode, the component is running within the
w3wp.exe process associated with the application pool which has been configured for the web
application containing the component.
On Windows 2003 in IIS 5.0 emulation mode, 2000, or XP, it's running within the IIS helper
process whose name I do not remember, it being quite a while since I last used IIS 5.0.
When multiple versions of the .NET Framework are executing side-by-side on a single computer,
the ASP.NET ISAPI version mapped to an ASP.NET application determines which version of the
common language runtime is used for the application.
The tool can be launched with a set of optional parameters. Option "i" Installs the version of
ASP.NET associated with Aspnet_regiis.exe and updates the script maps at the IIS metabase root
and below. Note that only applications that are currently mapped to an earlier version of ASP.NET
are affected
What is a PostBack?
The process in which a Web page sends data back to the same page on the server.
What is the < machinekey > element and what two ASP.NET technologies is it used for?
Configures keys to use for encryption and decryption of forms authentication cookie data and
view state data, and for verification of out-of-process session state identification.There fore 2
ASP.Net technique in which it is used are Encryption/Decryption & Verification
What three Session State providers are available in ASP.NET 1.1? What are the pros and
cons of each?
ASP.NET provides three distinct ways to store session data for your application: in-process
session state, out-of-process session state as a Windows service, and out-of-process session
state in a SQL Server database. Each has it advantages.
2. The State Server simply stores session state in memory when in out-of-proc mode. In this
mode the worker process talks directly to the State Server
3. SQL mode, session states are stored in a SQL Server database and the worker process talks
directly to SQL. The ASP.NET worker processes are then able to take advantage of this simple
storage service by serializing and saving (using .NET serialization services) all objects within a
client's Session collection at the end of each Web request
Both these out-of-process solutions are useful primarily if you scale your application across
multiple processors or multiple computers, or where data cannot be lost if a server or process is
restarted.
VaryByParam: A semicolon-separated list of strings used to vary the output cache. By default,
these strings correspond to a query string value sent with GET method attributes, or a parameter
sent using the POST method. When this attribute is set to multiple parameters, the output cache
contains a different version of the requested document for each specified parameter. Possible
values include none, *, and any valid query string or POST parameter name.
VaryByHeader: A semicolon-separated list of HTTP headers used to vary the output cache. When
this attribute is set to multiple headers, the output cache contains a different version of the
requested document for each specified header.
The Repeater class is not derived from the WebControl class, like the DataGrid and DataList.
Therefore, the Repeater lacks the stylistic properties common to both the DataGrid and DataList.
What this boils down to is that if you want to format the data displayed in the Repeater, you must
do so in the HTML markup.
The Repeater control provides the maximum amount of flexibility over the HTML produced.
Whereas the DataGrid wraps the DataSource contents in an HTML < table >, and the DataList
wraps the contents in either an HTML < table > or < span > tags (depending on the DataList's
RepeatLayout property), the Repeater adds absolutely no HTML content other than what you
explicitly specify in the templates.
While using Repeater control, If we wanted to display the employee names in a bold font we'd
have to alter the "ItemTemplate" to include an HTML bold tag, Whereas with the DataGrid or
DataList, we could have made the text appear in a bold font by setting the control's ItemStyle-
Font-Bold property to True.
The Repeater's lack of stylistic properties can drastically add to the development time metric. For
example, imagine that you decide to use the Repeater to display data that needs to be bold,
centered, and displayed in a particular font-face with a particular background color. While all this
can be specified using a few HTML tags, these tags will quickly clutter the Repeater's templates.
Such clutter makes it much harder to change the look at a later date. Along with its increased
development time, the Repeater also lacks any built-in functionality to assist in supporting paging,
editing, or editing of data. Due to this lack of feature-support, the Repeater scores poorly on the
usability scale.
However, The Repeater's performance is slightly better than that of the DataList's, and is more
noticeably better than that of the DataGrid's. Following figure shows the number of requests per
second the Repeater could handle versus the DataGrid and DataList
Can we handle the error and redirect to some pages using web.config?
Yes, we can do this, but to handle errors, we must know the error codes; only then we can take
the user to a proper error message page, else it may confuse the user.
CustomErrors Configuration section in web.config file:
The default configuration is:
< customErrors mode="RemoteOnly" defaultRedirect="Customerror.aspx" >
< error statusCode="404" redirect="Notfound.aspx" / >
< /customErrors >
If mode is set to Off, custom error messages will be disabled. Users will receive detailed
exception error messages.
If mode is set to On, custom error messages will be enabled.
If mode is set to RemoteOnly, then users will receive custom errors, but users accessing the site
locally will receive detailed error messages.
Add an < error > tag for each error you want to handle. The error tag will redirect the user to the
Notfound.aspx page when the site returns the 404 (Page not found) error.
[Example]
[Web.Config]
The DataGrid provides the means to display a group of records from the data source (for
example, the first 10), and then navigate to the "page" containing the next 10 records, and so on
through the data.
Using Ado.Net we can explicit control over the number of records returned from the data source,
as well as how much data is to be cached locally in the DataSet.
1.Using DataAdapter.fill method give the value of 'Maxrecords' parameter
(Note: - Don't use it because query will return all records but fill the dataset based on value of
'maxrecords' parameter).
2.For SQL server database, combines a WHERE clause and a ORDER BY clause with TOP
predicate.
3.If Data does not change often just cache records locally in DataSet and just take some records
from the DataSet to display.
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 knows 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.
Response.Redirect sends a response to the client browser instructing it to request the second
page. This requires a round-trip to the client, and the client initiates the Request for the second
page. Server.Transfer transfers the process to the second page without making a round-trip to the
client. It also transfers the HttpContext to the second page, enabling the second page access to
all the values in the HttpContext of the first page.
Yes, We can create user app domain by calling on of the following overload static methods of the
System.AppDomain class
1. Public static AppDomain CreateDomain(String friendlyName)
2. Public static AppDomain CreateDomain(String friendlyName, Evidence securityInfo)
3. Public static AppDomain CreateDomain(String friendlyName, Evidence securityInfo,
AppDomainSetup info)
4. Public static AppDomain CreateDomain(String friendlyName, Evidence securityInfo, String
appBasePath, String appRelativeSearchPath, bool shadowCopyFiles)
What are the various security methods which IIS Provides apart from .NET ?
a) Authentication Modes
b) IP Address and Domain Name Restriction
c) DNS Lookups DNS Lookups
d) The Network ID and Subnet Mask
e) SSL
What is Web Gardening? How would using it affect a design?
Two attributes in the section affect the Web garden model. They are webGarden and cpuMask.
The webGarden attribute takes a Boolean value that indicates whether or not multiple worker
processes (one per each affinitized CPU) have to be used. The attribute is set to false by default.
The cpuMask attribute stores a DWORD value whose binary representation provides a bit mask
for the CPUs that are eligible to run the ASP.NET worker process. The default value is -1
(0xFFFFFF), which means that all available CPUs can be used. The contents of the cpuMask
attribute is ignored when the webGarden attribute is false. The cpuMask attribute also sets an
upper bound to the number of copies of aspnet_wp.exe that are running.
Web gardening enables multiple worker processes to run at the same time. However, you should
note that all processes will have their own copy of application state, in-process session state,
ASP.NET cache, static data, and all that is needed to run applications. When the Web garden
mode is enabled, the ASP.NET ISAPI launches as many worker processes as there are CPUs,
each a full clone of the next (and each affinitized with the corresponding CPU). To balance the
workload, incoming requests are partitioned among running processes in a round-robin manner.
Worker processes get recycled as in the single processor case. Note that ASP.NET inherits any
CPU usage restriction from the operating system and doesn't include any custom semantics for
doing this.
All in all, the Web garden model is not necessarily a big win for all applications. The more stateful
applications are, the more they risk to pay in terms of real performance. Working data is stored in
blocks of shared memory so that any changes entered by a process are immediately visible to
others. However, for the time it takes to service a request, working data is copied in the context of
the process. Each worker process, therefore, will handle its own copy of working data, and the
more stateful the application, the higher the cost in performance. In this context, careful and
savvy application benchmarking is an absolute must.
Changes made to the section of the configuration file are effective only after IIS is restarted. In IIS
6, Web gardening parameters are stored in the IIS metabase; the webGarden and cpuMask
attributes are ignored.