SharePoint / .Net Dev Blog

In the last several years, I used PowerShell to scripting the enviorement installers for my Software oder mamage some servers. This was only possible on my windows enviorement.

Today Microsoft do the next step into is journey and bring the PowerShell to Linux. The reason is, that Microsoft will bring the MS and Linux world more together. The last step for this was, that they bring the bash to Windows.

Where can I get it?

You can get PowerShell from here. Thisnis a good stringpoint. There are some alpha builds available for CentOs and Ubuntu 16.04 and 14.04

So what is possible?

It seems that you can do anything from anywhere. For exampe , when you a linux guy and manage windows images, so you can use a mix of shell and powershell. This works in the other way too. In my, and I think in others too, the PowerShell will not be a repacement in a linux world. It is more a tool in you toolkit.

So that’s all?

No, because today Jeffrey Snover () make his statement from 2014 become true and brings PowerShell opensource. They hosting it in a Git repositority and can be found here.

You can read more about the anouncement here.

Today I will post my experience in VS Code creating and debugging ASP.Net Core apps.

First of all, VS Code has an huge extension Libary and you must use it I think. So I use some plugins that take some work of me.

The first Plugin is the Yeoman Generator engine. This generates a sekelton for any projects what you will write. You can install this with following NPM Command:

npm install -g yo

After installing it, you need to install the generators too. You will find them on http://ift.tt/1ryZvM8. But for the example we use only the aspnetcore generator, you install it with:

npm install -g generator-aspnet

After installing it, you can execute the follwoing command to start the aspnet core generator.

yo aspnet

After this you will see a selection of templates like this.

We select „Web Application Basic [without Membership and Authorization]“. After confirming it with Enter, it guide us throught a wizard and ask us several things. I listed the answers in the following table:

UI-Framework: Bootstrapt Name: Testproject

  When we answered all Questions from the wizard, it start to generate the sekelton for the ASP.Net Core project. This include that it get the latests resources from bower and npm. So it will present a fresh set of libaries that will be used in the project.

After the wizard is done you must execute some extra commands

cd "Testproject" dotnet restore

The dotnet restore command has the effect, that the missing components from nuget will be restored.

Now you it’s time to turn on Visual Studio Code, and load the directory the contains our „Testproject“. That look in VS Code like in this picture:

I accept the info that appears in the top infobar. The adds a new directory called .vscode and adds two files in it. These files are launch.json and tasks.json.

The tasks.json contains the different tasks that we can call in the visual studio code command. At the moment there is only the Build Task. the Content for this file looks like the following

{ "version": "0.1.0", "command": "dotnet", "isShellCommand": true, "args": [], "tasks": [ { "taskName": "build", "args": [ "${workspaceRoot}\\project.json" ], "isBuildCommand": true, "problemMatcher": "$msCompile" } ] }

This json describes, that there will be executed the „dotnet“ as a shell command. The tasks describes will describe the arguments for the command. In the example above there exists a task called „build“ and takes a argument „${workspaceRoot}\\project.json“. This tells that the project.json in the current workingdirectory will be used for compiling.

The launch.json look like this:

{ "version": "0.2.0", "configurations": [ { "name": ".NET Core Launch (web)", "type": "coreclr", "request": "launch", "preLaunchTask": "build", "program": "${workspaceRoot}\\bin\\Debug\\netcoreapp1.0\\Testproject.dll", "args": [], "cwd": "${workspaceRoot}", "stopAtEntry": false, "launchBrowser": { "enabled": true, "args": "${auto-detect-url}", "windows": { "command": "cmd.exe", "args": "/C start ${auto-detect-url}" }, "osx": { "command": "open" }, "linux": { "command": "xdg-open" } }, "env": { "ASPNETCORE_ENVIRONMENT": "Development" }, "sourceFileMap": { "/Views": "${workspaceRoot}/Views" } }, { "name": ".NET Core Attach", "type": "coreclr", "request": "attach", "processId": "${command.pickProcess}" } ] }

The describes the build and debug process itself. This is very self-explanatory.

Now it’s time to compile and start the webapplication. We simply hit F5 and the VS Code compiles the application and start the Browser to dipsplay the Page.

The result looks like my result:

So now we have a cool running asp.net Project. We want to run it in a docker container. But first let’s have a look into the solution explorer. We will se a file that will be called „Dockerfile“. Okay Docker = Docker…file.. let’s look into it, and we will se this content:

FROM microsoft/dotnet:latest COPY . /app WORKDIR /app RUN ["dotnet", "restore"] RUN ["dotnet", "build"] EXPOSE 5000/tcp ENTRYPOINT ["dotnet", "run", "--server.urls", "http://0.0.0.0:5000"]

Hey this looks like a Build definition for docker. You can install docker from the docker page, it is absolutely free and a instruction with a few first stept you’ll find here.

Now when you have installe docher, the only thing what you must do ist open up a PowerShell in Administration Mode. An run the compile command for docker:

docker built -t mywebproject .

Now the magic begins, this get the latest dotnet image, copy the current sources into the app directory in the docker image. After this it set the working directory ti the app directory. After that happened, it run the dotnet command tow times, the first time with the „restore“ parameter, to restore the nuget packages and references, after that it do a „build“ to compile the app IN THE CONTAINER!!!. After this it will opens up a tcp Port 5000 and execute the command to start the dotnet webserver.

The takes some time, but when it is ready you will see that it has worked. If you then apply some changes this will doesn’t take so much time, it is only the initalize of the image.

The complete output looks like the following output:

d:\TFS\GIT\Testproject>docker build -t mywebproject . Sending build context to Docker daemon 4.928 MB Step 1 : FROM microsoft/dotnet:latest latest: Pulling from microsoft/dotnet 357ea8c3d80b: Pull complete 52befadefd24: Pull complete 3c0732d5313c: Pull complete 182cb80041a7: Pull complete a49b25f72e2d: Pull complete 46be245fa43f: Pull complete Digest: sha256:833227fde31ebc668c8c4ea1db89a29231b7a396a977723511e61776166a196b Status: Downloaded newer image for microsoft/dotnet:latest ---> b5be6fbf2a31 Step 2 : COPY . /app ---> 7eaf7ee2c689 Removing intermediate container 2d9d3e356712 Step 3 : WORKDIR /app ---> Running in 203d2b1d8660 ---> 33cffdbfd937 Removing intermediate container 203d2b1d8660 Step 4 : RUN dotnet restore ---> Running in dcaaa1a9bd4e log : Restoring packages for /app/project.json... log : Installing NuGet.Configuration 3.5.0-beta2-1484. log : Installing NuGet.Protocol.Core.Types 3.5.0-beta2-1484. log : Installing NuGet.Protocol.Core.v3 3.5.0-beta2-1484. log : Installing NuGet.Repositories 3.5.0-beta2-1484. log : Installing NuGet.LibraryModel 3.5.0-beta2-1484. log : Installing NuGet.Packaging.Core.Types 3.5.0-beta2-1484. log : Installing Microsoft.AspNetCore.Cryptography.Internal 1.0.0. log : Installing Microsoft.AspNetCore.DataProtection.Abstractions 1.0.0. log : Installing Microsoft.AspNetCore.Routing.Abstractions 1.0.0. log : Installing Microsoft.DotNet.InternalAbstractions 1.0.0. log : Installing NuGet.DependencyResolver.Core 3.5.0-beta2-1484. log : Installing NuGet.Packaging.Core 3.5.0-beta2-1484. log : Installing NuGet.Common 3.5.0-beta2-1484. log : Installing NuGet.RuntimeModel 3.5.0-beta2-1484. log : Installing Microsoft.AspNetCore.DataProtection 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Abstractions 1.0.0. log : Installing Microsoft.AspNetCore.Routing 1.0.0. log : Installing Microsoft.Extensions.DependencyModel 1.0.0. log : Installing Microsoft.AspNetCore.Authorization 1.0.0. log : Installing Microsoft.Extensions.Globalization.CultureInfoCache 1.0.0. log : Installing Microsoft.Extensions.Localization.Abstractions 1.0.0. log : Installing System.ComponentModel.Primitives 4.1.0. log : Installing System.Collections.Specialized 4.0.1. log : Installing System.Collections.NonGeneric 4.0.1. log : Installing System.Diagnostics.Contracts 4.0.1. log : Installing System.Net.WebSockets 4.0.0. log : Installing NuGet.ProjectModel 3.5.0-beta2-1484. log : Installing NuGet.Packaging 3.5.0-beta2-1484. log : Installing NuGet.Frameworks 3.5.0-beta2-1484. log : Installing NuGet.Versioning 3.5.0-beta2-1484. log : Installing Microsoft.DotNet.ProjectModel 1.0.0-rc3-003121. log : Installing Microsoft.AspNetCore.Razor 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Razor.Host 1.0.0. log : Installing Microsoft.Extensions.FileProviders.Composite 1.0.0. log : Installing Microsoft.AspNetCore.Antiforgery 1.0.0. log : Installing Microsoft.AspNetCore.Html.Abstractions 1.0.0. log : Installing Microsoft.AspNetCore.JsonPatch 1.0.0. log : Installing Microsoft.AspNetCore.Cors 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Core 1.0.0. log : Installing Microsoft.AspNetCore.Localization 1.0.0. log : Installing Microsoft.Extensions.Localization 1.0.0. log : Installing Microsoft.Extensions.Caching.Abstractions 1.0.0. log : Installing System.ComponentModel.TypeConverter 4.1.0. log : Installing Microsoft.Extensions.ObjectPool 1.0.0. log : Installing Microsoft.AspNetCore.Hosting.Server.Abstractions 1.0.0. log : Installing Microsoft.Net.Http.Headers 1.0.0. log : Installing Microsoft.AspNetCore.Http.Features 1.0.0. log : Installing System.Text.Encodings.Web 4.0.0. log : Installing Microsoft.Extensions.FileSystemGlobbing 1.0.0. log : Installing Microsoft.Extensions.Primitives 1.0.0. log : Installing Microsoft.DotNet.Cli.Utils 1.0.0-preview2-003121. log : Installing Microsoft.DotNet.ProjectModel.Loader 1.0.0-preview2-003121. log : Installing Microsoft.AspNetCore.Razor.Runtime 1.0.0. log : Installing Microsoft.Extensions.CommandLineUtils 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Razor 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.DataAnnotations 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.ViewFeatures 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Formatters.Json 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Cors 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.ApiExplorer 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.Localization 1.0.0. log : Installing Microsoft.AspNetCore.Mvc.TagHelpers 1.0.0. log : Installing Microsoft.Extensions.DependencyInjection 1.0.0. log : Installing Microsoft.Extensions.Caching.Memory 1.0.0. log : Installing Microsoft.Extensions.Configuration.Binder 1.0.0. log : Installing Microsoft.AspNetCore.Hosting 1.0.0. log : Installing Microsoft.AspNetCore.Http 1.0.0. log : Installing Microsoft.AspNetCore.HttpOverrides 1.0.0. log : Installing Microsoft.AspNetCore.WebUtilities 1.0.0. log : Installing Microsoft.AspNetCore.Diagnostics.Abstractions 1.0.0. log : Installing Microsoft.Extensions.Options 1.0.0. log : Installing Microsoft.AspNetCore.Hosting.Abstractions 1.0.0. log : Installing Microsoft.AspNetCore.Http.Extensions 1.0.0. log : Installing Microsoft.Extensions.WebEncoders 1.0.0. log : Installing Microsoft.Extensions.FileProviders.Abstractions 1.0.0. log : Installing Microsoft.AspNetCore.Http.Abstractions 1.0.0. log : Installing Microsoft.Extensions.FileProviders.Physical 1.0.0. log : Installing Microsoft.Extensions.PlatformAbstractions 1.0.0. log : Installing Microsoft.Extensions.Configuration.FileExtensions 1.0.0. log : Installing Newtonsoft.Json 9.0.1. log : Installing System.Runtime.Serialization.Primitives 4.1.1. log : Installing Microsoft.Extensions.DependencyInjection.Abstractions 1.0.0. log : Installing Microsoft.Extensions.Configuration.Abstractions 1.0.0. log : Installing Microsoft.Extensions.Logging.Abstractions 1.0.0. log : Installing Microsoft.Extensions.Configuration 1.0.0. log : Installing Microsoft.AspNetCore.Razor.Tools 1.0.0-preview2-final. log : Installing Microsoft.AspNetCore.Mvc 1.0.0. log : Installing Microsoft.Extensions.Options.ConfigurationExtensions 1.0.0. log : Installing Microsoft.AspNetCore.Server.Kestrel 1.0.0. log : Installing Microsoft.AspNetCore.Server.IISIntegration 1.0.0. log : Installing Microsoft.AspNetCore.Diagnostics 1.0.0. log : Installing Microsoft.AspNetCore.StaticFiles 1.0.0. log : Installing Microsoft.VisualStudio.Web.BrowserLink.Loader 14.0.0. log : Installing Microsoft.Extensions.Configuration.Json 1.0.0. log : Installing Microsoft.Extensions.Logging 1.0.0. log : Installing Microsoft.Extensions.Logging.Console 1.0.0. log : Installing Microsoft.Extensions.Logging.Debug 1.0.0. log : Installing Microsoft.Extensions.Configuration.EnvironmentVariables 1.0.0. log : Installing Microsoft.Extensions.Configuration.CommandLine 1.0.0. log : Restoring packages for tool 'BundlerMinifier.Core' in /app/project.json.. . log : Installing NUglify 1.5.0. log : Installing BundlerMinifier.Core 2.0.238. log : Restoring packages for tool 'Microsoft.AspNetCore.Razor.Tools' in /app/pr oject.json... log : Restoring packages for tool 'Microsoft.AspNetCore.Server.IISIntegration.T ools' in /app/project.json... log : Installing Microsoft.AspNetCore.Server.IISIntegration.Tools 1.0.0-preview 2-final. log : Writing lock file to disk. Path: /app/project.lock.json log : /app/project.json log : Restore completed in 20884ms. ---> 59aa0cf668a1 Removing intermediate container dcaaa1a9bd4e Step 5 : RUN dotnet build ---> Running in 0f3d467f8f1f Project app (.NETCoreApp,Version=v1.0) will be compiled because project is not s afe for incremental compilation. Use --build-profile flag for more information. Compiling app for .NETCoreApp,Version=v1.0 Bundling with configuration from /app/bundleconfig.json Processing wwwroot/css/site.min.css Bundled Minified Processing wwwroot/js/site.min.js Compilation succeeded. 0 Warning(s) 0 Error(s) Time elapsed 00:00:02.5616789 (The compilation time can be improved. Run "dotnet build --build-profile" for m ore information) ---> 5ec9a7756b4f Removing intermediate container 0f3d467f8f1f Step 6 : EXPOSE 5000/tcp ---> Running in 541e34a2a6ed ---> 2fc362d58382 Removing intermediate container 541e34a2a6ed Step 7 : ENTRYPOINT dotnet run --server.urls http://0.0.0.0:5000 ---> Running in 667c4a41b0e0 ---> 1828c7fe9c12 Removing intermediate container 667c4a41b0e0 Successfully built 1828c7fe9c12 SECURITY WARNING: You are building a Docker image from Windows against a non-Win dows Docker host. All files and directories added to build context will have '-r wxr-xr-x' permissions. It is recommended to double check and reset permissions f or sensitive files and directories.

What did we do now? So we created an image that contains our webapplication we developed before. Wenn we do the command „docker images“ to get the available images you will se the mywebproject image. We can now take this image and check it into the docker repositority in, so that this image can now deployed to a testsystem or a production. This was easy for now.

But as next step, we will test our image if it works.

We must run the image

docker run -d -p 5000:5000 mywebproject

This command start up the image and opens the port 5000. Now we can make an call to http://localhost:5000 and BAM we get our webapplication running in this container. But what is, if we have an problem and wan’t to debug in this image. This can be do if we open the remote debugger port onto it.

docker run -d -p 3000:3000 -p 5858:5858 mywebapplication

Now you can attach your debugger and do a remote debugging if you want.

The big advantage of docker (or this techique) is that the sentence „on my dev machine it works“ doesn’t occur. Because you set the live enviroment and deploy it too. So when an error occur, you will get this on your „dev machine“.

  Twittern

Now my new Blog was initalized. You can reach it now under http://ift.tt/2b4cke4 In the next several week I will get a custom top level domain.

Twittern

I assumed that SharePoint is inteligent enouth to differ betweent their Keywords. 

Usually in a Search Center you can define your own query to get you sepcific results. I used a Query to filter especially for a contenttype and a given value from the Request parameter URL (”k”) like this:

{searchboyquery} {RequestParameter.k} contenttype:test

Problem

That looked great but for some reason after using sometimes the frefiner I got an empty result.

So there are no error in the ULS, no error in the Frontend, no error at all. After a small research I figured out that the extra paramter [RequestParameter.K} causes the problem.

Solution

So I removed it, after this it works very well, and the K Parameter in the request will be used in the [searchboxquery} placeholder. 

So there is a problem when I use the k Parameter directly, or I must remove the {Searchboxquery}, but I wanted the flexibility to add a searchbox later by hand.

In the past project I must modified the search results. 

In the meanwhile I figured out that the crawler found and results some old data in the search. But why? 

The reason is that I destroyed the webapplication with delete-spwebapplication and so the cralwer doesn’t recognize that there was the data deleted. But it find new data. 

The Solution

Here’s a quick snipplet to get the userinformation from the ldap server with 

$strFilter = "(&(objectCategory=User)(Department=Finance))" $objDomain = New-Object System.DirectoryServices.DirectoryEntry $objSearcher = New-Object System.DirectoryServices.DirectorySearcher $objSearcher.SearchRoot = $objDomain $objSearcher.PageSize = 1000 $objSearcher.Filter = $strFilter $objSearcher.SearchScope = "Subtree" $colProplist = "name" foreach ($i in $colPropList){$objSearcher.PropertiesToLoad.Add($i)} $colResults = $objSearcher.FindAll() foreach ($objResult in $colResults)    {$objItem = $objResult.Properties; $objItem.name}

The problem

In my central Admin, I got the following error message:

After trying serveral time with the psconfig command to upgradethe wohle databases, it already show me the error again. 

Then I identified the problem. Because in the database exists more as one CrawlStoreDb (ans propertyDB), but the search service uses only one of them. But that was not the databse shown in the Error message. So I assumed that the Database is obsolete.

I prooved it againg and checked the database size:

The size reflects to me that this will be not used by the sharepoint, because the other database is much bigger. I did a second test with hte health analzier after a renaming of the database on database level. After a while the same error show up but in the Database status I get the following error

The Search works like a charm and throwing no errors. So I can delete the obsolete databases. 

First of all I mus get the Database ID from the contentdatabase registration:

Get-SPDatabase | where {$_.Type -notcontains "Content Database" -and  $_.Type -notcontains "Configuration Database"} | sort Type | select Name ,Id

After that I can use the Id to delete the Contentdatabase with the Guid from the SPDatabase

$db= Get-SPDatabase -Identity {Guid} $db.Delete()

The word autmation service makes it possible to convert word documents into pdf document out of the box. 

Sometimes it is helpful to test the autmation service. So here comes the power of the PowerShell:

$AppName="Word Automation Services" $timerJobName="Word Automation Services" $SiteUrl="http://portal.contoso.com" $WordDoc="/Freigegebene%20Dokumente/Fdsfsfd.docx" $PDF="/Freigegebene%20Dokumente/test.pdf"

asnp *sh* Write-Host -BackgroundColor Green -ForegroundColor Yellow " --- Test Word Automation Service --- " write-host "" $WASinstance=Get-SPServiceInstance | ?{$_.typename -eq "Word Automation Services"} IF ($WASinstance.Status -ne "Online") {    Write-Host -ForegroundColor Red -BackgroundColor White " - Service Instance not started !! - Status: "$WASinstance.Status    Write-Host "  - Run to start: (Get-SPServiceInstance | ?{$_.typename -eq "Word Automation Services"}).Provision()"    break }

Write-Host -BackgroundColor Green -ForegroundColor Yellow " --- Test Word Automation Service Application --- " write-host "" Write-Host "Check service application: "$AppName

$was=Get-SPServiceApplication -Name $AppName -ErrorAction SilentlyContinue if (!$was) {    Write-Host -ForegroundColor Red -BackgroundColor White " - Service application not found !!"    break } Write-Host -ForegroundColor Green "  - Service application found" Write-Host -ForegroundColor Green "  - Status : "$was.Status

Write-Host "Convert Word document to PDF : "$SiteUrl $WordDoc [void][System.Reflection.Assembly]::LoadWithPartialName( "Microsoft.Office.Word.Server" ) $jobSettings = New-Object Microsoft.Office.Word.Server.Conversions.ConversionJobSettings $jobSettings.OutputFormat = "PDF" $job = New-Object Microsoft.Office.Word.Server.Conversions.ConversionJob( $AppName, $jobSettings ) $job.UserToken = (Get-SPWeb $SiteUrl).CurrentUser.UserToken $job.AddFile($SiteUrl+$WordDoc,$SiteUrl+$PDF) $job.Name="TEST JOB !!!!!!!" $job.Start( )

Write-Host "" Write-Host "Starting Timer job : " $timerJobNameget-sps Start-SPTimerJob $timerJobName

Write-Host "Job status:" new-object Microsoft.Office.Word.Server.Conversions.ConversionJobStatus($AppName, $job.JobId,$null);

Write-Host "" Write-Host -ForegroundColor Green "--- Test done ---"

In the head you have the variables to declare the Word automation Service Name (not the proxy), the source location and the destination for the pdf file

With the following script you can list all jobs from the service to get the state of the job.

Function ListConversionsStatus {    $AppName="Word Automation Services"    [void][System.Reflection.Assembly]::LoadWithPartialName( "Microsoft.Office.Word.Server" )    $WASAllJobs=[Microsoft.Office.Word.Server.Conversions.ConversionJobStatus]::GetAllJobs($AppName, $null)    foreach  ($WASJob in $WASAllJobs)    {        $WASJob        new-object Microsoft.Office.Word.Server.Conversions.ConversionJobStatus($AppName, $WASJob.JobId,$null);    } }

a customer wanted a predefined orderig from the deployed views. 

So there was a smal problem. SharePoint doens’t define a attribute like “orderID” for views in the Schema.xml definition.

The solution

Here’s a quick PowerShell snipplet to get users from the Ldap Server. This example use a query to fetch all users from the department Finance. 

It also results only the property “name”.

Microsoft announced the next SharePoint version for 2016. It’s called also SharePoint 2016. By the Blogpost on Offie Blogs, they mentioned that the take much work to improve the user experience. So it will be generate more support for touch devies. 

The also breakup the rumor, that microsoft discontinued the On-Premise servers. Because they will supporting more hybrid scenarios, so that the customers can store super duper top secret data onto ther on-premise server and other (not so secure) data into the cloud. 

We know now what managed properties are. How we can configure and search for them. In this post, I will show you for what we did with them too. 

Custom Search Display Template

In every search we will get the Title and a short description from the rest oft the search result. This is the default display tempalte for the search results. There exists many different search display templates. For example, you will get anothert display template shown for word documents with a small preview as when you get a item result from your custom list. 

For this scenario you can create your own display template. This is pretty easy. But you must have configured the managed property for this. So when you want to display a custom template, then you must first configured your custom columns and assigned it to a managed property. 

Only managed properties can be displayed in the search display template.

Where are the Templates?

Before I will answer this question, you must know that you can create a display template only for the current "level" and below, so if you create a display template for a particular site, then you must ist copy to the other site too. But if you create the template in the site collection, it will also available in the subsites in this site collection.

The place where you will find it is unter the site settings->Masterpages

In this you will se a folder structure. Click through the following folder structure: Display Templates -> Search.

Here you will se a lot of JavaScript and HTML files, if not, then you must enable the Publishing Infrastructure to get them. 

So how can I create my own Template?

First of all search the item_default.html in the Folder. Download them and open it up in your editor *cough* notepad++ *cough*. You will se many HTML code like the following: 

 this looks verry confused to someone, but trust me, it's only HTML with some additional special "comments" in it. 

First of all there is a Node called Title. This title will later showed up in the selection lists for using the template.

The Nodes with the namespace "mso" are configuration parameters that you will se in that properties dialog too. 

Let's concentrate on the Node called mso:ManagedPropertyMapping. In this Node you will define the displayed Properties that you will display in the Template. There will be the following format:

'InternalName':'ManagedPropertyName'

With the internal name you can now access the data to display it into your template.

Now you can concentrate on the html fragment under the mso parameters. Here you will find in the body tag a div with an id.

It is very important that you put all your display data into the div otherwise it will not be rendered.

You can access the data in HTML with _#= =#_  surounding the dataelement.

For example you can use

_#= ctx.InternalName =#_

to access the mapped managed property called internalname. So now you can design the display with your own design.

Can I embeed JavaScript?

Yes of course. IN the screen above you see the JavaScript. So there is one difference between referencing only the managed property and inserting JavaScript.

You muss enclosing the complete JavaScript with an opening “<!--#_” and a closing “_#-->”. In this now you can insert any JavaScript.

But here you must be carefull to insert the JavaScript in the given div tag. Otherwise ths script will be ignored.

You have also the posibility to execute some javaScript after the rendering. For this you must create an array in the context called OnPostRender.

ctx.OnPostRender = [];

In this you push your methods that must be called after the rendering is complete.

ctx.OnPostRender.push(function(){ console.log(”my function”);});

When you use trace logging in you application. You can put the output of this into a textfile. Simply insert the following snipplet into your .config file

<system.diagnostics>    <trace autoflush="false" indentsize="4">      <listeners>        <add name="myListener"          type="System.Diagnostics.TextWriterTraceListener"          initializeData="Mylog.log" />        <remove name="Default" />      </listeners>    </trace>  </system.diagnostics>

"This is part 2 of the smal series about managed Metadata. In the last post, I described the differences about crawled and managed properties. In this post i want to show you where we can use the managed properties.

Managed properties are, that we have learned since the last post, a single or a set of crwaled properties, mapped to one property in the property store.

So what can we do with this?

Searching by managed properties

Yes we can search for it, but how? The answer is simple. But first let assume you got a crawled property called "DocumentState". This crwaled property contains values from a choice list (Approved, Active, Closed). These crawled property is assigned to the managed property calles "DocumentStateM". 

Now we can use in the searchbox the following syntax:

"DocumentStateM: Active"

Ths Syntax is very easy "{ManagedProperty}:{Searchvalue}". The example above will search (and display) all entries that contains the Property DocumentStateM with value "Active" assigned. 

Do you want all documents that have the state active and closed, the syntax will be the following:

"DocumentStateM: Active OR DocumentStateM: Closed"

This is the basic syntax of the Search Query language in SharePoint. 

Result Sources

This example is very handy, but it will be more effective if you can create a preselection for the user. For example, you will only dsiplay the documents the contains the Value "Approved" to the document. For this you can create a result source. 

This will autmate some preselection for the user, before he assign his search query.

to create a new result source, you must navigate to https://{yourSharepoint}/_layouts/15/manageresultsources.aspx

This will show you a list with existing preselected resultsources. 

When you add a new result source, you will be redirected to a details page where you will enter a unique Name, and a protocoll and with a wizard, the predefined query. In our example you must insert DocumentStatusM:Approved {searchTerms}. 

After click on test query you will se on the right side the search results.

The keyword {searchTerms} is a placeholder for the manual user input from a search list. If you don't want that the user input will be considered then you can remove this.

In another post I will describe the other options of this wizard. For now you can ignore the other setting and close the wizard by clicking on "OK".

After saving the new result source, this will be avaiable in the searchresults webparts. 

Please pay attention where you create the result source. When you create a result source on the site level and want to use it on another site, it is not possible. For this you must defined it in the search configuration on the central administration. 

Lesson learned