sandrock/SrkToolkit

Use new csproj format, drop old things, target AspMvcCore

sandrock opened this issue · 1 comments

sandrock commented

Questions and decisions

v1 and v2 maintenance

  • Use two git branches?

    • (+) dual changes: allows cherry-picking

  • Use two solutions in one git branch?

    • (-) dual changes: copy code or use complex file links and conditional symbols

  • decide how:

    • branch release/v1.1 to maintain v1.1
    • branch release/v1.2 to maintain v1.2
    • branch release/v2.2 to maintain v2.0
    • branch dev/vX/FEATURE for development
    • remove branch master
    • change solution name to avoid IDE craziness

Target frameworks for v2

  • SrkToolkit.Common should have maximum framework compatibility, because there is not much framework-specific code.
    • net40/net45/net46 (for FX aficionados)
    • net6.0/net7.0 (why? / why not?)
    • netstandard2.0 (for whatever else)
  • SrkToolkit.Domain should use the same support as SrkToolkit.Common
  • AspMvc4
    • SrkToolkit.Web.AspMvc4 -> drop support in v2 (old stuff -> use v1)
    • SrkToolkit.Domain.AspMvc4 -> drop support in v2 (old stuff -> use v1)
  • AspMvc5
    • SrkToolkit.Web.AspMvc5 -> drop support in v2 (old stuff -> use v1)
    • SrkToolkit.Domain.AspMvc5 -> drop support in v2 (old stuff -> use v1)
  • AspNetCore2
    • SrkToolkit.Web.AspNetCore2 -> added support in v2
    • SrkToolkit.Domain.AspNetCore2 -> added support in v2
sandrock commented

The dropping of AspMvc5 projects may not be a thing