1. In the assembly that implements the type(Console), look up the method being called in the metadata.
2. From the metadata, get the IL from this method and verify it.
3. Allocate a block of memory.
4. Compile the IL into native CPU instructions: the native code is saved in the memory allocated in step#3.
5. Modify the method's entry in the Type's table so that it now points to the memory block allocated in Step#3.
6. Jump to the native code contained inside the memory block.

Declare @Var1 nvarchar(800)

Set @Var1=’’

Select @Var1 = @Var1 + ‘,’ + Field1 from Table1

Select @Var1

Hi,

Whenever I run sfc /scannow it asks for a CD. How can i point it to some other path where my installation source files reside.

Answer:

In Registry using regedit locate

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Setup\SourcePath

Set its value to the location where I386 foler is located. Provide the parent folder path of I386 and not of I386 itself.

Also update ServicePackSourcePath and add to Installation Sources as well.

here is the working code:

<form id="form1" runat="server">

<div>

<asp:TextBox runat="server" ID="txt1" TextMode="MultiLine" />

<asp:HiddenField runat="server" ID="hidSelectedText" />

<asp:Button runat="server" ID="showselected" Text="Show selected" OnClientClick="doselection();" OnClick="showselected_Click" />

<script type="text/javascript">

function doselection()

if (window.getSelection)

else if (document.getSelection)

else if (document.selection)

else

alert('selection not supported');

document.getElementById('<%=hidSelectedText.ClientID %>').value = txt;

</script>

</div>

</form>

-----------------------------------------------------------------------

Go to

Tools > Options 

Expand "Projects And Solutions"

Check "Track Active item in Solution Explorer"

Use

Virtual method has an implementation & provide the derived class with the option of overriding it.

Abstract method does not provide an implementation & forces the derived class to override the method.

Windows Authentication (via Active Directory) and SQL Server authentication (via Microsoft SQL Server username and password).

Windows Authentication is trusted because the username and password are checked with the Active Directory,

the SQL Server authentication is untrusted, since SQL Server is the only verifier participating in the transaction.

1. Positive test cases (correct data, correct output).

2. Negative test cases (broken or missing data, proper handling).

3. Exception test cases (exceptions are thrown and caught properly).

System.Diagnostics.Process objDocProcess = new System.Diagnostics.Process();

objDocProcess.EnableRaisingEvents = false;

objDocProcess.StartInfo.FileName = @"C:\Excel.xls";

A string is a sequential collection of Unicode characters that is used to represent text. At the other hand the string builder is sealed class(Cannot be inherited)it represents a mutable string of characters.

String is mutable that means that it can't be modified once created, to modify a given string by appending new characters or so the CLR destroy the first string instance and create a new string one and this costs in terms of memory and time process.

 Using the string builder, you create a mutable object that recieves modification without having to be destroyed and reinstanciated for each modifiaction

Poly means many and morph means form. Thus, polymorphism refers to being able to use many forms of a type without regard to the details.

Polymorphism have 2 types :

1. Compile time also called overloading have 3 types.

·         Constructor overloading (i.e., with same constructor name and different no of arguments or different datat types or both )

·         Function overloading (i.e., with same function name and different no of arguments or different data types or both)

·         operator overloading: example : Variable++;

2 Run time

·         It is achieved by overriding parent class method:

1. OnInit (Init)  -- Inializes all Child controls on the Page

2. LoadControlState  -- Loads the Control State 

3. LoadViewState -- Loads the View State

4. LoadPostData -- Control properties are set according to the received form data

5. Load -- Actions can be performed on the controls as all the pre-activities are complete by this time

6. RaisePostDataChangedEvent -- This event is raised if data has been changed in previous and Current Postbacks.

7. RaisePostBackEvent -- This event handles the user action that caused the Postback.

8. PreRender (OnPreRender) -- This event takes place between postback and saving viewstate. Till this stage changes will be saved to the control.

9. SaveControlState -- Self Explanatory

10. SaveViewState -- Self Explanatory

11. Render -- Generates artifacts at Client side (HTML,DHTML,Scripts) to properly display controls

12. Dispose -- Releases unmanaged Resource ( Database connections, file handles)

13. Unload -- Releases managed Resources ( Instances created by CLR)

The XmlSerializer can be used when you need the data in the object to be stored in an XML Format. However, this serialize has the limitation that it can serialize only the public fields of an object.

The SoapFormatter is ideal in scenarios where you need interoperability. This is ideal in applications spanning heterogeneous environments.

The BinaryFormatter generates a very compact stream when an object is serialized as compared to the other two techniques and hence is useful when data needs to travel electronically across the wire. This is appropriate when the applications do not involve heterogeneous environments.

Serialization is the process of saving the state of an object by converting it to a stream of bytes. The object can then be persisted to file, database, or even memory. The reverse process of serialization is known as deserialization

This classification arises from the format in which the data in the object is persisted. Each of the serialization techniques mentioned have different capabilities and each excel in specific scenarios. The XML serialization technique can convert only the public properties and fields of an object into an XML format. The XML serialization is also known as shallow serialization.

This inability of the XMLSerializer to serialize the private fields of an object is overcome by the SOAP and binary serialization techniques. In the binary and SOAP serialization techniques, the state of the entire object is serialized into a stream of bytes. In cases where the object contains a reference to other objects, even those are serialized. This type of serialization is known as deep serialization.

• An abstract class may contain complete or incomplete methods. Interfaces can contain only the signature of a method but no body. Thus an abstract class can implement methods but an interface can not implement methods.

• An abstract class can contain fields, constructors, or destructors and implement properties. An interface can not contain fields, constructors, or destructors and it has only the property's signature but no implementation.

• An abstract class cannot support multiple inheritances, but an interface can support multiple inheritances. Thus a class may inherit several interfaces but only one abstract class.

• A class implementing an interface has to implement all the methods of the interface, but the same is not required in the case of an abstract Class.

• Various access modifiers such as abstract, protected, internal, public, virtual, etc. are useful in abstract Classes but not in interfaces.

You bet. Just call SetNoStore on the HttpCachePolicy object exposed through the Response object's Cache property, as demonstrated here:

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.

Most browsers recognize the following META tag as a signal to automatically refresh the page every nn seconds:

Here's an ASPX file that displays the current time of day. Once displayed, it automatically refreshes every 5 seconds:

Use the HtmlInputFile class, which you can declare an instance of with an <input type="file" runat="server"/> tag. The following example is a complete ASPX file that lets a user upload an image file and a comment descibing the image. The Upload_Click method writes the image and the comment to a table named Pictures in a SQL Server database named MyPictures.