bdb-opensource / soldr Goto Github PK

By removing one reference at a time from a csproj, and then trying to build it, we can figure out which references are not required for a successful build. Add a feature to soldr for automating this process

Should probably be able to control this as a config option

soldr should ignore problems in solutions/projects that are certainly not dependencies of whatever is being built.

Due to the broken CopyLocal feature (see http://stackoverflow.com/questions/320295/how-does-copy-local-work), there's no good way to assume that all dependencies will be copied to the output folder.

The current workaround is in each "executable" project to manually reference all dependencies recursively. This solves the problem for dependencies through recursion but not to dependencies that are in the GAC (see link above).

This feature should copy all dependencies (recursively) into the output folder, and validate that the versions are unique (no two versions of same assembly through different recursive references).

The main problem with this approach is that visual studio won't build correctly if we rely on soldr to work around the dependency bugs of VS. So we'll end up not being able to deploy or even execute from a VS build ( some dlls will be missing)

The command line arguments for the CLI are too complicated. The user should have high-level commands that are easier to understand.

Examples:

soldr update-deps

soldr build

soldr clean

soldr resolve -- prints sln dependencies resolved by soldr, generate graph, etc.

Add feature to generate nuget packages for a target csproj by doing same recursively for all its dependencies.

See http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package

Add a feature to watch the filesystem for changes and build (and deploy/execute?) as soon as a change is detected

Allow specifying scripts to execute before/after a sln is built.

Usage ideas: stop-build-start for winservice projects; copy outputs to external folder (deployment) then commit and push

Add an "install" command that builds a target csproj and copies all outputs and required dlls to some dir.

To make it easy to use allow defining default source base dir in some config file

Example: install the outputs of project named ImportService into current dir:

soldr install ImportService 

Some warnings are being printed every time a dependency's outputs are copied to some target.

For example:

WARN : Project has unexpected outputs (don't have a prefix matching the project name)

We should only print the warning the first time we discover the problem during a build.