OutputPath property does not support absolute paths

[cpfister]

http://netmf.codeplex.com/workitem/2289

[smaillet-ms]

This is due to several parts of the build using msbuild properties like this: $(ProjectDir)$(OutDir), which assumes that OutDir is always a relative path from the Project directory.

[lt72]

This is too risky to fix at this stage, we will move to next release 4.5, hopefully by year end

[cpfister]

The more general context of this issue: we wanted to have a Visual Studio solution setup where we can support several platforms (e.g. NETMF 4.3, NETMF 4.4 and the full desktop framework) in a way that portable source files only exist once (so we don't have to keep several copies in sync), but platform-dependent source files can exist in several variants. If I remember correctly, this issue here was one of those that we found when trying to create such an environment.

[smaillet-ms]

@cpfister Thanks for the additional information. Unfortunately, as you can probably see by the recalled/closed pull requests I've made on this it is not a simple fix. While the simple fix resolves the build, it completely breaks debug and deploy for reasons presently unknown. Digging into and changing that part of the system at this stage is rather high risk. We'll keep looking into this but it isn't expected we'll get to a solution in the v4.4 release.

[cpfister]

Sure, no problem. I just wanted to give a bit more context than in the original post.

Thanks and best regards

Cuno

From: Steve Maillet [mailto:notifications@github.com]
Sent: 05 August, 2015 18:37
To: NETMF/netmf-interpreter
Cc: Cuno Pfister
Subject: Re: [netmf-interpreter] OutputPath property does not support absolute paths (#238)

@cpfisterhttps://github.com/cpfister Thanks for the additional information. Unfortunately, as you can probably see by the recalled/closed pull requests I've made on this it is not a simple fix. While the simple fix resolves the build, it completely breaks debug and deploy for reasons presently unknown. Digging into and changing that part of the system at this stage is rather high risk. We'll keep looking into this but it isn't expected we'll get to a solution in the v4.4 release.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/238#issuecomment-128063905.