.Dll is the Source code of ur deployed application.
.Exe is the presentation of ur frentend forms.
When u deployed ur application at that time the .Dll,.EXE
files will create
.DLL .EXE
1. It can be reused. 1. It cannot be reused
2. It can be versioned. 2. It cannot be versioned.
3. It is not self executable 3. It is self executable.
4. It doesn't have main 4. It will have main
function. function.
An ActiveX Dll runs is an in process server running in the
same memory space as the client process.
An ActiveX Exe is an out of process server which runs in
it's own separate memory space.
Question 2 is the same as question 1.
Advantages of ActiveX Dll
-------------------------
1) An in-process component shares its client’s address
space, so property and method calls don’t have to be
marshaled. This results in much faster performance.
Disadvantages of ActiveX Dll
----------------------------
1) If an unhandled error occurs it will cause the client
process to stop operating.
Advantages of ActiveX Exe
-------------------------
1) The component can run as a standalone desktop
application, like Microsoft Excel or Microsoft Word, in
addition to providing objects.
2) The component can process requests on an independent
thread of execution, notifying the client of task
completion using events or asynchronous call-backs. This
frees the client to respond to the user.
3)If an error occurs the client processes can continue to
operate.
Disadvantages of ActiveX Exe
----------------------------
1) Generally slower than an ActiveX dll alternative.
Rahul Mehta (MCAD)
Systime India
DLL is a dynamic link library file that we can directly
execute. if we want to use dll then we need to add refence
in our progrma in Dll there NO Main function. EXE file is
excutable file that we can directly run.In exe It must be
one statr point mena Main function.
A dll use same memory space of client while running.
An exe use own memory space separate from client while
running.
A dll is much faster.
A exe can be run as standalone program.
DLL - inprocess
DLL runs along with the application which is sharing that
particular DLL. If we interrupt that application that DLL
also affected which in turn affects all onter applications
which is using that application.
EXE - outprocess
EXE runs seperately.
DLL isa inprocess component i.e. it runs in the same
process space (means sever n dll both share the same
process space) whereas exe is a outof process component
means server n exe runs in its own process space.
* In case of dll any error in dll causes makes the
application off whereas in case of exe it cann't
*dll is faster than exe
DLL is a dependent type of program. Every DLL has an entry
point method and Dll gets loaded only when a call to it is
made from any application for the first time.
Exe is a self-running type of program.
1)
DLL: Can not run independently. Runs with EXE.
EXE: Can run independently.
2)
DLL: Takes up space in memory in processess' memory space,
DLL is in-process component.
EXE: Takes up space in memory separately, EXE is Out-
process.
3)
DLL: Runs faster than exe.
EXE: Slower than DLL.
4)
DLL: error causes off the application.
EXE: can't.
5)
DLL: Doesn't have own main entry point, handled by other
method(s).
EXE: Have own entry point, handled by OS.
i have one gridview contains edititemtemplate(which
contains update and cancel buttons) and i have one item
template (contains edit button)
i want the code for update and cancelbuttons in edit item
template and i want the code for edit button in
itemtemplate. please help me
What is the Web.config file used for?
a) To store the global information and variable definition
for the application.
b) Configures the time that the server-side codebehind
module is called
c) To Configure the Web Server.
d) To Configure the Web browser.
Your ASP.NET application displays sales data on a page. You
want to improve performance by holding the page in memory on
the server for one hour. You want to ensure that the page is
flushed from memory after one hour, and that the page is
re-created when the next request for the page is received.
What should you do?
A . Initialize a new instance of the Cache class in the
Application.Start event handler.
B . Initialize a new instance of the Timer class in the
Page.Load event handler.
C . Set the Duration attribute of the OutputCache directive
in the page.
D . In the Web.config file, set the timeout attribute of the
sessionState element.