I suggest you ...

Allow VisualStudioToolsManifest.xml to be TFM specific

In NuGet packages we can now place a file in \tools\VisualStudioToolsManifest.xml that list the set of controls that should be added to the Toolbox in the visual studio XAML designer. This works both for UWP and WPF.
However there's no way to make this TFM specific. This poses a problem if you for instance have both WPF and UWP controls in your nuget package and the set of controls is not 100% the same, or if you are providing multiple TFV where for instance newer TFV provides extra controls and deprecates older ones. Ie UAP10.0.14393, UAP10.0.16299, or net451, net461 etc.
I'd suggest that in addition to using
\tools\VisualStudioToolsManifest.xml
we can also use
tools\uap10.0\VisualStudioToolsManifest.xml
tools\uap10.0.16299\VisualStudioToolsManifest.xml
tools\net461\VisualStudioToolsManifest.xml

etc.

40 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Morten Nielsen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base