SaurabhKV

UAC - Accessing Internet Explorer

2010-03-27T23:09:00Z

Accessing Internet Explorer can be useful for obtaining Web content. The usual approach uses a COM object called InternetExplorer.Application like this:

$ie = New-Object -comObject InternetExplorer.Application
$ie.visible = $true
$ie.navigate('http://www.powershell.com')
$ie
$ie.Document

Unfortunately, this approach fails when you use IE with enhanced security (Vista UAC for example). While you can open IE and navigate to the Web page, you will lose access to the document property once the Web site is loaded because the COM object works only for local files. Once you navigate to a Web page, IE launches again with lower privileges, and PowerShell has no way of accessing the new instance.

To work around this issue, you can use yet another COM object called Shell.Application. It returns all Explorer windows, including all open IE windows. All you need do is pick the IE window you need, by specifying a keyword found in its title bar.

The following example launches a Web page and then waits until a browser window opened with the word "PowerShell" in its title bar. Next, the code returns the IE object and accesses the Web page content.

& "$env:programfiles\Internet Explorer\iexplore.exe" 'http://powershell.com'

$win = New-Object -comObject Shell.Application
$try = 0
$ie2 = $null
do {
Start-Sleep -milliseconds 500
$ie2 = @($win.windows() | ? { $_.locationName -like '*PowerShell*' })[0]
$try ++
if ($try -gt 20) {
Throw "Web Page cannot be opened."
}
} while ($ie2 -eq $null)

$ie2.document
$ie2.Document.body.innerHTML

http://powershell.com/cs/blogs/tips/archive/2009/04/03/accessing-internet-explorer.aspx

http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/

Save Team Foundation Server Password

2010-01-25T17:15:00Z

Have you ever be tired of entering your password every time you access your Team Foundation Server (TFS) project. Don’t worry. There’s a way to bypass the login my storing your passwords in a secure vault.

For Windows 7 users:

Start Menu>Control Panel
User Accounts and Family Safety > Credential Manager
Add A Windows Credential>
Type in your internet/network address as your TFS server address, and username and password of your TFS account.

For Windows Vista users:

Start Menu>Control Panel
User Accounts> Manage your Network Passwords
Click Add
Enter TFS server address
Enter your TFS username and password

For Windows XP users:

Start > Settings > Control Panel
User Accounts > Advanced> Manage Passwords > Add
Enter TFS server address
Enter your TFS username and password.

SharePoint stsadm.exe and Powershell

2009-12-28T14:32:00Z

Trying to run the SharePoint tool stsadm.exe in PowerSehll I get the following error:

The term 'stsadm.exe' is not recognized as a cmdlet, function, operable program, or script file

To get stsadm.exe to work in PowerShell you have to edit the 'profile.ps1' file.
Look in C:\WINDOWS\system32\windowspowershell\v1.0\ and if it doesn't exist just create a new file and add the following code:

Set-Alias -Name stsadm -Value $env:CommonProgramFiles”\Microsoft Shared\Web Server Extensions\12\BIN\STSADM.EXE”

Now you can use stsadm in Powershell without it buggering up.

http://2000mph.blogspot.com/2008/02/sharepoint-stsadmexe-and-powershell.html

SharePoint Page Layout Error: Only Content controls are allowed directly in a content page that contains Content controls

2009-10-13T08:06:00Z

I recently built a SharePoint feature to provision custom master pages and page layouts for a client. Overall the solution worked pretty well until one day, while making changes to one of the page layouts, I saw the following error: Only Content controls are allowed directly in a content page that contains Content controls.

Since other blog entries, referenced at the end of this article, can explain the background I'll get right to the cause and the solution. The cause is improper case for the <asp:Content> control tags in my page layout. A few contorls used a lower case "c" instead of an uppercase "C" in the word content. The page layout that had trouble had tags that looked like: <asp:content> instead of <asp:Content>. The specific offending tag is the one associated with the page title (<asp:Content ContentPlaceholderID="PlaceHolderPageTitle" runat="server">). The solution was as simple as correcting the case of the tag name and all worked well.

Aggregating content with the Content Query Web Part (CQWP)

2009-10-12T20:06:00Z

In most web content management projects based on SharePoint the Content Query Web Part is used for aggregating content. Out of the box it have a few styles, but seems a little limited. With a little tweaking you can display the information you want in the way you want it.

There are mainly three parts involved here:

The web part itself
The ItemStyle.xsl
The ContentQueryMain.xsl

The xsl files is defining how the content is displayed for the end users. The ItemStyle define the style for each item (like a row in a table), while the ContentQueryMain.xsl defines the surrounding (like the table around the rows). By exporting the web part you will find that there are plenty of properties not available in the user interface. The ones I change the most are:

CommonViewFields add columns that you can use in the web part.

<property name="CommonViewFields" type="string">Priority,Choice;PublishingStartDate,DateTime;Ingressbilde,Image;Ingress,HTML</property>

The Image field can be a little tricky

DataColumnRenames changes the name of the input column name to another name. Makes it easier to build the xsl when there are several fields that should be treated as they were the same. Here I rename Ingress to Description

<property name="DataColumnRenames" type="string">Ingress,Description</property>

ItemXslLink and MainXslLink can be pointed to your own XSL-stylesheet for how you want to display the items and what styles you want to make available for the users.

<property name="ItemXslLink" type="string" >/Style Library/XSL Style Sheets/MyItemStyle.xsl</property>

<property name="MainXslLink" type="string">/Style Library/XSL Style Sheets/MyContentQueryMain.xsl</property>

Update: Remember that both ItemXslLink and MainXslLink is server relative. So if your site collection is in the managed path /Sites/ then the xsl-links must reflect that. So for a Site Collection http://example.com/sites/department you will have this property

<property name="ItemXslLink" type="string" >/sites/department/Style Library/XSL Style Sheets/MyItemStyle.xsl</property>

Update end

To set the default style you set the ItemStyle property:

<property name="ItemStyle" type="string">MyNewsArchive</property>

Inside the ItemStyle.xsl you can add several styles. I like to add one that displays all data (columns) that is available to use. This view is developer friendly, but very user unfriendly.

<xsl:template name="ShowXML" match="Row[@Style='ShowXML']" mode="itemstyle">
    <xsl:for-each select="@*">
        <br />
        Name: <xsl:value-of select="name()" />
        <br />
        Value:<xsl:value-of select="." />
    </xsl:for-each>
</xsl:template>

Feature stapling doesn’t work with STP

2009-07-30T17:57:49Z

Feature stapling doesn’t work with STPs file(Site Template File)

Feature Stapling

2009-07-10T06:17:33Z

Causes the attachment of a Feature to all new instances of sites that use a given site definition, without modifying the site definition or creating code routines to activate the Feature on each site. Also known as a feature site template association,

Real World Example

A developer creates a Feature and to add it to every new Web site that is based on a specific site definition. The developer creates a feature-stapling Feature that includes mappings between the Feature and site definition

Technical Details

Feature stapling is implemented through a Feature that is specifically designed to staple other Features to one or more site definitions. Feature stapling allows a Feature to be stapled to any new sites created from any site definition or from specific site definitions based on the template name identified in the appropriate WEBTEMP.xml file.

Following is an example of feature stapling that associates the Feature with only the STS site definition templates.

Xml

Following is an example of feature stapling that associates the Feature with all site definitions.

Xml

Support Details

Feature stapling starts only when the feature stapling entry is added. To add the Features to existing sites, or to sites later added through a restoration process, you must associate the Features with the sites by using some other method.

IIS Service Unavailable Error on a 64 bit operating system

2009-06-24T17:08:36Z

PROBLEM:
If you find this error in the event log when starting an iis service on a 64 bit operating system (personally this happened to us with SharePoint). (This is also followed by a Service Unavailable error when trying to use the application):

Event Log: Could not load all ISAPI filters for site/service. Therefore startup aborted

SOLUTION:
It can be fixed by rebuilding asp.net. You can only run asp.net 1.1 in 32 bit mode and you can run asp.net 2.0 in either 32 bit mode or 64 bit mode.

ASP.NET 1.1
1. Click start, run and type this in:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
2. Click start, run and type this in:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
Note:Make sure ASP.NET 1.1 is Allowed in the Web service extension list in Internet Information Services Manager.

AND

ASP.NET 2.0 (32-bit)
1. Click start, run and type this in:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
2. Click start, run and type this in:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
Note: Make sure ASP.NET 2.0 (32 bit) is Allowed in the Web service extension list in Internet Information Services Manager.

ASP.NET 2.0 (64-bit)
1. Click start, run and type this in:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
2. Click start, run and type this in:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Note: Make sure ASP.NET 2.0 (64 bit) is Allowed in the Web service extension list in Internet Information Services Manager.

Note: Change 2.0.50727 to whatever build of the framework you have.

SharePoint JavaScript – Page Load Add function: _spBodyOnLoadFunctionNames

2009-06-22T12:27:16Z

In most cases SharePoint pages are based on a master page that contains the “body” element. These content pages can’t directly add a function to the body’s onload event. In order to work around this limitation, SharePoint provides the “_spBodyOnLoadFunctionNames” array. When the body is loaded, the onload event handler executes each function whose name is contained in this array. We added “FunctionName” to the array so that it would run when the body’s onload event fires.

Adding SharePoint Search to IE7

2009-06-18T23:00:33Z

The following registry file can be used to add MOSS search to the list of IE7 search providers ... so you can access it from the top right search box.
(Rename xxxx with the name of your MOSS machine)

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\Intranet]
"DisplayName"="Search Intranet"
"URL"=http://xxxx/searchcenter/pages/search_results.aspx?k={searchTerms}&s=Intranet
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\People]
"DisplayName"="Search people"
"URL"="http://xxxx/searchcenter/pages/people_results.aspx?k={searchTerms}"

Save the contents to a text file and rename to a .REG suffix. Then double click the file to invoke it

OR ----

Click Here