We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use two git branches?
Use two solutions in one git branch?
decide how:
release/v1.1
release/v1.2
release/v2.2
dev/vX/FEATURE
master
SrkToolkit.Common
SrkToolkit.Domain
SrkToolkit.Web.AspMvc4
SrkToolkit.Domain.AspMvc4
SrkToolkit.Web.AspMvc5
SrkToolkit.Domain.AspMvc5
SrkToolkit.Web.AspNetCore2
SrkToolkit.Domain.AspNetCore2
The text was updated successfully, but these errors were encountered:
migrate csproj to sdk version, move files around, migrate code, comme…
5bdb5af
…nt non-migrated code... #20
migrate code, comment non-migrated code... #20
a0a9646
The dropping of AspMvc5 projects may not be a thing
AspMvc5
Sorry, something went wrong.
sandrock
No branches or pull requests
Questions and decisions
v1 and v2 maintenance
Use two git branches?
Use two solutions in one git branch?
decide how:
release/v1.1
to maintain v1.1release/v1.2
to maintain v1.2release/v2.2
to maintain v2.0dev/vX/FEATURE
for developmentmaster
Target frameworks for v2
SrkToolkit.Common
should have maximum framework compatibility, because there is not much framework-specific code.SrkToolkit.Domain
should use the same support asSrkToolkit.Common
SrkToolkit.Web.AspMvc4
-> drop support in v2 (old stuff -> use v1)SrkToolkit.Domain.AspMvc4
-> drop support in v2 (old stuff -> use v1)SrkToolkit.Web.AspMvc5
-> drop support in v2 (old stuff -> use v1)SrkToolkit.Domain.AspMvc5
-> drop support in v2 (old stuff -> use v1)SrkToolkit.Web.AspNetCore2
-> added support in v2SrkToolkit.Domain.AspNetCore2
-> added support in v2The text was updated successfully, but these errors were encountered: