Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ETA for official release / state of project #7

Open
mwpowellhtx opened this issue Dec 26, 2016 · 0 comments
Open

ETA for official release / state of project #7

mwpowellhtx opened this issue Dec 26, 2016 · 0 comments

Comments

@mwpowellhtx
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant