Add support for XDT config transformation

Feb 17, 2011 at 5:14 PM
Added this work item:

I'd like to give this feature a try if nobody else picks it or is already working on something like that. Won't happen overnight on my side, so no promises on ETA if I end up taking it.



Daniel Cazzulino | Developer Lead | MS MVP | Clarius Consulting | +1 425.329.3471
Feb 17, 2011 at 6:06 PM

I don't think we'd take a dependency on xdt transforms in NuGet.Core (in it's current state, an msbuild task). If it was just a visual studio thing then that might be fine but I think it *should* be a core feature.

Feb 17, 2011 at 6:33 PM

No need to take any external dependencies, I'd say...
Feb 17, 2011 at 6:41 PM

So we re-implement it?

Feb 17, 2011 at 6:51 PM
language features seem simple enough
Feb 17, 2011 at 6:55 PM

I don't like that. There's probably a ton of bug fixes that are in the original version and we'd end up duplicating work. Lets see how others feel about this.

Feb 17, 2011 at 7:04 PM
So, you don't want to take a dependency on VS stuff, and you don't want to implement an opensource version.

So, you don't want to support XDT ever? ;)

I've already faced the serious limitations of the current transformations and the incredibly painful way to work around it via (amazingly error-prone) powershell scripts. And I only had to replace ONE element's attribute.
Feb 17, 2011 at 7:07 PM

I personally don't find this such a bad thing. If needed, we can treat it as an 'experimental' feature for now to see how it goes.

Feb 17, 2011 at 9:44 PM

Especially if Kzu will help us maintain it. J

Feb 17, 2011 at 9:49 PM

The team has spoken, good luck sir :).