Monday, April 22, 2013

How to create and implement custom field type in SharePoint ?

What is Custom field Type in SharePoint ?

With custom field types, developers can really integrate with the SharePoint platform.Where with other ways of extending new functionality is build mostly on top of the SharePoint. With custom fields the level of integration is a lot higher. This extra integration comes at a price, the development of custom field types is more labor intensive than developing ‘normal’ field controls. But then, ‘normal’ fields can only be used on publishing pages and not in SharePoint display forms or in SharePoint lists. Custom field types can be used in both SharePoint lists and on display forms. The data custom fields use is stored in the SharePoint content database and custom fields can be used in SharePoint workflows and have access to the build in version control system .


create and implement Custom Field Type step by step:

1. Open Microsoft Visual Studio, Go to File-->New-->Project.
2. In the New Project dialog box, select Class Library from the Templates box, give it a name and location, then click OK.
3. Add Reference of Microsoft.SharePoint assembly, and then click OK.
4. Make the project as strong name key file.
5. Now rename class.cs with CountryStateField.cs
6. Creating a class for Custom field Type
7. Create a field definition Schema XML file
8. Create a class which contains FieldTypeValue.

create and implement Custom Field Type step by step.

Open Microsoft Visual Studio, Go to File-->New-->Project.
In the New Project dialog box, select Class Library from the Templates box, give it a name and location, then click OK.
Add Reference of Microsoft.SharePoint assembly, and then click OK.
Make the project as strong name key file.
Now rename class.cs with CountryStateField.cs
Creating a class for Custom field Type
Create a field definition Schema XML file
Create a class which contains FieldTypeValue.
Create a class which is used for to display that , fieldcontrol.


Read more »
Posted by

How to create and implement custom field type in SharePoint ?

What is Custom field Type in SharePoint ?

With custom field types, developers can really integrate with the SharePoint platform.Where with other ways of extending new functionality is build mostly on top of the SharePoint. With custom fields the level of integration is a lot higher. This extra integration comes at a price, the development of custom field types is more labor intensive than developing ‘normal’ field controls. But then, ‘normal’ fields can only be used on publishing pages and not in SharePoint display forms or in SharePoint lists. Custom field types can be used in both SharePoint lists and on display forms. The data custom fields use is stored in the SharePoint content database and custom fields can be used in SharePoint workflows and have access to the build in version control system .
create and implement Custom Field Type step by step:

  1. Open Microsoft Visual Studio, Go to File-->New-->Project.
  2. In the New Project dialog box, select Class Library from the Templates box, give it a name and location, then click OK.
  3. Add Reference of Microsoft.SharePoint assembly, and then click OK.
  4. Make the project as strong name key file.
  5. Now rename class.cs with CountryStateField.cs
  6. Creating a class for Custom field Type
  7. Create a field definition Schema XML file
  8. Create a class which contains FieldTypeValue.
  9. Create a class which is used for to display that , fieldcontrol.

Let us go through every step in detail one by one.

Step6: Creating a Custom Field Type
The first step in creating a custom field type and field control is to create the field type class — the hub of everything related to the field. All field types must inherit from the Microsoft.SharePoint.SPField class or one that is derived from it.

Sample of Code

using System;

using System.Collections.Generic;

using System.Text;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebControls;

namespace Sample.FieldType

{



class CountryRegionField:SPFieldMultiColumn

public {

public CountryStateField(SPFieldCollection fields, string fieldName): base(fields, fieldName) { }

public CountryStateField(SPFieldCollection fields, string typeName, string  displayName): base(fields, typeName, displayName) { }

public override object GetFieldValue(string value)

{

if (string.IsNullOrEmpty(value))   return null;

return new CountryStateValue(value);

}

public override BaseFieldControl FieldRenderingControl

{

get

{

BaseFieldControl control = new CountryStateControl();

control.FieldName = this.InternalName;

return control;

}

}

public override string GetValidatedString(object value)

{

if (value == null)

{

if (this.Required) throw new SPFieldValidationException("Invalid value for this field.");

return string.Empty;

}

else

{

CountryStateValue field = value as CountryStateValue;

// if no value obtained, error in the field

if (field == null) throw new ArgumentException("Invalid value.");
// if it is required...

if (this.Required)

{

// make sure that both COUNTRY & State are selected

if (field.Country != string.Empty && field.State != string.Empty)

throw new SPFieldValidationException("Both are required.");

}

else

{

// else, even if not required, if one field is filled in, the other must beas well

if (!string.IsNullOrEmpty(field.Country))

if(string.IsNullOrEmpty(field.State))

throw new SPFieldValidationException("Both are required if one value is entered.");

}

return value.ToString();

}

}

}

}

Let us move to the next step , Create a xml file for Custom field Definition.

Step7 : Creating a Custom Field Type Definition

With a field type class created, the next step is to create the field type definition that will make SharePoint aware of the field. This is done by creating an XML file in the [..]\12\TEMPLATE\XML Folder. When SharePoint starts up ,it looks at the [..]\12\TEMPLATE\XML folder and loads all the field type - defined files named fldtypes[_*].xml .

All the SharePoint fields provided in the WSS 3.0 install are found in the fldtypes.xml file. Other fields are added based on the MOSS 2007 installation. For instance, all the Publishing - specific fields are defined in the fldtypes.publishing.xml file.

CountryStateField definition (fldtypes _ CountryState.xml)

< ?xml version=”1.0” encoding=”utf-8” ? >

< FieldTypes >

< FieldType >

< Field Name=”TypeName” > CountryState< /Field >

< Field Name=”ParentType” > MultiColumn < /Field >

< Field Name=”TypeDisplayName” > Country, State < /Field >

< Field Name=”TypeShortDescription” > Country and state < /Field >

< Field Name=”UserCreatable” > TRUE < /Field >

< Field Name=”FieldTypeClass” > Sample.FieldType. CountryStateField,Sample.FieldType,Version=1.0.0.0, Culture=neutral,  PublicKeyToken=e42a63991be18435 < /Field >

< RenderPattern Name=”DisplayPattern” >

< Switch >

< Expr > < Column / > < /Expr >

< Case Value=”” / >

< Default >

< Column SubColumnNumber=”0” HTMLEncode=”TRUE” / >

<![CDATA[;]]>

< Column SubColumnNumber=”1” HTMLEncode=”TRUE” / >

< /Default >

< /Switch >

< /RenderPattern >

< /FieldType >

< /FieldTypes >
  • TypeName: This is the unique name of the field used when creating items such as site columns using a Feature. For example, if a site column were created that was based on the field type created in this chapter, the element manifest ’ s site element would look like the following (omitting the other required attributes):
  • ParentType: The parent type is the field type from which the custom field type is derived — in this case, SPFieldMultiColumn or just MultiColumn .
  • TypeDisplayName: This name is used to display the field type on pages such as the Site Column Gallery or a content type ’ s detail page.
  • TypeShortDescription: The short description is the string used to display the field type as an option when creating new site or list columns (the long radio button list under the new column ’ s title textbox).
  • UserCreatable: This Boolean property tells SharePoint whether the field type can be used in the creation of a column in a list by a user. When false , developers can still use the field type in sitecolumns within the definition of list templates created using Features.
  • FieldTypeClass: This contains the strong name of the field type class and the assembly containing the class. This is also referred to as the five - part name: namespace.type, Assembly,Version, Culture, PublicKeyToken .

The custom field type definition should be added to the Visual Studio project in the following location: \TEMPLATE\XML\fldtypes_ CountryState.xml .

Step8:  Creating a Custom Field Value
One of the requirements of the ContryStateField custom field type was to store the data within a custom data structure. While it sounds a bit complex, it is actually very simple. The custom field value class is very handy with field types that are derived from the SPFieldMultiColumn field because data is stored in the SPFieldMultiColumn field as a special delimited string using ;# as the delimiter, and not just between two values but surrounding them ;#United States;#Florida;#

CountryStateValue.cs file containing the field value

using System;

using Microsoft.SharePoint;

namespace Sample.FieldType{

public class CountryStateValue : SPFieldMultiColumnValue {

private const int NUM_FIELDS = 2;

public CountryStateValue ()

: base(NUM_FIELDS) { }

public CountryStateValue (string value)

: base(value) { }

public string Country {

get { return this[0]; }

set { this[0] = value; }

}

public string State {

get {return this[1];}

set { this[1] = value; }

}

}

}

Step 9 : Creating a Custom Field Control

The first piece in a custom field control is the control class. This class must inherit from the Microsoft.SharePoint.WebControls.BaseFieldControl class or one that derives from it. For the CountryStateField , the BaseFieldControl will work.

using System;

using System.Collections.Generic;

using System.Text;

using Microsoft.SharePoint.WebControls;

using System.Web.UI.WebControls;

using Microsoft.SharePoint;

namespace Sample.FieldType

{

public class CountryStateControl : BaseFieldControl,IDesignTimeHtmlProvider

{

protected DropDownList _country;

protected DropDownList _StateSelector;

protected Literal _StateSelectorLiteral;

public override object Value {

get

{

EnsureChildControls();

CountryStateValue field = new CountryStateValue();

if (_country == null || _StateSelector == null )

{

field.Country = String.Empty;

field.State = String.Empty;

}

else

{

// set country value

if (_country.SelectedIndex == 0)

field.Country = String.Empty;

else

field.Country = _country.SelectedValue;

// set State value

if (_StateSelector.SelectedIndex == 0)

field.State = String.Empty;

else

field.State = _StateSelector.SelectedValue;

}

return field;

}

set

{

EnsureChildControls();

if (value != null && !string.IsNullOrEmpty(value.ToString()))

{

CountryStateValue field = new CountryStateValue(value.ToString());

_country.SelectedValue = field.Country;

if (_country.SelectedIndex > 0)

_StateSelector.SelectedValue = field.State;

SetStateControlVisibility(_country.SelectedIndex);

}

}

}

private void SetStateControlVisibility(int countrySelectedIndex)

{

switch (countrySelectedIndex)

{

case 0: // if none selected

_StateSelector.Visible = false;

_StateSelectorLiteral.Visible = false;

break;

default: sss

_StateSelector.Visible = true;

_StateSelectorLiteral.Visible = true;

break;

}

}

protected void Country_SelectedIndexChanged(object sender, EventArgs e)

{

EnsureChildControls();

//ADDstatesdependsonCountry(_country.SelectedIndex);

SetStateControlVisibility(_country.SelectedIndex);

}

protected void ADDstatesdependsonCountry(int countrySelectedIndex)

{

_StateSelector.Items.Clear();

//Code for Adding items to State dropdown depends on contry

}

void AddItesmsForContry()

{

//code for adding items to country dropdown

}

protected override void CreateChildControls()

{

if (this.Field == null || this.ControlMode == SPControlMode.Display ||this.ControlMode == SPControlMode.Invalid)

return;

base.CreateChildControls();

// get reference to Country selector

_country = new DropDownList();

_country.SelectedIndexChanged += new EventHandler(Country_SelectedIndexChanged);

_country.AutoPostBack = true;

//AddItesmsForContry()

_StateSelector = new  DropDownList();
_StateSelectorLiteral = new Literal();

//Add country ,state Selector and State Literal to control collection

this.Controls.Add(_country);

this.Controls.Add(_StateSelectorLiteral);

this.Controls.Add(_StateSelector);

}

}

}
Posted by

How to create and implement custom field type in SharePoint ?

What is Custom field Type in SharePoint ?

With custom field types, developers can really integrate with the SharePoint platform.Where with other ways of extending new functionality is build mostly on top of the SharePoint. With custom fields the level of integration is a lot higher. This extra integration comes at a price, the development of custom field types is more labor intensive than developing ‘normal’ field controls. But then, ‘normal’ fields can only be used on publishing pages and not in SharePoint display forms or in SharePoint lists. Custom field types can be used in both SharePoint lists and on display forms. The data custom fields use is stored in the SharePoint content database and custom fields can be used in SharePoint workflows and have access to the build in version control system .
create and implement Custom Field Type step by step:

  1. Open Microsoft Visual Studio, Go to File-->New-->Project.
  2. In the New Project dialog box, select Class Library from the Templates box, give it a name and location, then click OK.
  3. Add Reference of Microsoft.SharePoint assembly, and then click OK.
  4. Make the project as strong name key file.
  5. Now rename class.cs with CountryStateField.cs
  6. Creating a class for Custom field Type
  7. Create a field definition Schema XML file
  8. Create a class which contains FieldTypeValue.
  9. Create a class which is used for to display that , fieldcontrol.

Let us go through every step in detail one by one.

Step6: Creating a Custom Field Type
The first step in creating a custom field type and field control is to create the field type class — the hub of everything related to the field. All field types must inherit from the Microsoft.SharePoint.SPField class or one that is derived from it.

Sample of Code

using System;

using System.Collections.Generic;

using System.Text;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebControls;

namespace Sample.FieldType

{



class CountryRegionField:SPFieldMultiColumn

public {

public CountryStateField(SPFieldCollection fields, string fieldName): base(fields, fieldName) { }

public CountryStateField(SPFieldCollection fields, string typeName, string  displayName): base(fields, typeName, displayName) { }

public override object GetFieldValue(string value)

{

if (string.IsNullOrEmpty(value))   return null;

return new CountryStateValue(value);

}

public override BaseFieldControl FieldRenderingControl

{

get

{

BaseFieldControl control = new CountryStateControl();

control.FieldName = this.InternalName;

return control;

}

}

public override string GetValidatedString(object value)

{

if (value == null)

{

if (this.Required) throw new SPFieldValidationException("Invalid value for this field.");

return string.Empty;

}

else

{

CountryStateValue field = value as CountryStateValue;

// if no value obtained, error in the field

if (field == null) throw new ArgumentException("Invalid value.");
// if it is required...

if (this.Required)

{

// make sure that both COUNTRY & State are selected

if (field.Country != string.Empty && field.State != string.Empty)

throw new SPFieldValidationException("Both are required.");

}

else

{

// else, even if not required, if one field is filled in, the other must beas well

if (!string.IsNullOrEmpty(field.Country))

if(string.IsNullOrEmpty(field.State))

throw new SPFieldValidationException("Both are required if one value is entered.");

}

return value.ToString();

}

}

}

}

Let us move to the next step , Create a xml file for Custom field Definition.

Step7 : Creating a Custom Field Type Definition

With a field type class created, the next step is to create the field type definition that will make SharePoint aware of the field. This is done by creating an XML file in the [..]\12\TEMPLATE\XML Folder. When SharePoint starts up ,it looks at the [..]\12\TEMPLATE\XML folder and loads all the field type - defined files named fldtypes[_*].xml .

All the SharePoint fields provided in the WSS 3.0 install are found in the fldtypes.xml file. Other fields are added based on the MOSS 2007 installation. For instance, all the Publishing - specific fields are defined in the fldtypes.publishing.xml file.

CountryStateField definition (fldtypes _ CountryState.xml)

< ?xml version=”1.0” encoding=”utf-8” ? >

< FieldTypes >

< FieldType >

< Field Name=”TypeName” > CountryState< /Field >

< Field Name=”ParentType” > MultiColumn < /Field >

< Field Name=”TypeDisplayName” > Country, State < /Field >

< Field Name=”TypeShortDescription” > Country and state < /Field >

< Field Name=”UserCreatable” > TRUE < /Field >

< Field Name=”FieldTypeClass” > Sample.FieldType. CountryStateField,Sample.FieldType,Version=1.0.0.0, Culture=neutral,  PublicKeyToken=e42a63991be18435 < /Field >

< RenderPattern Name=”DisplayPattern” >

< Switch >

< Expr > < Column / > < /Expr >

< Case Value=”” / >

< Default >

< Column SubColumnNumber=”0” HTMLEncode=”TRUE” / >

<![CDATA[;]]>

< Column SubColumnNumber=”1” HTMLEncode=”TRUE” / >

< /Default >

< /Switch >

< /RenderPattern >

< /FieldType >

< /FieldTypes >
  • TypeName: This is the unique name of the field used when creating items such as site columns using a Feature. For example, if a site column were created that was based on the field type created in this chapter, the element manifest ’ s site element would look like the following (omitting the other required attributes):
  • ParentType: The parent type is the field type from which the custom field type is derived — in this case, SPFieldMultiColumn or just MultiColumn .
  • TypeDisplayName: This name is used to display the field type on pages such as the Site Column Gallery or a content type ’ s detail page.
  • TypeShortDescription: The short description is the string used to display the field type as an option when creating new site or list columns (the long radio button list under the new column ’ s title textbox).
  • UserCreatable: This Boolean property tells SharePoint whether the field type can be used in the creation of a column in a list by a user. When false , developers can still use the field type in sitecolumns within the definition of list templates created using Features.
  • FieldTypeClass: This contains the strong name of the field type class and the assembly containing the class. This is also referred to as the five - part name: namespace.type, Assembly,Version, Culture, PublicKeyToken .

The custom field type definition should be added to the Visual Studio project in the following location: \TEMPLATE\XML\fldtypes_ CountryState.xml .

Step8:  Creating a Custom Field Value
One of the requirements of the ContryStateField custom field type was to store the data within a custom data structure. While it sounds a bit complex, it is actually very simple. The custom field value class is very handy with field types that are derived from the SPFieldMultiColumn field because data is stored in the SPFieldMultiColumn field as a special delimited string using ;# as the delimiter, and not just between two values but surrounding them ;#United States;#Florida;#

CountryStateValue.cs file containing the field value

using System;

using Microsoft.SharePoint;

namespace Sample.FieldType{

public class CountryStateValue : SPFieldMultiColumnValue {

private const int NUM_FIELDS = 2;

public CountryStateValue ()

: base(NUM_FIELDS) { }

public CountryStateValue (string value)

: base(value) { }

public string Country {

get { return this[0]; }

set { this[0] = value; }

}

public string State {

get {return this[1];}

set { this[1] = value; }

}

}

}

Step 9 : Creating a Custom Field Control

The first piece in a custom field control is the control class. This class must inherit from the Microsoft.SharePoint.WebControls.BaseFieldControl class or one that derives from it. For the CountryStateField , the BaseFieldControl will work.

using System;

using System.Collections.Generic;

using System.Text;

using Microsoft.SharePoint.WebControls;

using System.Web.UI.WebControls;

using Microsoft.SharePoint;

namespace Sample.FieldType

{

public class CountryStateControl : BaseFieldControl,IDesignTimeHtmlProvider

{

protected DropDownList _country;

protected DropDownList _StateSelector;

protected Literal _StateSelectorLiteral;

public override object Value {

get

{

EnsureChildControls();

CountryStateValue field = new CountryStateValue();

if (_country == null || _StateSelector == null )

{

field.Country = String.Empty;

field.State = String.Empty;

}

else

{

// set country value

if (_country.SelectedIndex == 0)

field.Country = String.Empty;

else

field.Country = _country.SelectedValue;

// set State value

if (_StateSelector.SelectedIndex == 0)

field.State = String.Empty;

else

field.State = _StateSelector.SelectedValue;

}

return field;

}

set

{

EnsureChildControls();

if (value != null && !string.IsNullOrEmpty(value.ToString()))

{

CountryStateValue field = new CountryStateValue(value.ToString());

_country.SelectedValue = field.Country;

if (_country.SelectedIndex > 0)

_StateSelector.SelectedValue = field.State;

SetStateControlVisibility(_country.SelectedIndex);

}

}

}

private void SetStateControlVisibility(int countrySelectedIndex)

{

switch (countrySelectedIndex)

{

case 0: // if none selected

_StateSelector.Visible = false;

_StateSelectorLiteral.Visible = false;

break;

default: sss

_StateSelector.Visible = true;

_StateSelectorLiteral.Visible = true;

break;

}

}

protected void Country_SelectedIndexChanged(object sender, EventArgs e)

{

EnsureChildControls();

//ADDstatesdependsonCountry(_country.SelectedIndex);

SetStateControlVisibility(_country.SelectedIndex);

}

protected void ADDstatesdependsonCountry(int countrySelectedIndex)

{

_StateSelector.Items.Clear();

//Code for Adding items to State dropdown depends on contry

}

void AddItesmsForContry()

{

//code for adding items to country dropdown

}

protected override void CreateChildControls()

{

if (this.Field == null || this.ControlMode == SPControlMode.Display ||this.ControlMode == SPControlMode.Invalid)

return;

base.CreateChildControls();

// get reference to Country selector

_country = new DropDownList();

_country.SelectedIndexChanged += new EventHandler(Country_SelectedIndexChanged);

_country.AutoPostBack = true;

//AddItesmsForContry()

_StateSelector = new  DropDownList();
_StateSelectorLiteral = new Literal();

//Add country ,state Selector and State Literal to control collection

this.Controls.Add(_country);

this.Controls.Add(_StateSelectorLiteral);

this.Controls.Add(_StateSelector);

}

}

}
Posted by

Friday, April 19, 2013

How to enable or disable AutoPlay in windows 8 ?

What is AutoPlay?

AutoPlay lets you choose an action for different kinds of media when you plug in a device, insert media, or receive content from another person using Tap and Send. You can set AutoPlay to open different kinds of content, such as photos, music, and video on different kinds of media, such as drives, CDs, or DVDs. For example, you can use AutoPlay to select an app that will automatically open photos on a removable drive when you plug it into your PC. With AutoPlay, you don't have to open the same app or reselect preferences every time you plug in a certain device. 

Step1:  Press "Windows Key + Q" to open the "App Search pane" and type "Control Panel" and select it from the search result.


You can also press "Windows Key + X" and select "Control Panel" from there.

Step2: In Control Panel window select "Hardware and Sound" option.



Step3: Next, select "AutoPlay" option.



Step4: In AutoPlay settings un-check "Use AutoPlay for all media and devices" option and click on" Save", to disable AutoPlay feature.



Please feel free to post your comments, I’ll be more than happy to assistant you.
Posted by
Labels:

SharePoint 2010 Productivity Hub – Direct download links

The Productivity Hub is a Microsoft SharePoint Server 2010 site collection that offers training material for end-users. It is fully customizable and Microsoft provides content packs with training materials that you can add to the Productivity Hub. You first need to install the Core before installing the different Content packs.
SharePoint 2010 Productivity Hub

Listed below are the different direct download links:
Quick steps to get started:
  1. Make sure that your SharePoint Server has the correct patching level – you will need to have SharePoint Server 2010 SP1 installed and SharePoint Server 2010 August 2011 Cumulative updates or later (KB2553050)
  2. Create a separate site collection for the Productivity hub
  3. Extract the core install file
  4. Unpack the content packs that you want to include and copy the different extracted folders underneath the core install directory. Remark: if the content packs are not imported you can still import them afterwards – check out the Microsoft Productivity Hub 2010 SP1 Installation Guide which is included in the Core install
  5. Install the Productivity Hub using a Powershell command which is included.
The code for the Productivity Hub Silverlight components and other add-ons are also available on Codeplex - http://productivityhub.codeplex.com/



 


 


 


The above procedure I got from Jop
Posted by

Microsoft to let Office 365 users replace SharePoint newsfeed with Yammer

Microsoft has offered more details about its plans to integrate SharePoint and Yammer, saying it'll give Office 365 customers the option of replacing SharePoint Online's activity-stream component with Yammer's.
Without committing to a specific date, Microsoft said it would provide this option during the summer. In the same timeframe, it will offer a Yammer application that will let users embed a Yammer group feed into a SharePoint site, Microsoft said. This Yammer application, which will be available on the SharePoint app store, will work both with SharePoint Online and with SharePoint 2013 servers installed on customer premises.
Later in the year, the integration will deepen with a single sign-on process for both products, and Yammer will be included in the Office 365 interface. Yammer will also gain integration with Office Web Apps, the browser-based version of the Office productivity suite.

In 2014, Office 365 customers can expect integration between Yammer and other Office 365 components beyond SharePoint, such as Lync and Exchange.
On Tuesday, Microsoft also reiterated that Yammer represents the future of the company's push for adding ESN (enterprise social networking) features to its products. However, Microsoft also said it recognises that some enterprises will be uncomfortable adopting Yammer, because it's a multi-tenant cloud service, so it will continue to offer and support SharePoint on premises.
Microsoft bought Yammer last summer for $1.2 billion, an acquisition that was seen as an acknowledgement by the company that it needed to improve its ESN capabilities in SharePoint and across its Office and business applications.
At its SharePoint Conference in November of last year, Microsoft said in a press release it planned to integrate Yammer and SharePoint in the areas of "unified identity, integrated document management and feed aggregation." However, Microsoft hadn't provided an update on those plans until today.
Microsoft bundles Yammer with some enterprise editions of Office 365, the cloud collaboration and email suite that includes SharePoint Online, Exchange Online, Lync Online and other components.

Posted by

How to Know when Your Computer Was Last Used?

Step1:  Go to Start > Run or press Window Keys + R. If you are running a version later than XP, you may need to type the following in smart search in the start menu.





Step2: Type 'eventvwr.msc' and press Enter.
 

Step3: The Event Viewer should come up .

if you are using Windows Vista and UAC pops up, choose Continue.


Step4: Open the System Log.



This is a log of everything that has happened recently on your computer with dates and times. You can use this data to find out when your computer was last used.
Posted by

Wednesday, April 17, 2013

Microsoft Windows history

                Highlights from the first 25 years

                                Getting started: Microsoft co-founders Paul Allen (left) and Bill Gates


1983
Bill Gates announces Microsoft Windows November 10, 1983.
1985
Microsoft Windows 1.0 is introduced in November 20, 1985 and is initially sold for $100.00.
1987
Microsoft Windows 2.0 was released December 9, 1987 and is initially sold for $100.00.
1987
Microsoft Windows/386 or Windows 386 is introduced December 9, 1987 and is initially sold for $100.00.
1988
Microsoft Windows/286 or Windows 286 is introduced June, 1988 and is initially sold for $100.00.
1990
Microsoft Windows 3.0 was released May, 22 1990. Microsoft Windows 3.0 full version was priced at $149.95 and the upgrade version was priced at $79.95.
1991
Following its decision not to develop operating systems cooperatively with IBM, Microsoft changes the name of OS/2 to Windows NT.
1991
Microsoft Windows 3.0 or Windows 3.0a with multimedia was released October, 1991.
1992
Microsoft Windows 3.1 was released April, 1992 and sells more than 1 Million copies within the first two months of its release.
1992
Microsoft Windows for Workgroups 3.1 was released October, 1992.
1993
Microsoft Windows NT 3.1 was released July 27, 1993.
1993
Microsoft Windows 3.11, an update to Windows 3.1 is released December 31, 1993.
1993
The number of licensed users of Microsoft Windows now totals more than 25 Million.
1994
Microsoft Windows for Workgroups 3.11 was released February, 1994.
1994
Microsoft Windows NT 3.5 was released September 21, 1994.
1995
Microsoft Windows NT 3.51 was released May 30, 1995.
1995
Microsoft Windows 95 was released August 24, 1995 and sells more than 1 Million copies within 4 days.
1995
Microsoft Windows 95 Service Pack 1 (4.00.950A) is released February 14, 1996.
1996
Microsoft Windows NT 4.0 was released July 29, 1996.
1996
Microsoft Windows 95 (4.00.950B) aka OSR2 with FAT32 and MMX support is released August 24, 1996.
1996
Microsoft Windows CE 1.0 was released November, 1996.
1997
Microsoft Windows CE 2.0 was released November, 1997.
1997
Microsoft Windows 95 (4.00.950C) aka OSR2.5 is released November 26, 1997.
1998
Microsoft Windows 98 was released June, 1998.
1998
Microsoft Windows CE 2.1 was released July, 1998.
1998
In October of 1998 Microsoft announced that future releases of Windows NT would no longer have the initials of NT and that the next edition would be Windows 2000.
1999
Microsoft Windows 98 SE (Second Edition) was released May 5, 1999.
1999
Microsoft Windows CE 3.0 was released 1999.
2000
On January 4th at CES Bill Gates announces the new version of Windows CE will be called Pocket PC.
2000
Microsoft Windows 2000 was released February 17, 2000.
2000
Microsoft Windows ME (Millennium) released June 19, 2000.
2001
Microsoft Windows XP is released October 25, 2001.
2001
Microsoft Windows XP 64-Bit Edition (Version 2002) for Itanium systems is released March 28, 2003.
2003
Microsoft Windows Server 2003 is released March 28, 2003.
2003
Microsoft Windows XP 64-Bit Edition (Version 2003) for Itanium 2 systems is released on March 28, 2003.
2003
Microsoft Windows XP Media Center Edition 2003 is released on December 18, 2003.
2004
Microsoft Windows XP Media Center Edition 2005 is released on October 12, 2004.
2005
Microsoft Windows XP Professional x64 Edition is released on April 24, 2005.
2005
Microsoft announces it's next operating system, codenamed "Longhorn" will be named Windows Vista on July 23, 2005.
2006
Microsoft releases Microsoft Windows Vista to corporations on November 30, 2006.
2007
Microsoft releases Microsoft Windows Vista and Office 2007 to the general public January 30, 2007.
2009
Microsoft releases Windows 7 October 22, 2009.
2012
Microsoft releases Windows 8 October 26, 2012.


 
Posted by
Subscribe to: Posts (Atom)