We create .NET NuGet packages which have dependencies on native DLLs. We provide a single NuGet package that provides both x86 and amd64 versions of the native DLLs. We then use a build\<packagename>.targets file that will detect how the project is being built and copy the appropriate native DLL to the project's TargetDir. While that works great for EXE projects, it doesn't help with DLL projects which are in turn referenced from EXE projects. I really, really wished VS and/or C# projects had an "official" way to reference native DLLs/projects. This isn't that uncommon of a use case - managed project depends on native dll. Then perhaps NuGet could officially support this as well.
I would love to see .NET Native compilation for use on embedded devices i.e. think .NET CF and/or .NET MF. Low end embedded processors are significantly resource constrained. .NET startup delays due to jitting can be unacceptable. Add to that the size of the .NET Framework requiring larger flash, impacting the BOM (device cost) and this .NET Native support becomes real interesting for the embedded space.
@Ian2 - I agree. I want to see Cortana pushed to Windows 8.x (or 9) and then onto Xbox One. It would also be cool if the team created a UserVoice page for Cortana so folks could request and vote on features.
We have thousands of unit tests that were created before VS 2012. If we would have had the traits capability we probably would have used it. Instead, we relied upon grouping our tests in namespaces that match the namespace of the API they're testing. What we really need in the Test Explorer is the ability to group by Namespace. Class is nice but too fine grained for us as we typically have dozens of associated test classes within a single test namespace. If we could group by Namespace we could more easily test just the part of our API implementation that has changed (due to bug fix or new feature).