reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mariia Mykhailova (JIRA)" <>
Subject [jira] [Commented] (REEF-1255) Specify packages shared between projects on solution level
Date Thu, 07 Jul 2016 22:38:10 GMT


Mariia Mykhailova commented on REEF-1255:

The discussion in PR pointed out that the scenario for adding new NuGet dependency to a project
involves an entry for this package being created in project's packages.config, which gets
re-created for that purpose. 

We can take middle ground - keep per-project packages.config files themselves (so they don't
get re-created) but keep them empty, and when a new package is added move it to solution-level
packages.config (manually but that's the price for having single place for versions of all

Or we can just live with the current state of things, assuming that package version update
is a rare event and can be handled manually. VS NuGet package manager allows to update version
in all projects at once but it does some extra things like generate {{app.config}} for all
projects, so it involves manual work anyways.

Does anybody feel strongly about either approach?

> Specify packages shared between projects on solution level
> ----------------------------------------------------------
>                 Key: REEF-1255
>                 URL:
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Mariia Mykhailova
>            Priority: Minor
> It would be nice to specify versions of packages used in multiple .NET projects not in
each project's {{packages.config}} in a single place, so that we don't run into issues with
different projects using different versions, like REEF-1015. One step further is to declare
all packages in solution-level {{packages.config}} and eliminate project-level files altogether.

This message was sent by Atlassian JIRA

View raw message