You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sure I'm not alone looking for Intellisense supported for NuSpec files. Nothing more annoying than an otherwise valid Xml file, pointing to the XmlNs, and not having Intellisense "see" anything behind the Xsd.
I see it listed as Alpha; actually, apparently was listed at one point, then de-listed after all. Any reasons as to why? Moreover, why no follow through?
I suppose that one possible workaround would be to work with the "nuspec" as though it were Xml on the front side of things, then through a series of post-build events copy to nuspec after all. Still, would be nice to have "direct" support for Intellisense without having to jump through those sorts of hoops. Testing that hypothesis, that does not work, either.
Doing a little more digging, it seems like this is more related to a VS2015 backlog item that appears to have since been "closed". However, this is hardly closed from an end-user POV, IMO.
So, at this point, is it even possible? Or something that is broken until/unless the VS team decides to address it?
Thanks!
The text was updated successfully, but these errors were encountered:
I'm sure I'm not alone looking for
Intellisense
supported forNuSpec
files. Nothing more annoying than an otherwise validXml
file, pointing to theXmlNs
, and not havingIntellisense
"see" anything behind theXsd
.I see it listed as Alpha; actually, apparently was listed at one point, then de-listed after all. Any reasons as to why? Moreover, why no follow through?
I suppose that one possible workaround would be to work with the "nuspec" as though it were Xml on the front side of things, then through a series of post-build events copy to nuspec after all. Still, would be nice to have "direct" support for Intellisense without having to jump through those sorts of hoops. Testing that hypothesis, that does not work, either.
Doing a little more digging, it seems like this is more related to a VS2015 backlog item that appears to have since been "closed". However, this is hardly closed from an end-user POV, IMO.
So, at this point, is it even possible? Or something that is broken until/unless the VS team decides to address it?
Thanks!
The text was updated successfully, but these errors were encountered: