Moved Readme

src/Readme.md → Readme.md

@@ -12,21 +12,21 @@ in the current directory.
 The .NET 4.7.2 application is executed with
 
 > IOBound.exe
-
-![Image](https://github.com/Alois-xx/IOBound/images/IOBound_Net742.png)
+ 
+![Image](https://github.com/Alois-xx/IOBound/blob/master/src/images/IOBound_Net472.png)
 
 The .NET Core application as usual with 
 
 > dotnet IOBound.dll
 
-![Image](https://github.com/Alois-xx/IOBound/images/IOBound_NetCore2.1.png)
+![Image](https://github.com/Alois-xx/IOBound/blob/master/src/images/IOBound_NetCore2.1.png)
 
 ## Why? ##
 
 I wanted to check how much faster the `Span<T>` based Apis of .NET Core perform compared 
-to the regular .NET Framework. The C# 7.2 compiler supports Span natively but to unlock the full
+to the regular .NET Framework. The C# 7.2 compiler supports `Span<T>` natively but to unlock the full
 performance you need support of the JIT compiler to generate truly efficient code. 
-This Span supporting JIT compiler will not be ported back to the regular .NET Framework due to
+The `Span<T>` supporting JIT compiler of .NET Core will not be ported back to the regular .NET Framework due to
 application compatibility concerns (at least that is the story up to now Oct. 2018). 
 Now you can check for yourself if you really need to switch over to .NET Core to squeeze out 
 the last bit of performance or not.

src/IOBound.csproj

@@ -15,6 +15,10 @@
     <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
   </PropertyGroup>
 
+  <ItemGroup>
+    <None Include="..\Readme.md" Link="Readme.md" />
+  </ItemGroup>
+
   <ItemGroup>
     <PackageReference Include="MessagePack" Version="1.7.3.4" />
     <PackageReference Include="System.Memory" Version="4.5.1" />