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.