...You should have 1 clone of nopCommerce and that is where you work. When nopCommerce adds new features, you use Mercurial to pull a changeset from nopCommerce into your 1 clone.
That's what I've started to do, but I think it gets more complicated than that. I see it as 2 different kinds of changes being done by the nop team: 1) bug fixes, 2) new features for next release.
I want the bug fixes, but I (typically) don't want any new features yet - especially any that would require running a SQL update script that has DDL in it. (Even the scripts that just add new data like localizations, etc. are problematic, because I have to look out for them - i.e. unlike just applying the changeset to the VS code, I've got notice that there is an update.sql, and then manually run the update).
If I decide not to apply a particular changeset, then I run the risk that a later bug fix I want is in some file that was modified in the prior changeset I didn't use - thus dependencies.skyler.severns wrote:
overriding the views by placing the new one in your theme folder.
That's interesting! Would you elaborate on that - does the new view file (e.g. .cshtml) need to be in a subfolder the of the same name as original? e.g. ...\Themes\DarkOrange\Views\Catalog
EDIT: Never mind the question - I tried it out, and yes, the folder structure is required:
see my last post in https://www.nopcommerce.com/boards/t/11206/checkout-stopped-working.aspx?p=3
for more details about customizing views.