Assuming a split between client+extended and client only:
1. To make a web app, users need to:
Reference ActiveRecord, using the client+extended build (is a
separate download or are there just many folders?).
2. To make a desktop app, users need to:
Reference ActiveRecord, using the client build.
3. Using in a common library, users need to:
Somehow the common library needs to reference the right version.
Perhaps I need to add new configurations to the solution such
as Debug-Client and Release-Client and then manually edit the project
files to use $(Configuration) in the hint paths. Maybe I need to use
some sort of IF logic. I do know it was problematic when we had
SQLite set up with different references based on the configuration.
I'm totally open to suggestions as to how to handle this... I
genuinely don't really know how to do this properly.
Assuming a split between client and extended:
1. To make a web app, users need to:
Reference ActiveRecord.
Reference ActiveRecord.Web.
2. To make a client app, users need to:
Reference ActiveRecord.
3. To make a common library, users need to:
Reference ActiveRecord
It seems to me that training users to manage multiple builds of the
same library is more complicated than having them add an extra
assembly required for some particular piece of functionality.
Patrick Earl
--
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.
