WSS Site Templates & Chicago SharePoint User Group Meeting

January 30th, 2007 by coskunc

Well yesterday was the event for Chicago SharePoint User Group and I finally got to meet with Lawrence and Rob. I actually worked with Rob on a project but it was over email and IM. So it was finally great to meet them and put a face to the name.

The event was great and gave great insight to the community, and I just wanted to thank Rob and Lawrence for coming out to Chicago.

Application Templates for Windows SharePoint Services 3.0
One of the biggest announcements was that the new application templates are now available. Here is the link so that you can download the templates and test them and see which one works for you.

http://www.microsoft.com/technet/windowsserver/sharepoint/wssapps/templates/default.mspx


Site Admin Templates
arrow Board of Directors
arrow Business Performance Reporting
arrow Case Management for Government Agencies
arrow Classroom Management
arrow Clinical Trial Initiation and Management
arrow Competitive Analysis Site
arrow Discussion Database
arrow Disputed Invoice Management
arrow Employee Activities Site
arrow Employee Self-Service Benefits
arrow Employee Training Scheduling and Materials
arrow Equity Research
arrow Integrated Marketing Campaign Tracking
arrow Manufacturing Process Management
arrow New Store Opening
arrow Product and Marketing Requirements Planning
arrow Request for Proposal
arrow Sports League
arrow Team Work Site
arrow Timecard Management

 

Another announcement we got was the new SharePoint Community Portal  url here you if you missed this link in the meeting –

http://sharepoint.microsoft.com/sharepoint/default.aspx

 

"My opinions do not reflect those of my blog host, SharePoint Experts"

WSS Site Templates & Chicago SharePoint User Group Meeting

January 30th, 2007 by coskunc

Well yesterday was the event for Chicago SharePoint User Group and I finally got to meet with Lawrence and Rob. I actually worked with Rob on a project but it was over email and IM. So it was finally great to meet them and put a face to the name.

The event was great and gave great insight to the community, and I just wanted to thank Rob and Lawrence for coming out to Chicago.

Application Templates for Windows SharePoint Services 3.0
One of the biggest announcements was that the new application templates are now available. Here is the link so that you can download the templates and test them and see which one works for you.

http://www.microsoft.com/technet/windowsserver/sharepoint/wssapps/templates/default.mspx


Site Admin Templates
arrow Board of Directors
arrow Business Performance Reporting
arrow Case Management for Government Agencies
arrow Classroom Management
arrow Clinical Trial Initiation and Management
arrow Competitive Analysis Site
arrow Discussion Database
arrow Disputed Invoice Management
arrow Employee Activities Site
arrow Employee Self-Service Benefits
arrow Employee Training Scheduling and Materials
arrow Equity Research
arrow Integrated Marketing Campaign Tracking
arrow Manufacturing Process Management
arrow New Store Opening
arrow Product and Marketing Requirements Planning
arrow Request for Proposal
arrow Sports League
arrow Team Work Site
arrow Timecard Management

 

Another announcement we got was the new SharePoint Community Portal  url here you if you missed this link in the meeting –

http://sharepoint.microsoft.com/sharepoint/default.aspx

 

"My opinions do not reflect those of my blog host, SharePoint Experts"

Content place holder FAQs and The Minimal Master Page minimal.master

January 19th, 2007 by coskunc

Why do I get an error when I delete some content placeholders?
In my last post I listed all of the default content placeholders and talked about how there are some content placeholders that are empty but we can't just take them out because when we do the page doesn't render properly and you get an error.

The reason why you get an error is because the content placeholder you remove is probably being used by some other page in that site since SharePoint master pages contain references to elements that is shared across multiple pages and when that page tries to place its own custom content in that placeholder it creates an error since there is no place to show the content.

For example the "PlaceHolderPageImage" is empty on the default.master page but the FormsAllItems.aspx uses that content placeholder to place the image (icon) for that page.

Why would you then take out a content placeholder from a master page if it throws an error?
This mostly is needed because you need to create a custom master page and you start from scratch because the default.master master page is not what you want.

The recommended approach when creating a new custom master page is to copy the default master page and start from there so you don't lose any of the required content placeholders when creating your own master page. But what if you don't like that master page and you want to start from scratch?

You can either manually create all of the content place holders I've listed in my earlier post or read below.

The answer = "Minimal Master Page"

The folks at Microsoft has created a great master page that is called the minimal master page as the name states is it's the minimal code you need to start a master page. So if you want to start from scratch and want a clean master page that has no styles attached to it this is by far the best way to do it.

Here is the Code for a Minimal Master Page

<%– Identifies this page as a .master page written in C# and registers tag prefixes, namespaces, assemblies, and controls. –%>
<%@ Master language="C#" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "
http://www.w3.org/TR/html4/loose.dtd">
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>
<%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %>
<%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %>
<%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %>
<%– Uses the Microsoft Office namespace and schema. –%>
<html>
  <WebPartPages:SPWebPartManager runat="server"/>
  <SharePoint:RobotsMetaTag runat="server"/>

  <%– The head section includes a content placeholder for the page title and links to CSS and JavaScript files that run on the server. –%>
  <head runat="server">
    <asp:ContentPlaceHolder runat="server" id="head">
      <title>
        <asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server" />
      </title>
    </asp:ContentPlaceHolder>
    <Sharepoint:CssLink runat="server"/>
    <asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server" />
  </head>
 
  <%– When loading the body of the .master page, MOSS 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. –%>
  <body onload="BLOCKED SCRIPT_spBodyOnLoadWrapper();">
    <%– The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. –%>
    <form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
      <wssuc:Welcome id="explitLogout" runat="server"/>
      <PublishingSiteAction:SiteActionMenu runat="server"/> 
      <PublishingWebControls:AuthoringContainer id="authoringcontrols" runat="server">
        <PublishingConsole:Console runat="server" />
      </PublishingWebControls:AuthoringContainer>
      <%– The PlaceHolderMain content placeholder defines where the page content should go for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. –%>
      <asp:ContentPlaceHolder id="PlaceHolderMain" runat="server" />
        <asp:Panel visible="false" runat="server">

        <%– These ContentPlaceHolders are only necessary to ensure all out of the box MOSS 2007 pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. –%>
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea"  runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>
</asp:Panel>
    </form>
  </body>
</html>


To create a minimal master page

  1. Open SharePoint Designer.

  2. On the File menu, click New, point to SharePoint Content, and click the Page tab.

  3. Double-click Master Page to create a new master page.

  4. Click Design to show the master page in design view. The master page covers the header and left margin areas, and several content placeholders are visible.

  5. Click Code to show the master page in code view.

  6. Copy and paste the code above into the master page.

To learn more about the minimal master place please visit
How to: Create a Minimal Master Page 

Content place holder FAQs and The Minimal Master Page minimal.master

January 19th, 2007 by coskunc

Why do I get an error when I delete some content placeholders?
In my last post I listed all of the default content placeholders and talked about how there are some content placeholders that are empty but we can't just take them out because when we do the page doesn't render properly and you get an error.

The reason why you get an error is because the content placeholder you remove is probably being used by some other page in that site since SharePoint master pages contain references to elements that is shared across multiple pages and when that page tries to place its own custom content in that placeholder it creates an error since there is no place to show the content.

For example the "PlaceHolderPageImage" is empty on the default.master page but the FormsAllItems.aspx uses that content placeholder to place the image (icon) for that page.

Why would you then take out a content placeholder from a master page if it throws an error?
This mostly is needed because you need to create a custom master page and you start from scratch because the default.master master page is not what you want.

The recommended approach when creating a new custom master page is to copy the default master page and start from there so you don't lose any of the required content placeholders when creating your own master page. But what if you don't like that master page and you want to start from scratch?

You can either manually create all of the content place holders I've listed in my earlier post or read below.

The answer = "Minimal Master Page"

The folks at Microsoft has created a great master page that is called the minimal master page as the name states is it's the minimal code you need to start a master page. So if you want to start from scratch and want a clean master page that has no styles attached to it this is by far the best way to do it.

Here is the Code for a Minimal Master Page

<%– Identifies this page as a .master page written in C# and registers tag prefixes, namespaces, assemblies, and controls. –%>
<%@ Master language="C#" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "
http://www.w3.org/TR/html4/loose.dtd">
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>
<%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %>
<%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %>
<%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %>
<%– Uses the Microsoft Office namespace and schema. –%>
<html>
  <WebPartPages:SPWebPartManager runat="server"/>
  <SharePoint:RobotsMetaTag runat="server"/>

  <%– The head section includes a content placeholder for the page title and links to CSS and JavaScript files that run on the server. –%>
  <head runat="server">
    <asp:ContentPlaceHolder runat="server" id="head">
      <title>
        <asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server" />
      </title>
    </asp:ContentPlaceHolder>
    <Sharepoint:CssLink runat="server"/>
    <asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server" />
  </head>
 
  <%– When loading the body of the .master page, MOSS 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. –%>
  <body onload="BLOCKED SCRIPT_spBodyOnLoadWrapper();">
    <%– The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. –%>
    <form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
      <wssuc:Welcome id="explitLogout" runat="server"/>
      <PublishingSiteAction:SiteActionMenu runat="server"/> 
      <PublishingWebControls:AuthoringContainer id="authoringcontrols" runat="server">
        <PublishingConsole:Console runat="server" />
      </PublishingWebControls:AuthoringContainer>
      <%– The PlaceHolderMain content placeholder defines where the page content should go for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. –%>
      <asp:ContentPlaceHolder id="PlaceHolderMain" runat="server" />
        <asp:Panel visible="false" runat="server">

        <%– These ContentPlaceHolders are only necessary to ensure all out of the box MOSS 2007 pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. –%>
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea"  runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>
</asp:Panel>
    </form>
  </body>
</html>


To create a minimal master page

  1. Open SharePoint Designer.

  2. On the File menu, click New, point to SharePoint Content, and click the Page tab.

  3. Double-click Master Page to create a new master page.

  4. Click Design to show the master page in design view. The master page covers the header and left margin areas, and several content placeholders are visible.

  5. Click Code to show the master page in code view.

  6. Copy and paste the code above into the master page.

To learn more about the minimal master place please visit
How to: Create a Minimal Master Page 

The default content placeholders on Default.master in a Windows SharePoint Services 3.0 site

January 19th, 2007 by coskunc

If you have been working with the SharePoint 2007 master pages you probably have seen many placeholders with no content in them and some with content. But what are these content placeholders? Why is it in there? If you find yourself asking these questions here is a great article on content placeholders that would be a good place to start reading.

Here is a table that identifies all of the default content placeholders and explains what they represent

 

Content placeholder                    Description
PlaceHolderBodyAreaClass Additional body styles in the page header
PlaceHolderBodyLeftBorder Border element for the main page body
PlaceHolderBodyRightMargin Right margin of the main page body
PlaceHolderCalendarNavigator Shows a date-picker for navigating in a calendar when a calendar is visible on the page
PlaceHolderFormDigest The "form digest" security control
PlaceHolderGlobalNavigation The global navigation breadcrumb
PlaceHolderHorizontalNav Top navigation menu for the page
PlaceHolderLeftActions Bottom of the left navigation area
PlaceHolderLeftNavBar Left navigation area
PlaceHolderLeftNavBarBorder Border element on the left navigation bar
PlaceHolderLeftNavBarDataSource Data source for the left navigation menu
PlaceHolderLeftNavBarTop Top of the left navigation area
PlaceHolderMain Main content of the page
PlaceHolderMiniConsole A place to show page-level commands, for example, WIKI commands such as Edit Page, History, and Incoming Links
PlaceHolderNavSpacer The width of the left navigation area
PlaceHolderPageDescription Description of the page contents
PlaceHolderPageImage Page icon in the upper-left area of the page
PlaceHolderSearchArea Search box area
PlaceHolderSiteName Site name
PlaceHolderTitleAreaClass Additional styles in the page header
PlaceHolderTitleAreaSeparator Shows shadows for the title area
PlaceHolderTitleBreadcrumb Main content breadcrumb area
PlaceHolderPageTitleInTitleArea Page title shown immediately below the breadcrumbs
PlaceHolderTitleLeftBorder Left border of the title area
PlaceHolderTitleRightMargin Right margin of the title area
PlaceHolderTopNavBar Top navigation area
PlaceHolderUtilityContent Extra content at the bottom of the page
SPNavigation Empty by default in Windows SharePoint Services 3.0. Can be used for additional page editing controls.
WSSDesignConsole The page editing controls when the page is in Edit Page mode (in the browser, click Site Actions, and then click Edit Page)

 

The default content placeholders on Default.master in a Windows SharePoint Services 3.0 site

January 19th, 2007 by coskunc

If you have been working with the SharePoint 2007 master pages you probably have seen many placeholders with no content in them and some with content. But what are these content placeholders? Why is it in there? If you find yourself asking these questions here is a great article on content placeholders that would be a good place to start reading.

Here is a table that identifies all of the default content placeholders and explains what they represent

 

Content placeholder                    Description
PlaceHolderBodyAreaClass Additional body styles in the page header
PlaceHolderBodyLeftBorder Border element for the main page body
PlaceHolderBodyRightMargin Right margin of the main page body
PlaceHolderCalendarNavigator Shows a date-picker for navigating in a calendar when a calendar is visible on the page
PlaceHolderFormDigest The "form digest" security control
PlaceHolderGlobalNavigation The global navigation breadcrumb
PlaceHolderHorizontalNav Top navigation menu for the page
PlaceHolderLeftActions Bottom of the left navigation area
PlaceHolderLeftNavBar Left navigation area
PlaceHolderLeftNavBarBorder Border element on the left navigation bar
PlaceHolderLeftNavBarDataSource Data source for the left navigation menu
PlaceHolderLeftNavBarTop Top of the left navigation area
PlaceHolderMain Main content of the page
PlaceHolderMiniConsole A place to show page-level commands, for example, WIKI commands such as Edit Page, History, and Incoming Links
PlaceHolderNavSpacer The width of the left navigation area
PlaceHolderPageDescription Description of the page contents
PlaceHolderPageImage Page icon in the upper-left area of the page
PlaceHolderSearchArea Search box area
PlaceHolderSiteName Site name
PlaceHolderTitleAreaClass Additional styles in the page header
PlaceHolderTitleAreaSeparator Shows shadows for the title area
PlaceHolderTitleBreadcrumb Main content breadcrumb area
PlaceHolderPageTitleInTitleArea Page title shown immediately below the breadcrumbs
PlaceHolderTitleLeftBorder Left border of the title area
PlaceHolderTitleRightMargin Right margin of the title area
PlaceHolderTopNavBar Top navigation area
PlaceHolderUtilityContent Extra content at the bottom of the page
SPNavigation Empty by default in Windows SharePoint Services 3.0. Can be used for additional page editing controls.
WSSDesignConsole The page editing controls when the page is in Edit Page mode (in the browser, click Site Actions, and then click Edit Page)

 

Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions

January 12th, 2007 by coskunc

Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions

If you are a SharePoint developer and or want to develop for SharePoint 2007 and if you haven't installed this tool yet don't even waste a minute get this NOW!

What do you get with this tool?


Visual Studio 2005 Project Templates

  • Web Part
  • Team Site Definition
  • Blank Site Definition
  • List Definition

Visual Studio 2005 Item Templates (items that can be added into an existing project)

  • Web Part
  • Custom Field
  • List Definition (with optional Event Receiver)
  • Content Type (with optional Event Receiver)
  • Module

SharePoint Solution Generator

  • This stand-alone program generates a Site Definition project from an existing SharePoint site. The program enables developers to use the browser and Microsoft Office SharePoint Designer to customize the content of their sites before creating code by using Visual Studio.

 

 

Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions

January 12th, 2007 by coskunc

Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions

If you are a SharePoint developer and or want to develop for SharePoint 2007 and if you haven't installed this tool yet don't even waste a minute get this NOW!

What do you get with this tool?


Visual Studio 2005 Project Templates

  • Web Part
  • Team Site Definition
  • Blank Site Definition
  • List Definition

Visual Studio 2005 Item Templates (items that can be added into an existing project)

  • Web Part
  • Custom Field
  • List Definition (with optional Event Receiver)
  • Content Type (with optional Event Receiver)
  • Module

SharePoint Solution Generator

  • This stand-alone program generates a Site Definition project from an existing SharePoint site. The program enables developers to use the browser and Microsoft Office SharePoint Designer to customize the content of their sites before creating code by using Visual Studio.

 

 

I've been tagged? What is this?

January 12th, 2007 by coskunc

I've been tagged by a fellow friend John Holliday. Well at first I didn't know what this was all about. Working long hours makes you not not bknow about these things :) So I googled the "I've been tagged" phrase and my god there was 45M results..

Results 110 of about 44,900,000 for I've Been Tagged! . (0.12 seconds) 

Well this is a crazy little game but I like it. Even though I have no time to tagg 5 people I'll still write 5 things about me.

1. I'm married and expecting a baby girl by mid February. We will name her Tuana Ilayda Cavusoglu.

2. Love sports but only good at watching. I am a die hard Fenerbahce S.K. fan. I never missed a game when I lived in Turkey. It's kind of hard to watch their games now that I live in Chicago. But now that I live in Chicago I found a couple of teams I fell in love with over the years the Chicago Bears and a Chicago Cubs. (Go Bears!) And also another soccer team I root for is F.C. Barcelona

3. I lived in Burgos/Spain, Istanbul/Turkey and Chennai/India.

4. I graduated from ISIK University at Istanbul,Turkey

5. Was born in the USA but have Turkish parents.

I've been tagged? What is this?

January 12th, 2007 by coskunc

I've been tagged by a fellow friend John Holliday. Well at first I didn't know what this was all about. Working long hours makes you not not bknow about these things :) So I googled the "I've been tagged" phrase and my god there was 45M results..

Results 110 of about 44,900,000 for I've Been Tagged! . (0.12 seconds) 

Well this is a crazy little game but I like it. Even though I have no time to tagg 5 people I'll still write 5 things about me.

1. I'm married and expecting a baby girl by mid February. We will name her Tuana Ilayda Cavusoglu.

2. Love sports but only good at watching. I am a die hard Fenerbahce S.K. fan. I never missed a game when I lived in Turkey. It's kind of hard to watch their games now that I live in Chicago. But now that I live in Chicago I found a couple of teams I fell in love with over the years the Chicago Bears and a Chicago Cubs. (Go Bears!) And also another soccer team I root for is F.C. Barcelona

3. I lived in Burgos/Spain, Istanbul/Turkey and Chennai/India.

4. I graduated from ISIK University at Istanbul,Turkey

5. Was born in the USA but have Turkish parents.