How To Access TFS 2010 From Visual Studio 2005

December 2, 2011

To connect to Team Foundation Server (TFS) 2010 from Visual Studio 2005, Following software updates should be installed on a machine.

This is a working solution. I tested it.

  1. Visual Studio 2005, a pre-requisite
  2. Visual Studio Team System 2005 Team Explorer, Download from here
  3. Visual Studio 2005 Team Suite Service Pack 1, Download from here
  4. Visual Studio Team System 2005 SP1 Forward Compatibility update for TFS 2010, Download from here
Advertisements

How To Access Team Foundation Server 2010 From Visual Studio 2008

December 2, 2011

I encountered a scenario to connect to TFS 2010 from Visual Studio 2008. Did a little googling and came up with quick check list of software components necessary to achieve this.

Catch here is to follow the order of installation.

  1. You must have Visual Studio 2008 installed 🙂 Off course You had it installed, that’s why you can under this situation you reading this blog post.
  2. Install Visual Studio Team System Explorer. Download from here
  3. Install Visual Studio 2008 Service Pack 1. Download from here
  4. Install Visual Studio Team System 2008 Forward Compatbility Update for TFS 2010. Download from here

Configuring In Place Records Management In SharePoint 2010

June 27, 2011

Any SharePoint 2010 Document Library Can be configured for in place records management. This will be explained in this post.

When we click a document, Manage section on the ribbon has no button for declaring it a records. This can be seen in the screen shot given below. This means in place records management feature is not enabled on this document library. One thing to remember here is that In Place Records Management is site collection level feature.

  1. Go to site collection features and look for “In Place Records Management” feature. Before enabling, it will look like this:

  2. After activation, feature will look like this:


    At this stage in place records management feature is enabled, but Declare Record button will not appear on ribbon. We need to do one more setting here.

  3. Now go to document library setting page and click link as shown in screen shot below:

  4. Click the radio button as shown in screen shot below and click ok.

  5. After these settings document library will show Declare Record button. Declare Record button is disabled because we have not selected any document. This implies, in place records management can be applied to single document at a time.

  6. Select a document in document library, declare record button will be enabled.

  7. Click Declare Record button on the ribbon and you are done with declaring a record.

Enjoy SharePoint 2010.


Create Managed Metadata Column using Power Shell

June 15, 2011

Although creating a managed metadata column is pretty straight forward using a web browser. But sometimes we need to automate things, if we need to create bulk of columns.

Here is a code snippet to achieve this.

$siteUrl = “http://somesharepointweb”;
$fieldName = “Region”;
$fieldGroup = “Custom”;
$allowMultipleValues = “false”;
$isRequired = “true”;
$termStoreName = “Managed Metadata Service”;
$termGroupName = “Intranet”;
$termSetName = “North America”

#Get sp web
$site = New-Object -TypeName “Microsoft.SharePoint.SPSite” -ArgumentList $siteUrl;

$fieldType = “”;
$bAllowMulitpleValues = “”;
$bIsRequired = “”;

if ($allowMultipleValues.ToLower() -eq “true”)
{
$fieldType = “TaxonomyFieldTypeMulti”
}
else
{
$fieldType = “TaxonomyFieldType”
}
if ($allowMultipleValues.ToLower() -eq “true”)
{
$bAllowMulitpleValues = $true;
}
else
{
$bAllowMulitpleValues = $false;
}

if ($isRequired.ToLower() -eq “true”)
{
$bIsRequired = $true;
}
else
{
$bIsRequired = $false;
}

#Create a taxonomy field
$field = [Microsoft.SharePoint.Taxonomy.TaxonomyField]$site.RootWeb.Fields.CreateNewField($fieldType, $fieldName);

#Get a taxonomy session
$session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($site)

#Get Term Store
$termstore = $session.TermStores[$termStoreName]

#Get Term Group
$group = $termstore.Groups[$termGroupName]

#Get Term Set
$termSet= $group.TermSets[$termSetName]

#populate newly created field
$field.Sspid = $termSet.TermStore.Id
$field.TermSetId = $termSet.Id
$field.AllowMultipleValues = $bAllowMulitpleValues
$field.Group = $fieldGroup
$field.Required = $bIsRequired
$site.RootWeb.Fields.Add($field)

#Update sp web
$site.RootWeb.Update()


Error deploying BAM Definition with aggregation

October 13, 2010

Following error comes in a way when we try to deploy BAM Definition having an aggregation.

OLE DB error: OLE DB or ODBC error: The SELECT permission was denied on the object ‘bam_OrderProcess_PivotTable1_RTATable’, database ‘BAMPrimaryImport’, schema ‘dbo’.; 42000.

Solution:
What ever the user is accessing BAMPrimaryImport database, assing it as role of db_owner.

Happy BAMing.


MicrosoftEdiXSDTemplates.exe missing in directory %programfiles%\Microsoft BizTalk Server 2006\

August 24, 2010

I came accross a situation where default schema templates were missing after BizTalk Server 2006 R2 installation. After some googling I didn’t find any solution out of it. MicrosoftEdiXSDTemplates.exe is a self extracting archive that have thousand of EDI schema templates ready to use. It can be found in
%programfiles%\Microsoft BizTalk Server 2006\XSD_Schema\EDI directory. But If you don’t find this directory and MicrosoftEdiXSDTemplates.exe file, this means some thing is wrong.

I came to know that order of BizTalk installation does matter to resolve this issue. Just verify whether you installed VS 2005 before BTS installation. In my case I installed BizTalk Server 2006 R2 prior to installing Visual Studio 2005. Fix is very simple. Just Modify BizTalk Installation and check Developer Tools and SDK check box during installation. After Installation you will be able to locate MicrosoftEdiXSDTemplates.exe in %programfiles%\Microsoft BizTalk Server 2006\XSD_Schema\EDI directory.

Happy BizTalking..


Error: Exporting Data from an Access 2007 Database to a SharePoint List

August 3, 2010

Faulting application msaccess.exe, version 12.0.4518.1014, stamp 4542815c, faulting module acewss.dll, version 12.0.4518.1014, stamp 45428ad1, debug? 0, fault address 0x0000b498.

You may get the above error in Windows Event log, while exporting Access 2007 datasheet to Microsoft Office Sharepoint 2007. Solution was very simple and I came to know this after two days of fruitless efforts.

Resolution:
Install Microsoft Office 2007 Service Pack 1 KB936982

Cheers 🙂