Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Answer: Here I have taken information regarding Share Point Portal Server 2003 provides
mainly access to the crucial business information and applications.With the help of Share Point
Server we can server information between Public Folders, Data Bases, File Servers and the
websites that are based on Windows server 2003. This Share Point Portal is integrated with
MSAccess and Windows servers,So we can get a Wide range of document management
functionality. We can also create a full featured portal with readymade navigation and structure.
Question: What changes are done in IIS 6.0 over IIS 5.0 ?
Answer: IIS makes easy to get information.IIS 6.0 is the next latest of web server available in
Windows Server 2003 platform. IIS 6.0 contains several enhancements over IIS 5.0 that are mainly
to increase reliability, manageability, scalability, and security. IIS 6.0 is a key component of the
Windows Server 2003 application platform, using which you can develop and deploy high
performance ASP.NET Web applications, and XML Web Services.
Question:-Can you define what is SharePoint and some overview about this ?
Answer: SharePoint helps workers for creating powerful personalized interfaces only by
dragging and drop pre-defined Web Part Components. And these Web Parts components also
helps non programmers to get information which care and customize the appearance of Web
pages. To under stand it we take an example one Web Part might display a user's information
another might create a graph showing current employee status and a third might show a list of
Employees Salary. This is also possible that each functions has a link to a video or audio
presentation.So now Developers are unable to create these Web Part components and make
them available to SharePoint users.
Question:-What is Sandbox in SQL server and explain permission level in Sql Server ?
Answer: Sandbox is place where we run trused program or script which is created from the third
party. There are three type of Sandbox where user code run.
Safe Access Sandbox:-Here we can only create stored procedure,triggers,functions,datatypes
etc.But we doesnot have acess memory ,disk etc.
External Access Sandbox:-We cn access File systems outside the box. We can not play with
threading,memory allocation etc.
Unsafe Access Sandbox:-Here we can write unreliable and unsafe code.
Question:-How many types of cookies are there in .NET ?
Answer: Two type of cookeies.
a) single valued eg request.cookies(”UserName”).value=”dotnetquestion”
b)Multivalued cookies. These are used in the way collections are used example
request.cookies(”CookiName”)(”UserName”)=”dotnetquestionMahesh”
request.cookies(”CookiName”)(”UserID”)=”interview″
Use the View State property to save data in a hidden field on a page. Because ViewState stores
data on the page, it is limited to items that can be serialized. If you want to store more complex
items in View State, you must convert the items to and from a string.
ASP.NET provides the following ways to retain variables between requests:
Context.Handler object Use this object to retrieve public members of one Web form’s class from
a subsequently displayed Web form.
Query strings Use these strings to pass information between requests and responses as part of
the Web address. Query strings are visible to the user, so they should not contain secure
information such as passwords.
Cookies Use cookies to store small amounts of information on a client. Clients might refuse
cookies, so your code has to anticipate that possibility.
View state ASP.NET stores items added to a page’s ViewState property as hidden fields on the
page.
Session state Use Session state variables to store items that you want keep local to the current
session (single user).
Application state Use Application state variables to store items that you want be available to all
users of the application.
Programmers understand that they're responsible for releasing any memory that they allocate,
but they're not very good at actually doing it. In addition, functions that allocate memory as a
side effect abound in the Windows API and in the C runtime library. It's nearly impossible for a
programmer to know all of the rules. Even when the programmer follows the rules, a small
memory leak in a support library can cause big problems if called enough.
The .NET Framework solves the memory management problems by implementing a garbage
collector that can keep track of allocated memory references and release the memory when it is
no longer referenced. A large part of what makes this possible is the blazing speed of today's
processors. When you're running a 2 GHz machine, it's easy to spare a few cycles for memory
management. Not that the garbage collector takes a huge number of cycles--it's incredibly
efficient.
The garbage collector isn't perfect and it doesn't solve the problem of mis-managing other scarce
resources (file handles, for example), but it relieves programmers from having to worry about a
huge source of bugs that trips almost everybody up in other programming environments.
On balance, automatic memory management is a huge win in almost every situation.