(for NikGitStats2, prog_tools.pdf, prog3_layers_requirements.pdf, prog4_game_requirements.pdf)

• [MAY/20] Added Prog4Hf4
• [MAY/15] Dont forget that the WPF apps have the same rules (even in the 3rd homework): USE THE IoC, LUKE!
  HU API video, around 1:01:45: "Ez egy eléggé ocsmány húzás, ez rejtett függőséget okoz [...] a korábbi példákban bemutatott IoC container használatát dependency injectionnel kombinálva tessék betartani"
  EN API video, around 58:40: "I should receive the logic with Dependency Injection"
  In the C# code: "TODO: IoC + Dependency Injection!"
• [APR/30] Added Prog4Hf2 and Prog4Hf3 checkers
• [APR/11] To use WPF classes (Rect, Geometry, Drawing, Pen, Brush...) in a Class Library project, you have to manually edit the csproj file of the Class Library. In the csproj file, into the <ItemGroup> you must add:
  
  <FrameworkReference Include="Microsoft.WindowsDesktop.App" />
  
  In the same csproj file, in the <PropertyGroup>, you must set the <TargetFramework> to be
  
  <TargetFramework>net5.0-windows</TargetFramework>
• [APR/11] If you experience performance issues with your Prog4 game, you can try disabling XAML debugging/hot reload in your Visual Studio via Tools/Options: search Debugging/Hot Reload and Debugging/General/Diagnostic tools, and DISABLE both of them!
• [APR/11] Do not forget, in your dotnet core nUnit unit test class libraries, you also need a nuget reference to Microsoft.Net.Test.Sdk
• [MAR/19] Seems like the network problems are still there (and they only got worse...) So I added a "retry" handler to the GitClone checker, now it retries cloning a repo altogether 3 times...
• Old changelog entries are hidden... [SHOW ALL]
• [MAR/19] Sorry, the server died for two days... Lets hope it will stay alive for a while :(((
• [MAR/17] Disabling Stylecop + NetAnalyzers via "dotnet_analyzer_diagnostic.severity" is not allowed (you must not use dotnet_analyzer_diagnostic.severity anywhere!)
• [MAR/11] The GitStats creator VM has random network problems... This means that randomly, GIT calls might fail with an error message. If this happens, then "git pull" fails, so please wait for the next gitstats execution. Of course, noone will receive bad grades if you have "gitstats false" because of this error message ...
  In this case, you'll see this in your TXT output:

              fatal: early EOF
              fatal: the remote end hung up unexpectedly
              fatal: index-pack failed
              error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054
              

• [MAR/05] Enabled again, runs at 10:00 and 20:00
• [MAR/05] Expects dotnet5 projects
• [MAR/05] Completely reworked unit test engine
• [MAR/05] Only StyleCop.Analyzers is needed; but also in the csproj you must have: EnableNETAnalyzers=true + AnalysisMode=AllEnabledByDefault + EnforceCodeStyleInBuild=true
• The "xxxDoSomethingAsync()" version of the non-crud operations should not use async/await. Simply write "return Task.Run(xxxx)" or "return Task.Factory.StartNew(xxxx)", where xxxx is the call to the regular non-crud operation. Then in the Console App you have to use .Wait() and/or .Result to process the result of the Task...