From the comments on your announcement:
"Because all the .net binaries in the Bricks central repository are
Curiously, why not only handle signed assemblies and take advantage of
the GAC? If we did do it this way then:
Developer starts a project. Does:
1) bricks install castle-activerecord (which installs assemblies into
2) Creates a project which references a specific version.
3) Notes down this version for use in the build scripts.
CI Build and deployment scripts would do:
bricks install castle-activerecord --version 2.0.213123
There is no concept of 'update', since you would not replace existing
versions, simple get the latest version and put it in the GAC.
bricks install-latest castle-activerecord
bricks install castle-activerecord --latest
bricks install castle-activerecord --version latest
I suspect if we had a system like this which took advantage of the
GAC, more open source projects would strong name and correctly version
You received this message because you are subscribed to the Google Groups "Bricks Development" group.
To post to this group, send email to bricks...@googlegroups.com
To unsubscribe from this group, send email to bricks-devel...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/bricks-devel?hl=en