Year: 2018

Detailed list about my activities in programming in 2018

This is what I have done in 2018:

Base learning

  • Angular
  • R
  • CI /CD with Azure DevOps Syntax base
  • Roslyn
  • .NET Core

 

Presentations:

  • Continuing the presentations about Design Patterns ( course )
  • Various Presentations ( ROSLYN AOP, Introduction to R, Messaging with MediatR)
  • Presenting at OWASP : Top 10 OWASP and counter attacks in .NET Core
  • Presenting at Code Camp Bucuresti .NET Core and Angular – deploy on Windows, Android, Linux ( Mac + iOS) : https://github.com/ignatandrei/AngNetCoreDemo

 

 

Free Projects :

             

  • Literary Awards – full javascript, database in the browser

Site Web: https://ignatandrei.github.io/LiteraryAwards/

Android :https://play.google.com/store/apps/details?id=com.msprogrammer.com

 

  • ONG Declaration for Romania

GitHub : https://ignatandrei.github.io/Decl230/

Android: https://play.google.com/store/apps/details?id=decl203.msprogrammer.ro

 

Starting Stankins v2  : https://github.com/ignatandrei/stankins , Live Demo at https://azurestankins.azurewebsites.net

 

 

Components:

  • AOP_With_Roslyn – .NET Global Tool for AOP with ROSLYN

GitHub :https://github.com/ignatandrei/AOP_With_Roslyn

NuGet: https://www.nuget.org/packages/dotnet-aop

 

  • AspNetCoreImageTagHelper – .NET Core for base 64 images

GitHub: https://github.com/ignatandrei/AspNetCoreImageTagHelper

NuGet: https://www.nuget.org/packages/AspNetCore.Mvc.ImageBase64/

Mentioned on https://github.com/aspnet/Mvc

  • Versions For .NET Core written in Angular:

NPM  : https://www.npmjs.com/package/versions-netcore-angular

Live Demo: https://azurestankins.azurewebsites.net/about

 

Books:

( free download at http://msprogrammer.serviciipeweb.ro/2018/09/03/making-open-source-component-from-idea-to-deploy-with-examples-from-net-core/ )

 

Various:

 

 

 

OpenSource library- Source Link

Part 1

Implement Open-source library guidance

Part 2

OpenSource library – Cross-platform targeting

Part 3

OpenSource library-Dependencies

Part 4

OpenSource library- Source Link

Part 5

OpenSource library-versioning

Part 6

OpenSource library- Breaking changes

Part 7

OpenSource library- conclusion

The documentation at https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/sourcelink says to enable source link.


Nr

Recomandation

AOP Roslyn

1

CONSIDER using SourceLink to add source control metadata to your assemblies and NuGet packages.

 Modified(1)

2

CONSIDER including symbol files (*.pdb) in the NuGet package.

 Done already(2)

For (1) : I have followed the instructions at https://github.com/dotnet/sourcelink/blob/master/README.md

For(2): It was done already by csproj configuration.

Friday Links 299

  • development – Programmatically read Excel file in SharePoint 2013 sandbox solution gives permission error – SharePoint Stack Exchange
  • https://gist.githubusercontent.com/abfo/c290cf22ab52dec47e59e87206c3371b/raw/7ab438a90d1f55c461dcfcf6b277cda5af1a601b/Program.cs
  • Get auth tokens – Documentation – Microsoft Graph
  • microsoftgraph/aspnet-todo-rest-sample: This sample shows how to read and write into an Excel document stored in your OneDrive for Business account by using the Excel REST APIs.
  • The State of JavaScript 2018: Front-end Frameworks – Overview
  • 29 Must Read Books For Programmers – DEV Community
  • Caching http requests to debug faster – Meziantou’s blog
  • Using a headless browser to capture page screenshots
  • How to upload a file to Google Drive from the command lineOliverMarshall.net
  • Download Remote Server Administration Tools for Windows 10 from Official Microsoft Download Center
  • Putting it all together – CORS tutorial – IIS Field Readiness – blog of the European IIS team
  • Deployment — Portainer 1.19.2 documentation
  • Use Action Filters to cut down your context.SaveChanges calls
  • Make Beautiful Tables with the Formattable Package | Displayr
  • A Mathematician’s Perspective on Topological Data Analysis and R · R Views

    • OpenSource library–Dependencies

    Part 1

    Implement Open-source library guidance

    Part 2

    OpenSource library – Cross-platform targeting

    Part 3

    OpenSource library-Dependencies

    Part 4

    OpenSource library- Source Link

    Part 5

    OpenSource library-versioning

    Part 6

    OpenSource library- Breaking changes

    Part 7

    OpenSource library- conclusion

    Now trying to respect what it says at https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/dependencies .

    Nr

    Recomandation

    AOP Roslyn

    1

    DO review your .NET library for unnecessary dependencies.

    		 Done manually(1)

    2

    DO NOT have NuGet package references with no minimum version

    		 Done already(2)

    3

    AVOID NuGet package references that demand an exact version

    		 Done already(2)

    4

    AVOID NuGet package references with a version upper limit

    		 Done already(2)

    5

    CONSIDER referencing shared source packages for small, internal pieces of functionality

    		 N/A(5)

    6

    CONSIDER making your package a shared source package if it provides small, internal pieces of functionality.

    		 N/A(5)

    7

    DO reference shared source packages with PrivateAssets=”All”.

    		 N/A(5)

    8

    DO NOT have shared source package types in your public API.

    		 N/A(5)

    9

    DO NOT publish shared source packages to NuGet.org.

    		 N/A(5)

    For (1): Reviewing .NET library for unnecessary dependencies is practically a manual process. Could be a dotnet global tool – but for the moment I just inspected the .csproj for references and see that all are ncessary

    For (2): As I read from documentation “Typically, the package reference version in the project file is the minimum version and there’s no maximum.” .So doing nothing I am at the good point

    For (5), I usually put a new dll or NuGet package – I do not share code source. So this is done also without friction.

    Friday Links 298

  • Nick Craver – Stack Overflow: How We Do Monitoring – 2018 Edition
  • Nick Craver – Stack Overflow: The Hardware – 2016 Edition
  • Exceptional : ASP.NET Core
  • Nick Craver – Stack Overflow: How We Do Monitoring – 2018 Edition
  • opserver/Opserver: Stack Exchange’s Monitoring System
  • Nick Craver – Software Imagineering
  • StackExchange/BosunReporter: A .NET client to send metrics to Bosun/OpenTSDB. https://bosun.org
  • Scalable frontend #2
    —
    Common patterns – The Miners
  • Scalable frontend #1
    —
    Architecture – The Miners
  • Reject the tyranny of being picked: pick yourself | Seth’s Blog
  • Background tasks with hosted services in ASP.NET Core | Microsoft Docs
  • Implement background tasks in microservices with IHostedService and the BackgroundService class | Microsoft Docs
  • Functional Programming Principles in Javascript | Codementor
  • How to read excel file from SharePoint Document Library .NET/C#
  • Programmatically read excel file from SharePoint online document library(o365) and save to sql server database.

    • OpenSource library–Strong naming

    The strong naming is something that I have not have done usually, so it will be interesting following https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming .

    Nr

    Recomandation

    AOP Roslyn

    1

    CONSIDER strong naming your library’s assemblies.

    Not –see below

    2

    CONSIDER adding the strong naming key to your source control system.

    easy- not

    3

    CONSIDER incrementing the assembly version
    on only major version changes to help
    users reduce binding redirects, and how often they’re updated.

    not

    4

    DO NOT add, remove, or change the strong naming key.

    easy- not

    5

    DO NOT publish strong-named and non-strong-named versions of your library.

    easy – not

    I have tried to add signing – it is pretty easy in Visual Studio to generate a new pfx fiel to sign code. However, when compiling, it requires all dependencies to be signed

    CSC : error CS8002: Referenced assembly ‘PortableConsoleLibs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ does not have a strong name. [C:\projects\aop-with-roslyn\AOPRoslyn\aopCmd\aop.csproj]

    So , if one of your referenced libraries is not code signed, it is a big no

    The other requirements are pretty easy..

    Friday Links 297

  • Web-animation toolkit
  • Nick Craver – Stack Overflow: How We Do Monitoring – 2018 Edition
  • Test Stack Overflow Domain
  • Measuring Page Load Speed with Navigation Timing – HTML5 Rocks
  • Stack Overflow’s Bosun Architecture · Kyle Brandt
  • StackExchange/BosunReporter: A .NET client to send metrics to Bosun/OpenTSDB. https://bosun.org
  • scollector
  • Creating Service Monitor Application with .NET Core – CodeProject
  • KevinDockx/StreamExtensions: A set of helper extension methods (on Stream) for working with streams. Particularly useful for interaction with an API through HttpClient.
  • 10 Javascript Compression Tools and Libraries for 2019
  • My way of working with internal nuget packages – DEV Community
  • The Most Useful 40 Web Sites You Don’t Know About
  • www.papertoys.com
  • www.codementor.io
  • Angular Validators With Conditional Validation In Reactive Forms | Codementor

    • OpenSource library – Cross-platform targeting

    Part 1

    Implement Open-source library guidance

    Part 2

    OpenSource library – Cross-platform targeting

    Part 3

    OpenSource library-Dependencies

    Part 4

    OpenSource library- Source Link

    Part 5

    OpenSource library-versioning

    Part 6

    OpenSource library- Breaking changes

    Part 7

    OpenSource library- conclusion

    At https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/cross-platform-targeting there are the recommendations  for Cross platform. Let’s see what needs to be done for https://github.com/ignatandrei/AOP_With_Roslyn

    Let’s see:

     

    Nr Recommandation AOP Roslyn
    1 DO start with including a netstandard2.0 target. Done – the main dll, AOPRoslyn, is already .netstandard2,0
    2 AVOID including a netstandard1.x target. Not needed
    3 DO include a netstandard2.0 target if you require a netstandard1.x target. Not needed
    4 DO NOT include a .NET Standard target if the library relies on a platform-specific app model. Not needed
    5 CONSIDER targeting .NET implementations in addition to .NET Standard. Not needed
    6 AVOID using multi-targeting with .NET Standard if your source code is the same for all targets. Not needed
    7 CONSIDER adding a target for net461 when you’re offering a netstandard2.0 target. OK> see later point 9

     
    8 DO distribute your library using a NuGet package. Done

    https://www.nuget.org/packages/dotnet-aop

     
    9 DO use a project file’s TargetFrameworks property when multi-targeting Struggle to implement/ partially done – modified AOPRoslyn.csproj
    10 CONSIDER using MSBuild.Sdk.Extras when multi-targeting for UWP and Xamarin as it greatly simplifies your project file. Not needed
    11 DO NOT include a Portable Class Library (PCL) target. OK
    12 DO NOT include targets for .NET platforms that are no longer supported. Not needed

    I tried to modify to include

    <TargetFrameworks>netstandard2.0;net461</TargetFrameworks>

    ( Attention: Frameworks , not Framework)

    First , you should publish the .csproj

    dotnet publish <path to csproj>

    should be modified with -f=”netstandard2.0″

    Then , each dependency should support it :

    error NU1202: Package PortableConsoleLibs 1.0.0 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package PortableConsoleLibs 1.0.0 supports: netcoreapp2.0 (.NETCoreApp,Version=v2.0)

    So you should contact the owners to support it – or re-compile the sources, if you have.

    So I will stick with

    “DO NOT include targets for .NET platforms that are no longer supported.” including NET461.

    Conclusion: 11 / 12 it is a good score.

    Friday links 296

    Andrei Ignat weekly software news(mostly .NET)

    * indicates required

    Please select all the ways you would like to hear from me:

    You can unsubscribe at any time by clicking the link in the footer of our emails. For information about our privacy practices, please visit our website.

    We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices here.