Dotnet on queil.net

Dotnet Test and Jenkins

Thu, 24 Oct 2019 08:25:00 +0100

Problem ¶

How to get dotnet test results collected by Jenkins?

Solution ¶

Make dotnet test create logs:

dotnet test --logger trx

In console output you should now see messages like:

Results File: ...\TestResults\a_long_file_name.trx

Make Jenkins collect the results:

MSTest is the plugin that can consume trx files. Make sure it’s installed.

Add this line to your Jenkinsfile below your tests execution:
```
mstest testResultsFile:"**/*.trx", keepLongStdio: true
```

Notes ¶

You can run dotnet test on the whole solution. It generates a trx file per test project. The MSTest plugin collects all the files and creates an aggregated report accessible in Jenkins. This method is test-framework agnostic. I tested it with NUnit 3.

Seamless Debugging of NuGet Packages

Wed, 14 Aug 2019 18:15:52 +0100

Introduction ¶

Sharing and reusing code between developers and teams has always been a serious challenge. Done badly it may gravely impede development and result with mediocre quality. Sharing source code per se has lots of problems on its own. Therefore, virtually every technology stack has a way of distributing versioned binaries instead. NuGet is the standard for sharing binaries in the .NET world. In open-source communities it’s natural to be able to view source code of a binary package. The next step is an ability to debug third-party binaries if debugging symbols are present. This, however, requires the source code to be downloaded and the debugger to be pointed to it. Source Link is an attempt to make the whole experience seamless. Essentially, it works by enriching packages’ metadata with source control specific information which then can be used on debug time to automatically download and display required source code.

Dotnet Templating Cheat Sheet

Tue, 10 Jul 2018 07:00:01 +0000

A few tips/examples on dotnet new templating. The snippets should be put in the template.json file of your template. All the text in UNDERSCORE_CASE you should replace.

Excluding files ¶

"sources":[{
    "modifiers":[{ 
                "exclude":["**/*.nuspec"]
                }]
        }]

Replacing text in file names ¶

"symbols":{
            "PARAM_NAME":{
                "type":"parameter",
                "description":"PARAMETER_DESCRIPTION",
                "replaces":"TEXT_TO_BE_REPLACED",
                "isRequired":true,
                "FileRename":"TEXT_TO_BE_REPLACED_IN_FILE_NAMES"
            }
        }

Input parameter ¶

"symbols":{
            "PARAM_NAME":{
                "type":"parameter",
                "description":"PARAMETER_DESCRIPTION",
                "replaces":"TEXT_TO_BE_REPLACED",
                "isRequired":true
            }
        }

Transformed parameter (text after the last dot) ¶

"symbols":{
            "PARAM_NAME":{
                "type":"derived",
                "valueSource":"SOURCE_PARAM_NAME",
                "valueTransform":"AfterLastDot",
                "replaces":"TEXT_TO_BE_REPLACED"
            }
},
"Forms":{
            "AfterLastDot":{
                "identifier":"replace",
                "pattern":"^.*\\.(?=[^\\.]+$)",
                "replacement":""
            }
    }

Transformed patrameter (to lower case) ¶

"symbols":{
            "PARAM_NAME":{
                "type":"derived",
                "valueSource":"SOURCE_PARAM_NAME",
                "valueTransform":"ToLower",
                "replaces":"TEXT_TO_BE_REPLACED"
            }
},
"Forms":{
            "ToLower":{
                "identifier":"lowerCase"
            }
    }

Generated port number parameter ¶

"symbols":{
            "PARAM_NAME":{
                "type":"generated",
                "generator":"port",
                "parameters":{
                    "low":LOW_PORT_NUMBER,
                    "high":HIGH_PORT_NUMBER
                },
                "replaces":"TEXT_TO_BE_REPLACED"
            }
        }

Give it a try: Safe

Wed, 16 May 2018 07:46:11 +0100

Intro ¶

I’ve recently learnt about the SAFE Stack. It’s F# all the way from the client to the server side. It’s a fantastic news for back-end people (knowing F#). There is no need of learning intricacies of JavaScript. You can focus on productivity instead. In this post I just want to show you how quickly you can start developing.

First SAFE app ¶

Prerequisites ¶

.Net Core 2, Node.js, Yarn. Make sure you’ve got it all. Then just open shell and let’s type.