Henrik,
Thanks for getting back to me with such a detailed response!
So you're basically saying that anytime you do development on, say
Castle.ActiveRecord, you always package it up and then update Castle.Tx
from that locally sourced package?
-rb
On 9/1/2011 2:40 PM, Henrik Feldt wrote:
For C.Tx; first run 'rake prepare', which will generate assembly infos.
Then you could just build normally with MSBuild, open it in VS or run
'rake'. It's a normal solution. If you're looking for stability, then you're
looking for the master branch. Develop-branch is a mess right now, but
openfilesystem_merge is progressing very nicely, and is almost complete.
Nugets:
I also do local nugets - e.g. if you're using logirel to create the folder
structure to build them with rake, you'll get new revision numbers
(major.minor.patch.revision) once in a while (ever hour), and then use
'semver inc' to increment the patch/build number.
So what I do, if I change something from an OSS project is to make sure I
can build it and have it generate nugets automatically, then I increment the
patch number as I add changes to it. I've set up a local nuget server at the
office, which is pushed to automatically ('rake default release'), again
through the scaffold that logirel creates for me (after changing the
buildscripts/paths.rb/URI hash). Then I use the package manager console and
run 'package-update' or 'ls Company.* | % { update-package
TheUpdatedNugetName -ProjectName $_ }' if I only want to upgrade a single
package.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of G. Richard
Bellamy
Sent: den 1 september 2011 12:59
To: [email protected]
Subject: Castle.Transactions
Henrik, or anyone else for that matter :),
What is the recommended way to build the Castle.Transactions project with
assemblies generated during development, rather than via packages?
I have zero experience working with NuGet, and found myself completely
flummoxed until I realized the /lib directory was essentially being ignored
in favor of /packages for dependent assemblies.
I've been looking around, and from what I can tell, there is no "best
practices" method for switching between locally developed and packaged
assemblies.
-rb
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
