New issue

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

Allow starting the repository with new libraries #379

Closed
tusmester opened this Issue May 31, 2018 · 0 comments

Comments

Projects
None yet
3 participants
@tusmester
Copy link
Member

tusmester commented May 31, 2018

Currently a component's dll version has to be the same as the component version in the repository (Packages table) - otherwise the repository will not start.

This applies and will continue to apply only for Release mode libraries.

We want to allow lightweight releases, when the database has not changed (no schema and no content change) only the code has changed to be compatible with the previous component version in the db.

Example

Component releases

These releases all have a corresponding NuGet package with the same version.

Component Version DB change Dependency
CompA 7.1.0 YES
CompA 7.1.1 -
CompA 7.1.2 -
CompA 7.2.0 YES
CompB 3.2.0 YES
CompB 3.2.1 -
CompB 3.2.2 - CompA v7.2.0
CompB 3.3.0 YES CompA v7.2.0
Installed versions (Packages table)
Component Version
CompA 7.1.0
CompA 7.1.1
CompB 3.2.0

Scenario1

Install NuGet package in Visual Studio: CompA, 7.1.2

Result: no error, CompA dll 7.1.2 is compatible with db 7.1.0 (there was no db change since then)

Scenario2

Install NuGet package: CompA, 7.2.0

Result: ERROR, CompA dll 7.2.0 is NOT compatible with db 7.1.1 (there was a db change)
Please execute a patch for CompA.

Scenario3

Install NuGet package: CompB, 3.2.1

Result: no error, CompB dll 3.2.1 is compatible with db 3.2.0 (there was no db change)

Scenario4

Install NuGet package: CompB, 3.2.2 --> this installs CompA 7.2.0 NuGet package, see dependency above

Result: ERROR, CompA 7.2.0 is not installed yet, see Scenario2
Please execute a patch for CompA.

@tusmester tusmester added this to the Sprint 160 milestone May 31, 2018

@kavics kavics self-assigned this Jun 1, 2018

@tusmester tusmester modified the milestones: Sprint 160, Sprint 161 Jun 13, 2018

@kultsar kultsar closed this Jun 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment