Tuesday, March 8, 2011
Monday, March 7, 2011
LINQ to SQL Full
LINQ to SQL
- Part 1: Introduction to LINQ to SQL
- Part 2: Defining our Data Model Classes
- Part 3: Querying our Database
- Part 4: Updating our Database
- Part 5: Binding UI using the ASP:LinqDataSource Control
- Part 6: Retrieving Data Using Stored Procedures
- Part 7: Updating our Database using Stored Procedures
- Part 8: Executing Custom SQL Expressions
Tuesday, March 1, 2011
Installing SharePoint Server-2010
Installing SharePoint Server-2010
2)Create a Sharepoint 2010 VM in 32 bits host machine
Download doc for details
1)How to install SPS2010 in Single Box Development Server?
1. After you have finished installing OS, start to add Active Directory Domain Service roles.
Complete the installation procedure and configure the roles.
2. Then, start to add Application Server and Web Server roles.
This installation is straight forward, and you will be easily get your Application Server and Web Server roles configured in the machine.
3. Install SQL Server 2008 SP1 + CU KB970315
Download SQL Server 2008 SP1 here: http://www.microsoft.com/downloads/details.aspx?familyid=66AB3DBB-BF3E-4F46-9559-CCC6A4F9DC19&displaylang=en
Download CU KB970315 here: http://support.microsoft.com/kb/970315
And here is the tricky part, installing SPS2010
4. Extract SPS2010 installer to a folder
/extract:e:\sps2010
That command will extract to folder e:\sps2010. Replace with your own distribution.
5. You will see that there is several sub-folder under Files folder in the extracted location. Each sub-folder represents different setup option. For example, SetupFarm contains configuration files for farm installation option etc.
6. Start the installation sequence by executing following command in the extracted location.
Setup.exe /config Files\SetupFarm\config.xml
Refer:
http://andreasglaser.net/post/2009/11/17/Installing-SharePoint-Server-2010-on-Windows-Server-2008-R2-and-SQL-Server-2008-R2-Part-1-Overview.aspx
http://www.ericharlan.com/Moss_SharePoint_2007_Blog/how-to-install-sharepoint-2010-guide-a166.html
1)How to install SPS2010 in Single Box Development Server?
2)Create a Sharepoint 2010 VM in 32 bits host machine
Download doc for details
1)How to install SPS2010 in Single Box Development Server?
1. After you have finished installing OS, start to add Active Directory Domain Service roles.
Complete the installation procedure and configure the roles.
2. Then, start to add Application Server and Web Server roles.
This installation is straight forward, and you will be easily get your Application Server and Web Server roles configured in the machine.
3. Install SQL Server 2008 SP1 + CU KB970315
Download SQL Server 2008 SP1 here: http://www.microsoft.com/downloads/details.aspx?familyid=66AB3DBB-BF3E-4F46-9559-CCC6A4F9DC19&displaylang=en
Download CU KB970315 here: http://support.microsoft.com/kb/970315
And here is the tricky part, installing SPS2010
4. Extract SPS2010 installer to a folder
That command will extract
5. You will see that there is several sub-folder under Files folder in the extracted location. Each sub-folder represents different setup option. For example, SetupFarm contains configuration files for farm installation option etc.
6. Start the installation sequence by executing following command in the extracted location.
Setup.exe /config Files\SetupFarm\config.xml
Refer:
http://andreasglaser.net/post/2009/11/17/Installing-SharePoint-Server-2010-on-Windows-Server-2008-R2-and-SQL-Server-2008-R2-Part-1-Overview.aspx
http://www.ericharlan.com/Moss_SharePoint_2007_Blog/how-to-install-sharepoint-2010-guide-a166.html
Wednesday, February 23, 2011
Tuesday, February 15, 2011
test
There are lot of things going on in the DDF file, but here is what I think is important to understand.
- Comments in the file begin with a semi-colon
- .OPTION lines tell the MAKECAB utility what options to use when building the CAB archive
- .Set lines tell the MAKECAB utility what values to apply to certain parameters that are used when building the CAB archive
- Make sure the CabinetNameTemplate parameter is set to what the name of the WSP file will be (in the example above the MAKECAB utility will generate a CAB archive named my.wsp)
- Each content file to be added to the CAB archive is listed on a line in a space separated source-destination format
- For example, this CAB archive will contain an HTML file (my.html); the last line in the example above tells the MAKECAB utility to grab the my.html file from the file system (the source location) and place copy it to LAYOUTS/mysample/my.html in the CAB archive (the destination location)
- Double quotes can be used to define sources that contain spaces in the path or file name
- Make sure to include the solution meta-data XML file (manifest.xml) at the root of the CAB archive
The next step is to create the solution manifest file .
The example is a very simple solution manifest, but there are a couple of things to take away from it.
- Every solution has a GUID (globally unique identifier) that identifies uniquely
- As a general rule, every deployment file, schema,
test
There are lot of things going on in the DDF file, but here is what I think is important to understand.
* Comments in the file begin with a semi-colon
* .OPTION lines tell the MAKECAB utility what options to use when building the CAB archive
* .Set lines tell the MAKECAB utility what values to apply to certain parameters that are used when building the CAB archive
o Make sure the CabinetNameTemplate parameter is set to what the name of the WSP file will be (in the example above the MAKECAB utility will generate a CAB archive named my.wsp)
* Each content file to be added to the CAB archive is listed on a line in a space separated source-destination format
o For example, this CAB archive will contain an HTML file (my.html); the last line in the example above tells the MAKECAB utility to grab the my.html file from the file system (the source location) and place copy it to LAYOUTS/mysample/my.html in the CAB archive (the destination location)
o Double quotes can be used to define sources that contain spaces in the path or file name
o Make sure to include the solution meta-data XML file (manifest.xml) at the root of the CAB archive
The next step is to create the solution manifest file .
The example is a very simple solution manifest, but there are a couple of things to take away from it.
* Every solution has a GUID (globally unique identifier) that identifies uniquely
* As a general rule, every deployment file, schema,
* Comments in the file begin with a semi-colon
* .OPTION lines tell the MAKECAB utility what options to use when building the CAB archive
* .Set lines tell the MAKECAB utility what values to apply to certain parameters that are used when building the CAB archive
o Make sure the CabinetNameTemplate parameter is set to what the name of the WSP file will be (in the example above the MAKECAB utility will generate a CAB archive named my.wsp)
* Each content file to be added to the CAB archive is listed on a line in a space separated source-destination format
o For example, this CAB archive will contain an HTML file (my.html); the last line in the example above tells the MAKECAB utility to grab the my.html file from the file system (the source location) and place copy it to LAYOUTS/mysample/my.html in the CAB archive (the destination location)
o Double quotes can be used to define sources that contain spaces in the path or file name
o Make sure to include the solution meta-data XML file (manifest.xml) at the root of the CAB archive
The next step is to create the solution manifest file .
The example is a very simple solution manifest, but there are a couple of things to take away from it.
* Every solution has a GUID (globally unique identifier) that identifies uniquely
* As a general rule, every deployment file, schema,
Monday, February 14, 2011
How to Add STSADM in path using Windows Server 2008
I always keep STSADM in path, because it very useful. You can also create a shortcut for command prompt configured for STSADM.
For Sharepoint 2007
Usually STSADM.exe exist in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\.
For Sharepoint 2010
Usually STSADM.exe exist in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\
Click on ‘Start’
Right Click on ‘Computer’ and select Properties
Select ‘Advanced System Settings’
Click on the ‘Environment Variables…’
Now select the ‘Path’ from system variables
Click Edit
Their will be already may be some path available you just append this new path
first add ;(semicolon) then your path of BIN folder (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\
) where stsadm.exe will be.
Add this path (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN) in existing path seprated by ‘;’
Thats all, now you can use STSADM from anywherein command prompt.
For Sharepoint 2007
Usually STSADM.exe exist in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\.
For Sharepoint 2010
Usually STSADM.exe exist in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\
Click on ‘Start’
Right Click on ‘Computer’ and select Properties
Select ‘Advanced System Settings’
Click on the ‘Environment Variables…’
Now select the ‘Path’ from system variables
Click Edit
Their will be already may be some path available you just append this new path
first add ;(semicolon) then your path of BIN folder (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\
) where stsadm.exe will be.
Add this path (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN) in existing path seprated by ‘;’
Thats all, now you can use STSADM from anywherein command prompt.