Starting today Sdl Studio PowerShell toolkit became open source on github. You can find more details on this article I wrote:

Or you can directly go to the source code location here: 

I've replied on this thread

Rotten thread, I know... but anyway...

I started playing with the PowerShell Tookit, modified the modules to accept the Studio path (Studio2, Studio3, etc.) as argument, so that I can easily play with different installed Studio versions... Still playing only with the Sample_RoundTrip script, though...

But I'm struggling with the filetypes known to the API-created project, in particular a MemoQ XLIFF.

According to the API documentation, method used by PowerShell Toolkit for creation of new project "creates a new project based on the default project template set up in SDL Trados Studio. "

But... while Studio 2015 recognizes a *.mqxliff file - apparently because it's included by default, no need to Install File Type from OpenExchange - and produces correct analysis stats, Studio 2014 does not and spits out only zeroes... and I don't understand why, since my Studio 2014 default project template DOES include MemoQ XLIFF file type!

Even if I create a copy of my default project template as "Default" profile - just in case the API uses the "Default" profile instead a default profile - it still does not work.

Where is the catch?

I can't use Powershell Toolkit with Studio 2015...

I have modified the default modules to accept Studio version to be used in the "Add-Type" path, so that I can easily test the toolkit with 2011, 2014 or 2015 version (installed on the same machine).... and while it works just fine when run with 2014 (the Sample Roundtrip script runs successfully), when run with 2015, all I get is a bunch of errors.

I'm not a developer (this .NET sh*t is a reall HELL), so I don't have a clue what is that crap telling me...

SDL EXPERTS - it's your product, so be so kind and tell me what's wrong.
According to $PSVersionTable I should be running PS 4.0... Win7 x64 with .NET Framework installed in all versions you can think of...

And - when are you going to update the toolkit to work out-of-the-box with recent Studio version (so that it's actually USEFUL to anyone willing to start with it)?!

Hi Evzen,

I think you only need to modify a couple places.

In TMHelper.psm1 change the function New-FileBasedTM to the following:

function New-FileBasedTM
{
	param([String] $filePath,[String] $description, [String] $sourceLanguageName, [String] $targetLanguageName, 
		[Sdl.LanguagePlatform.TranslationMemory.FuzzyIndexes] $fuzzyIndexes, 
		[Sdl.LanguagePlatform.Core.Tokenization.BuiltinRecognizers] $recognizers,
                [Sdl.LanguagePlatform.Core.Tokenization.TokenizerFlags] $tokenizers,
                [Sdl.LanguagePlatform.TranslationMemory.WordCountFlags] $wordCountFlags)
	
	
	$sourceLanguage = Get-CultureInfo $sourceLanguageName;
	$targetLanguage = Get-CultureInfo $targetLanguageName;

	[Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemory] $tm = 
	New-Object Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemory ($filePath,
	$description, $sourceLanguage, $targetLanguage, $fuzzyIndexes, $recognizers, $tokenizers, $wordCountFlags);	
}

Then in Sample_Roundtrip.ps1, modify line 16 as follows:

New-FileBasedTM $tmFilePath "Created by PowerShell" "en-US" "de-DE" $indexes $recognizers 7 4;

# 7 and 4 are the defaults

Long story short, the constructor found below has two more parameters (8 in total) in Trados Studio 2015 (in previous versions there were only 6 parameters). So the code above needs to be modified like the above to work.

Let me know if that works for you.