Wednesday, January 04, 2012
Saturday, November 05, 2011
In pursuit with the world’s largest jigsaw puzzle
One of my ambitions is to do the worlds largest jigsaw puzzle (called LIFE) which is 24000 pieces in future.In doing so I have started the miniature version of LIFE which is 3000 pieces.Currently I have completed quarter of it which is around 700-800 pieces.Planning to complete this end of the year if time permits to do so.
Here is the full image of LIFE after you complete it.
Here is my last puzzle.
Friday, October 21, 2011
Configuring Forms Based Authentication (FBA) in SharePoint 2010
Steps
- Create MSSQL membership store
- Create the new web application
- Configure support for FBA
- In Central Administration
- In new web application
- In STS web service (new in SharePoint 2010)
- Adding user policies to the web application
- Login to the site
This is where all the user details going to be store.
- Create the database
- Run the ASP.NET SQL Server Setup Wizard located at C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe and follows the instructions.
- Once completed create a separate database user and assign that user and add the “db_owner” role.
- Add users into the membership store
- Launch the Visual Studio and create a web site project
- Add a connection string pointing to the above created database
- Launch the “ASP.NET Configuration” wizard in “Website” menu item.
- Click on the “Security” link and select the “internet” option and add users in to the store.
Step 2: Create the new web application
- Go to Central Administration > Manage web applications and click on the “New” in the ribbon
- Set the settings in the dialog box as in the below images (Check the red boxes)
- Once the web application created, create the site collection as well.
- Edit the web.config for the central administration in the virtual directories folder
- Add the following entry just above the </system.web> node
<membership defaultProvider="AspNetSqlMembershipProvider">
<providers>
<remove name="AspNetSqlMembershipProvider" />
<add connectionStringName="AspNetSqlProvider" passwordAttemptWindow="10" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" description="Stores and retrieves membership data from the Microsoft SQL Server database" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</providers>
</membership>
<roleManager defaultProvider="AspNetWindowsTokenRoleProvider">
<providers>
<clear />
<remove name="AspNetSqlRoleProvider" />
<add connectionStringName="AspNetSqlProvider" applicationName="/" description="Stores and retrieves roles data from the local Microsoft SQL Server database" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</providers>
</roleManager>
- Add the below connectionString details just above the </configuration> node and put the corresponding values for the database,user id and password
<connectionStrings>
<add connectionString="Data Source=eccolw7ira;Initial Catalog=<database>;User ID=<user id>;Password=<password>" name="AspNetSqlProvider" />
</connectionStrings>
- Edit the web.config for the corresponding site in the virtual directories folder
- Add the following entry just above the </system.web> node.
- Note : If the membership entry is already available , add only the missing entries (Highlighted in Yellow) from the bellow entry.
| <membership defaultProvider="i"> <providers> <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlMembershipProvider" /> <add connectionStringName="AspNetSqlProvider" passwordAttemptWindow="10" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" description="Stores and retrieves membership data from the Microsoft SQL Server database" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </membership> <roleManager defaultProvider="c"> <providers> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlRoleProvider" /> <add connectionStringName="AspNetSqlProvider" applicationName="/" description="Stores and retrieves roles data from the local Microsoft SQL Server database" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </roleManager> |
- Add the below connectionString details just above the </configuration> node and put the corresponding values for the database,user id and password
| <connectionStrings> <add connectionString="Data Source=eccolw7ira;Initial Catalog=<database>;User ID=<user id>;Password=<password>" name="AspNetSqlProvider" /> </connectionStrings> |
- Edit the web.config located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken
- Add the following entry just above the </configuration> node
| <system.web> <membership defaultProvider="AspNetSqlMembershipProvider"> <providers> <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlMembershipProvider" /> <add connectionStringName="AspNetSqlProvider" passwordAttemptWindow="10" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" description="Stores and retrieves membership data from the Microsoft SQL Server database" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </membership> <roleManager defaultProvider="AspNetSqlRoleProvider" enabled="true" cacheRolesInCookie="false"> <providers> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <remove name="AspNetSqlRoleProvider" /> <add connectionStringName="AspNetSqlProvider" applicationName="/" description="Stores and retrieves roles data from the local Microsoft SQL Server database" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </roleManager> </system.web> <connectionStrings> <add connectionString="Data Source=eccolw7ira;Initial Catalog=<database>;User ID=<user id>;Password=<password>" name="AspNetSqlProvider" /> </connectionStrings> |
- Go to Central administration > Manage web applications and select the web application and click on the “User Ploicy” button in ribbon.
- Click on the “Add users” link and select the “Default” as the zone and click on “Next”.
- Type the user name in the “Users” text box and click on the People Picker icon.
- If everything configured correctly you should see the user name get underlined in the “users” box. OR
- Click on the “Browse” button under the users text box and type the user name in the search text box and click on the search button.
- And you should see the user name in the search result.
Step 5: Login to the site
- Open the site in browser and select the “Forms Authentication” from the drop down
- Provide the user credentials and you should be redirected to the home page
Wednesday, May 18, 2011
Setting assembly version automatically when building in a Bamboo server
How to instruct your msbuild script to set the correct “AssemblyVersion” of your libraries using “AssemblyInfo.cs” when building in a Bamboo server.In Puzzlepart it is vital to have the current build number and the current revision number in the assembly version of products.
Solution :
Assembly version syntax : <major version>.<minor version>.<build number>.<revision>
More info can be found here about the syntax.
Step 1 : First you need to make sure the corresponding Build-Specific Variable are passed into the build script.
How ?
In Bamboo build configuration under the “Builder” tab you have “Options” where you can pass msbuild command line switches.Step 2 : Accessing those variables from the msbuild script
example : /p:BuildKey=${bamboo.buildKey} /p:BuildPlanName=${bamboo.buildPlanName} /p:BuildNumber=${bamboo.buildNumber} /p:Revision=${bamboo.custom.svn.revision.number}
![]()
<PropertyGroup>Step 3 : Create the Assembly version using those properties
<MajorVersion Condition="'$(MajorVersion)' == ''">1</MajorVersion>
<MinorVersion Condition="'$(MinorVersion)' == ''">0</MinorVersion>
<BuildNumber Condition="'$(BuildNumber)' == ''">0</BuildNumber>
<Revision Condition="'$(Revision)' == ''">0</Revision>
<BuildPlanName Condition="'$(BuildPlanName)' == ''">LocalBuild</BuildPlanName>
<BuildKey Condition="'$(BuildKey)' == ''">NOKEY</BuildKey>
</PropertyGroup>
<PropertyGroup>Step 4 : Use the assembly version in “AssemblyInfo” task
<ComputedAssemblyName>$(MajorVersion).$(MinorVersion).$(BuildNumber).$(Revision)</ComputedAssemblyName>
</PropertyGroup>
<AssemblyInfo CodeLanguage="CS"
OutputFile="$(ApplicationName)\Properties\AssemblyInfo.cs"
AssemblyTitle="ApplicationName"
AssemblyDescription="Description"
AssemblyCompany=""
AssemblyProduct="$(ApplicationName)"
AssemblyCopyright="Copyright © "
ComVisible="false"
CLSCompliant="false"
Guid="248D49F7-BC5D-4413-8E4A-98B4654B1594"
AssemblyVersion="$(ComputedAssemblyName)" />
Monday, February 14, 2011
Arctic SharePoint Challenge 2011
Are you ready to take on the challenge ?
Visit http://arcticsharepointchallenge.com/ for more info and feel free to follow @SPChallenge (Dexter the Lynx challenge mascot) on twitter.
Sunday, November 14, 2010
2010 Formula 1 world champion decider at Yas Marina circuit in Abu Dhabi
| Pos | Driver | Nationality | Team | Points |
1 | Fernando Alonso | Spanish | Ferrari | 246 |
| 2 | Mark Webber | Australian | RBR-Renault | 238 |
| 3 | Sebastian Vettel | German | RBR-Renault | 231 |
| 4 | Lewis Hamilton | British | McLaren-Mercedes | 222 |
Saturday, November 06, 2010
First ever series win in Australia
Wednesday, September 29, 2010
Integrating ReSharper into Visual Studio 2010
Sunday, September 05, 2010
SharePoint 2010 : First custom connector implementation for BCS
Found out this code snippet from MSDN for a connector to the file system.
Managed to complete this exercise and created an external list with the External Content Type and I did see the files from the file system in the list.See bellow images.
Folder contents in file system :
External list in SP context :
I am really impressed by this and it has already inspired me to go deep into this and hoping to create some more custom connectors for other external systems as well.
Found out lot of issues/problems while I am doing this and I just list down possible erroneous scenarios.
- Business Data Connectivity Services issues
- Assembly deployment to the GAC
- Assembly information
- Configure Business Data Connectivity access rights
Error accessing Business Data Connectivity Services in Windows 7
While I was doing some research on BCS , wanted to import a BDC model from Central Administration > Manage service applications > Business Data Connectivity Services.
As I hit the link, following error message prompted.
As usual did a search on the Google and found out the following entries.
http://sensoft2000-sharepoint.blogspot.com/2010/08/error-access-services-is-unable-to.html
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806
Downloaded the above fix and installed.
problem solved. :)
More references on the issue :
http://support.microsoft.com/kb/976462
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=976462&kbln=en-us
Thursday, August 26, 2010
How to send Ctrl-Alt-Del key combination in remote desk top
How many times I have to search web, to find out the correct key combination to send ctrl+alt+del into remote desk top.Here it is.This will be a self note to me on this regard.From here onwards I won’t be searching the web but in my blog only, if and only if I forgot it :)
CTRL + ALT + END
CTRL + ALT + END
CTRL + ALT + END
CTRL + ALT + END
CTRL + ALT + END
…
Monday, July 12, 2010
Sharepoint foundation 2010 on windows 7 x64
The second step under “To set up a developer workstation” failed successfully because of this command “c:\SharePointFiles\SharePoint /extract:c:\SharePointFiles”
Here it referred to a file called “SharePoint” but the name of the downloaded application was “SharePointFoundation.exe”. So in order to pass this step I had to change the name from “SharePoint” to “SharePointFoundation” in the above command.
After that I continued with the installation steps and managed to launch the setup.exe after completing the installation of prerequisites mentioned.
In the 3rd step under the “Step 3: Install SharePoint 2010” I select the “Server Farm” option and in the next step I selected the standalone option.I had no clue what so ever why I selected that option, but it happened for some reason and it worked.
Then I had to wait for a quite a longer time to complete the installation and prompted to run the sharepoint configuration wizard.
And finally after the configuration wizard completed, it prompted the newly created sharepoint team site.(See image at top)
Now sharepoint foundation 2010 at my finger tips so that I can start playing with it.
Sunday, July 11, 2010
My classical box guitar
Tuesday, July 06, 2010
Web services extensions option in IIS7
Monday, May 10, 2010
Wednesday, April 28, 2010
Pool table in action
Saturday, April 10, 2010
How many of you remember Upali Wijewardena
Friday, April 09, 2010
An article by CIO of Xtra personnel (http://xtra.no)
---- Translated text removed from here -----


