Import element does not expand ItemGroup correctly

Multi tool use
Multi tool use












0














I'm trying to populate an ItemGroup with directory basenames, pass it through a transform to create absolute paths from them and import the files residing there. It works flawlessly in a Message element, but fails to do anything in an Import. What am I missing?



<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<MyDependencies Include="Dir1" />
<MyDependencies Include="Dir2" />
</ItemGroup>

<!-- "Expansion: C:pathDir1import.targets;C:somepathDir2import.targets" -->
<Target Name="TestMessage" BeforeTargets="PrepareForBuild">
<Message
Importance="High"
Text="Expansion: @(MyDependencies -> 'C:path%(Identity)import.targets')"
/>
</Target>

<!-- Uncomment to trigger error -->
<!--<Import Project="@(MyDependencies -> 'C:path%(Identity)import.targets')" />-->
</Project>


The Import's path remains unexpanded and leads to:



error MSB4102: The value "@(MyDependencies -> 'C:path%(Identity)import.targets')" of the "Project" attribute in element <Import> is invalid. Illegal characters in path.









share|improve this question






















  • This is a classic evaluation order problem (and a duplicate IIRC). I can't pinpoint the exact piece of documentation stating this but the transform is only evaluated in a pass after importing. edit well docs.microsoft.com/en-us/visualstudio/msbuild/… says "During the execution phase of a build ... Item values and item transformations are also expanded" and it says Import is part of the evaluation phase so I guess that does answer it.
    – stijn
    Dec 28 '18 at 9:53












  • @stijn damn, the documentation is incomplete but it looks like you're right and item groups plain don't work with Import...
    – Quentin
    Dec 28 '18 at 14:57
















0














I'm trying to populate an ItemGroup with directory basenames, pass it through a transform to create absolute paths from them and import the files residing there. It works flawlessly in a Message element, but fails to do anything in an Import. What am I missing?



<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<MyDependencies Include="Dir1" />
<MyDependencies Include="Dir2" />
</ItemGroup>

<!-- "Expansion: C:pathDir1import.targets;C:somepathDir2import.targets" -->
<Target Name="TestMessage" BeforeTargets="PrepareForBuild">
<Message
Importance="High"
Text="Expansion: @(MyDependencies -> 'C:path%(Identity)import.targets')"
/>
</Target>

<!-- Uncomment to trigger error -->
<!--<Import Project="@(MyDependencies -> 'C:path%(Identity)import.targets')" />-->
</Project>


The Import's path remains unexpanded and leads to:



error MSB4102: The value "@(MyDependencies -> 'C:path%(Identity)import.targets')" of the "Project" attribute in element <Import> is invalid. Illegal characters in path.









share|improve this question






















  • This is a classic evaluation order problem (and a duplicate IIRC). I can't pinpoint the exact piece of documentation stating this but the transform is only evaluated in a pass after importing. edit well docs.microsoft.com/en-us/visualstudio/msbuild/… says "During the execution phase of a build ... Item values and item transformations are also expanded" and it says Import is part of the evaluation phase so I guess that does answer it.
    – stijn
    Dec 28 '18 at 9:53












  • @stijn damn, the documentation is incomplete but it looks like you're right and item groups plain don't work with Import...
    – Quentin
    Dec 28 '18 at 14:57














0












0








0







I'm trying to populate an ItemGroup with directory basenames, pass it through a transform to create absolute paths from them and import the files residing there. It works flawlessly in a Message element, but fails to do anything in an Import. What am I missing?



<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<MyDependencies Include="Dir1" />
<MyDependencies Include="Dir2" />
</ItemGroup>

<!-- "Expansion: C:pathDir1import.targets;C:somepathDir2import.targets" -->
<Target Name="TestMessage" BeforeTargets="PrepareForBuild">
<Message
Importance="High"
Text="Expansion: @(MyDependencies -> 'C:path%(Identity)import.targets')"
/>
</Target>

<!-- Uncomment to trigger error -->
<!--<Import Project="@(MyDependencies -> 'C:path%(Identity)import.targets')" />-->
</Project>


The Import's path remains unexpanded and leads to:



error MSB4102: The value "@(MyDependencies -> 'C:path%(Identity)import.targets')" of the "Project" attribute in element <Import> is invalid. Illegal characters in path.









share|improve this question













I'm trying to populate an ItemGroup with directory basenames, pass it through a transform to create absolute paths from them and import the files residing there. It works flawlessly in a Message element, but fails to do anything in an Import. What am I missing?



<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<MyDependencies Include="Dir1" />
<MyDependencies Include="Dir2" />
</ItemGroup>

<!-- "Expansion: C:pathDir1import.targets;C:somepathDir2import.targets" -->
<Target Name="TestMessage" BeforeTargets="PrepareForBuild">
<Message
Importance="High"
Text="Expansion: @(MyDependencies -> 'C:path%(Identity)import.targets')"
/>
</Target>

<!-- Uncomment to trigger error -->
<!--<Import Project="@(MyDependencies -> 'C:path%(Identity)import.targets')" />-->
</Project>


The Import's path remains unexpanded and leads to:



error MSB4102: The value "@(MyDependencies -> 'C:path%(Identity)import.targets')" of the "Project" attribute in element <Import> is invalid. Illegal characters in path.






msbuild msbuild-itemgroup






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 27 '18 at 16:42









Quentin

44.4k584140




44.4k584140












  • This is a classic evaluation order problem (and a duplicate IIRC). I can't pinpoint the exact piece of documentation stating this but the transform is only evaluated in a pass after importing. edit well docs.microsoft.com/en-us/visualstudio/msbuild/… says "During the execution phase of a build ... Item values and item transformations are also expanded" and it says Import is part of the evaluation phase so I guess that does answer it.
    – stijn
    Dec 28 '18 at 9:53












  • @stijn damn, the documentation is incomplete but it looks like you're right and item groups plain don't work with Import...
    – Quentin
    Dec 28 '18 at 14:57


















  • This is a classic evaluation order problem (and a duplicate IIRC). I can't pinpoint the exact piece of documentation stating this but the transform is only evaluated in a pass after importing. edit well docs.microsoft.com/en-us/visualstudio/msbuild/… says "During the execution phase of a build ... Item values and item transformations are also expanded" and it says Import is part of the evaluation phase so I guess that does answer it.
    – stijn
    Dec 28 '18 at 9:53












  • @stijn damn, the documentation is incomplete but it looks like you're right and item groups plain don't work with Import...
    – Quentin
    Dec 28 '18 at 14:57
















This is a classic evaluation order problem (and a duplicate IIRC). I can't pinpoint the exact piece of documentation stating this but the transform is only evaluated in a pass after importing. edit well docs.microsoft.com/en-us/visualstudio/msbuild/… says "During the execution phase of a build ... Item values and item transformations are also expanded" and it says Import is part of the evaluation phase so I guess that does answer it.
– stijn
Dec 28 '18 at 9:53






This is a classic evaluation order problem (and a duplicate IIRC). I can't pinpoint the exact piece of documentation stating this but the transform is only evaluated in a pass after importing. edit well docs.microsoft.com/en-us/visualstudio/msbuild/… says "During the execution phase of a build ... Item values and item transformations are also expanded" and it says Import is part of the evaluation phase so I guess that does answer it.
– stijn
Dec 28 '18 at 9:53














@stijn damn, the documentation is incomplete but it looks like you're right and item groups plain don't work with Import...
– Quentin
Dec 28 '18 at 14:57




@stijn damn, the documentation is incomplete but it looks like you're right and item groups plain don't work with Import...
– Quentin
Dec 28 '18 at 14:57

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53948207%2fimport-element-does-not-expand-itemgroup-correctly%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53948207%2fimport-element-does-not-expand-itemgroup-correctly%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







rYMFkdAnscyll3LwUu3PzR hKZLio37,RDVe K SCej2ll6CyyvxVqnbvEEKFEJ,E6HoUdUWV PBDly1H
XXnAw,kH1JLD10zA vptpw Hd d

Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas