Directory specification recommendation for using NuGet to add libraries to a WiX project

[Heath Stewart]

While groking the NuGet code working on some other issues, I noticed a comment that WixProjectSystem.AddReference doesn't make sense but as one of the WiX contributors, I can envision (and have discussed in their dev group) adding both .wixlibs (much like static .libs in native projects) and extensions (custom assemblies to add functionality to WiX) using NuGet.

Currently, we have two mainline forks of WiX: wix3 and wix4. While mostly backward compatible, wix4 is still under active development (hasn't even had its first RTW yet) and may change so we were thinking that supporting these as baselines make sense. So, following how you can include libs for different .NET baselines, does the following make sense from a packaging view?

• libs/wix3
• libs/wix4
• libs/wix (i.e. don't care about version, or should libs/wix3 just work for wix4+ if those directories aren't found?)

File extensions supported would include - but are not limited to - .wixlib and .dll, where adding a .wixlib would effectively add a <WixLibrary> element to the .wixproj and a .dll would effectively add a <WixExtension> element to the .wixproj.

I've been a long-time user of NuGet, but since I'm just starting to get into the development side of it does this jive with best/current practices?