hschne

Preliminary Tool Analysis

The Key Project

The Key Project is primarily a symbolic execution engine for Java Programs. It is available as a standalone application and an eclipse plugin.

Pros

• Heavy on formal methods: Pre-Conditions, Invariants, etc. must be understood to properly utilize the tool
• Appart from that, appears to be relatively easy to use

hschne

Instructions

• copy the file commit-msg to .git/hooks/commit-msg
• make sure your delete the sample file .git/hooks/commit-msg.sample
• Make commit msg executable. chmod +x .git/hooks/commit-msg
• Edit commit-msg to better fit your development branch, commit regex and error message
• Profit $$

Shell example

hschne

#!/bin/bash

function usage()
{
    echo "Available parameters:"
    echo "---------------------"
    echo "-h --help"
    echo "-d|--date: Date used in aurora link, e.g. 20160315"
    echo "-c|--count: Amount of slides available, default is 10"
    echo "-o|-output: Name of output file. Default is output.pdf"

hschne

Option Explicit
Public Sub ChangeSpellCheckingLanguage()
    Dim j As Integer, k As Integer, m As Integer, scount As Integer, fcount As Integer, ncount As Integer
    scount = ActivePresentation.Slides.Count
    For j = 1 To scount
        If ActivePresentation.Slides(j).HasNotesPage Then
            ncount = ActivePresentation.Slides(j).NotesPage.Shapes.Count
            For m = 1 To ncount
                If ActivePresentation.Slides(j).NotesPage.Shapes(m).HasTextFrame Then
                    ActivePresentation.Slides(j).NotesPage.Shapes(m).TextFrame.TextRange.LanguageID = msoLanguageIDEnglishUK

hschne

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
<PropertyGroup>
    <MSBuildCommunityTasksPath>$(SolutionDir)\.build</MSBuildCommunityTasksPath>
</PropertyGroup>  
<Import Project="$(MSBuildCommunityTasksPath)\MSBuild.Community.Tasks.Targets" />
  <PropertyGroup>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
    <ProductVersion>8.0.50727</ProductVersion>

hschne

#Using the Visual Studio Remote Debugger

###Introduction Imagine you were to deploy an application developed in Visual Studio to a remote server, or some virtual machine or something. Funny things happen, and on this one single machine, you application displays some rather weird behaviour. How are you gonna debug that? Well, fret not and enter the dark and magic world of remote debugging.

##Tutorial

###Attach to process

Open your favourite version of visual studio. Head over to the menu entry Debug and Attach to Process. You can select a process running on the machine specified in the field Qualifier to attach your debugger to and hit that attach button. Visual Studio will enter the debug mode. You can now hit breakpoints set in visual studio by steering the selected process, just like you would when hitting that debug button.