Finding the contact us link on amazon is like trying to find a needle in a haystack these days.
Finally located it properly, rather than googling “amazon online chat” as I have done in the past…
<#
.Synopsis
Write-XmlPathOutput processes all files in a directory for a given XPath expression and puts the results to .txt files of the same name
.EXAMPLE
Write-XmlPathOutput -DirectoryPath DirectoryPath -XPath //*/project
.INPUTS
DirectoryPath - the path to the directory
XPath - the xpath you wish to use
.OUTPUTS
.txt text files in the same directory
#>
function Write-XmlPathOutput
{
[CmdletBinding(DefaultParameterSetName='Parameter Set 1',
SupportsShouldProcess=$false,
PositionalBinding=$false,
HelpUri = 'http://merrickchaffer.blogspot.com/',
ConfirmImpact='Medium')]
[OutputType([String])]
Param
(
# Param1 help description
[Parameter(Mandatory=$true,
ValueFromPipeline=$true,
ValueFromPipelineByPropertyName=$true,
ValueFromRemainingArguments=$false,
Position=0,
ParameterSetName='Parameter Set 1')]
[ValidateNotNull()]
[Alias("p")]
[String]
$DirectoryPath = (Get-Location).Path,
# xpath help description
[Parameter(Mandatory=$false, ParameterSetName='Parameter Set 1', Position=1,
ValueFromPipeline=$true,
ValueFromPipelineByPropertyName=$true,
ValueFromRemainingArguments=$false )]
[Alias("x")]
[String]
$XPath = "//*/project/@file"
)
Begin
{
}
Process
{
if ($pscmdlet.ShouldProcess("Target", "Operation"))
{
$files = Get-ChildItem (Get-ChildItem $DirectoryPath\*.xml)
if ($files -ne $null -and $files.Length -gt 0) {
ForEach ($file in $files) {
$OutFile = [string]::Concat($file.FullName, ".txt")
Select-Xml -Path $file.FullName -XPath $XPath | Select -ExpandProperty Node | Out-File $OutFile
}
}
}
}
End
{
}
}
Write-XmlPathOutput -DirectoryPath C:\temp -XPath "//*/project/@file"
I was wanting a clean way to convert a C# Boolean property on a view model into a javascript true / false bit of text for passing into our Typescript context settings constructors, and stumbled upon this way …
@Json.Encode(Model.BoolPropertyName)
Works a treat too!
So after wondering where all our tasks had disappeared to, it turns out that someone had changed the default Area path, and ticked it in the _admin/_areas section of the portal.
This has the knock on affect of removing any items from the task board that are not under ticked area paths, hence the stuff that was in our task board disappeared, even though the items were all still there in TFS and accessible via team explorer.
Hi guys
Something that's proving very useful to me now is the fact that you can use advanced search functionality in the quick search box in Visual Studio 2013 to find tickets that you're after.
Example 1,
1. Hit Ctrl+# to enter the team explorer search box
2. Drop down the arrow, and click the assigned to
3. Hit enter
This will then find all the work items assigned to you by default, although you can change the name to someone else to see what they're working on e.g.
Example 2 ,
1. Hit Ctrl+# to enter the team explorer search box
2. Type "Stack Rank":3.75
3. Hit Enter
You'll then get back all items where the stack rank is equal to 3.75
Other search examples as follows:
For all work items that have been changed on a given date
"Changed Date":2015-07-14
For all work items authorized by someone
"Authorized As":"Name Here"
For all bugs changed today
T:"Bug" "Changed Date":2015-01-14
For all items that you uploaded to TFS today
"Authorized As":"@Me" "Changed Date":2015-07-14
That last one is particularly useful, if you've just forgotten the task number you checked in and closed
Use the following powershell script to find the last users to login to a box since a given date, in this case the 21st April 2022 at 12pm un...
