Commerce module in OrchardCore main project - PackageReference vs. ProjectReference #282
-
|
I added the OrchardCore.Commerce project as a module to the original OrchardCore project. If I leave the PackageReferences I can see and activate the Commerce module in the Features section, but if I delete the PackageReferences and add all the individual ProjectReferences the module is not displayed. Commented as PackageReference
Added as ProjectReference
My goal is to have the Commerce module source in the OrchardCore main project source. Is it a feasible solution? Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
This is not a supported scenario. Some of the other packages (e.g. Lombiq.HelpfulLibraries.OrchardCore) also reference the OC packages; so both will end up loaded which causes conflicts - unless you include a lot of altered source in your repo. Generally it's not a good developer practice to include the OC source code because it slows down development and compilation. Why do you want it? |
Beta Was this translation helpful? Give feedback.
-
|
I wanted to have a single source for all code so that I could easily navigate through all projects, classes and implementations. The build would only happen once and after that I would disable all already built projects keeping only the ones I work on. Thank you for your answer. |
Beta Was this translation helpful? Give feedback.
This is not a supported scenario. Some of the other packages (e.g. Lombiq.HelpfulLibraries.OrchardCore) also reference the OC packages; so both will end up loaded which causes conflicts - unless you include a lot of altered source in your repo. Generally it's not a good developer practice to include the OC source code because it slows down development and compilation. Why do you want it?