Replies: 1 comment 2 replies
-
|
This isn't possible in MSBuild's import model. The only way to run code again with "parameters" is by specifying properties to the MSBuild task, which doesn't seem highly appropriate here. You might consider generating the files from a template so you can expand the boilerplate-like things? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have an API that imports many modules. Here's the code snippet:
And each of those
Module.targetsfiles define two properties and import a baseModule.targetsfile:/CRM/Customers/Module.targets
/CRM/Club/Module.targets
And this is the base
Module.targets:So, basically what I'm trying to do is to centralize a module's MSBuild configuration and only provide parameters.
The problem is that MSBuild complains that:
How can I solve this?
Beta Was this translation helpful? Give feedback.
All reactions