XDT (web.config) transform engine released on NuGet
We have just released the XDT transform engine on NuGet, with a license which allows you to redistribute the assembly with your own product. . If you are not familiar with XDT it is a XML transformation engine which drives our web.config transforms in Visual Studio. You can read more about XDT at here. You can now take a dependency on XDT and ship it with your own product.
Why are we doing this?
One of the top 10 most voted features for NuGet is Support Visual Studio (XDT) web.config transforms. To summarize the request, NuGet package authors would like to be able to leverage XDT transforms when a package is installed.
When we initially set out to do this work, we knew that we needed to release XDT under a license which allows it to be redistributed with other 3rd party products. When we solicited feedback on our plans from the NuGet community, we heard some pretty clear feedback. If XDT wouldn’t work for all NuGet scenarios it had no place in NuGet core. We have heard that feedback and are reacting.
The easiest option, and best in my opinion, is to release the XDT code under an open source license. There are no guarantees that we will be able to do this, but things are looking good at this time. Once we make more progress on this I will let you all know.
Since we are hoping that XDT will have permanent home soon we have not setup a formal way to communicate issues. For now the best thing to do is to use the Contact Owners page.
XDT is pretty solid but every product has some bugs. Most of them are pretty minor but you may be likely to run into the bug described below.
Whitespace is not preserved when calling XmldTransformableDocument.Save(FIleSteam)
If you reference Microsoft.Web.Xdt.dll and call XmldTransformableDocument.Save(FIleSteam) the whitespaces are not preserved in the transformed file.
Sayed Ibrahim Hashimi | http://sedodream.com/