How to auto build App Y when Library X builds (and upgrade App Y's reference to Library X before)?

rajiv's Avatar


13 Jul, 2018 12:47 PM

Folks -

Whats the best way to structure appveyor projects to handle a situation where we want a successful build of a common library to trigger a couple of other projects that actually consume this library? I have borrowed from the Deployment Project approach and now have the ability to trigger other projects but before those builds are initiated, I want them to upgrade their <PackageReference> to the latest version of this common library (which is being exposed via a private nuget account feed on appveyor).

In other words, I would like:
 1) a successful build of Library X (generating version N+1) to trigger the build of App Y and App Z
 2) but make sure that App Y and App Z have both upgraded their
       <PackageReference Include="Library X" Version="N"/>
   to <PackageReference Include="Library X" Version="N+1"/>

All the projects in question are targeting .netcoreapp2.0. And of course App Y and App Z should also do a normal build if any of their direct code base has changed.

Has anyone dealt with this situation and if so - what's the recommended way of handling this?

Thanks very much

  1. Support Staff 1 Posted by Ilya Finkelshte... on 13 Jul, 2018 06:49 PM

    Ilya Finkelshteyn's Avatar

    Per my knowledge <PackageReference Include="Library X" Version="*"/> should always restore latest package, can you try "*" instead of "N"?

  2. 2 Posted by rajiv on 15 Jul, 2018 07:44 PM

    rajiv's Avatar

    Thanks Ilya! While '*' doesn't seem to work, other format variations such as Major.minor work. The full reference:

  3. rajiv closed this discussion on 15 Jul, 2018 07:45 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac