We have added a few test projects to our Umbraco solution which have a reference to the main Umbraco project. This is causing the 'base' front end folders and files to be generated on the tests running.
Is this intended?
Even if so is there anything we can do to stop this from happening?
This is also a problem when trying to separate out sections of the solution into different projects as well due to the need to reference Umbraco.Cms.
After playing around with your suggestion and looking at some other options I have come across 2 things.
The suggestion of using the base packages is perfect for projects that are referenced by the Umbraco project. (No idea why I didn't just do this!)
This doesn't help for test projects as you need to reference the main Umbraco project. However I found you can use the private asset = contentfiles;analyzers;build;buildTransitive; flag on the reference and that stops those files being generated in 'parent' projects.
This solves the issue however I am not yet sure of any side effects of doing this.
Test projects in Umbraco V9 (RC1)
Hi all o/
We have added a few test projects to our Umbraco solution which have a reference to the main Umbraco project. This is causing the 'base' front end folders and files to be generated on the tests running.
This is also a problem when trying to separate out sections of the solution into different projects as well due to the need to reference Umbraco.Cms.
Thanks
You should make references to
and/or
depending on that you are testing.
The Umbraco.Cms package is just a meta-package only having dependencies but no code.
After playing around with your suggestion and looking at some other options I have come across 2 things.
This solves the issue however I am not yet sure of any side effects of doing this.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.