Skip to content

Conversation

@jornh
Copy link
Contributor

@jornh jornh commented Oct 5, 2014

Fix #375

Or that's what I'm crossing my fingers it will. I'm guessing at where files will be picked up and that's the "beauty" of web-services,you can't really test it out locally 😄 We'll simply have to push something to NuGet.org andsee if it gets picked up.

@jornh jornh mentioned this pull request Oct 5, 2014
@amaitland amaitland added this to the 33.0.0 milestone Oct 5, 2014
@amaitland amaitland added the cef3 label Oct 5, 2014
@amaitland
Copy link
Member

What's the next step with this? Does it require pushing a package?

@jornh
Copy link
Contributor Author

jornh commented Oct 5, 2014

Yes, I guess the only way for us to show up on http://NuDoq.org will be to push a package containing .XML to NuGet proper even AND that it's not a -pre ... Then we can even just sit back, wait and pray that NuDoq will pick it up.

Was what you were asking about?

Only good thing is I don't think adding this shouldn't hurt much 😄 . The little local testing I did/can do with MinimalExample had the .xml files appear in its bin\ folder so at least we will get that.

@amaitland
Copy link
Member

Think that covers it off nicely 😄

Does look fairly low risk, so I'd say merge at your pleasure 😄

jornh added a commit that referenced this pull request Oct 5, 2014
@jornh jornh merged commit 6adb459 into cefsharp:master Oct 5, 2014
@jornh jornh deleted the feature/xmldoc branch October 5, 2014 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NuDoq / bring xml documentation to the web

2 participants