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
Broken link to API reference #95
Labels
area-documentation
Issues related to fixing or improving documentation for the client library.
Comments
tameraw
added
the
area-documentation
Issues related to fixing or improving documentation for the client library.
label
Apr 28, 2017
Any updates? |
@micahswitzer - Understand that these broken links are frustrating. It should be fixed now. Let us know if you run into other ones. |
@tameraw - we updated a couple of instances of the same link in the docs on docs.microsoft.com last week. The API reference links should now all be correct - but please let me know if you come across any other instances. |
@dominicbetts - Thanks! |
varunpuranik
pushed a commit
to varunpuranik/azure-iot-sdk-csharp
that referenced
this issue
Dec 13, 2018
* Add snitch module * Add prep-mail tool
brycewang-microsoft
pushed a commit
that referenced
this issue
Jul 14, 2022
template for message enrichments and hub
brycewang-microsoft
pushed a commit
that referenced
this issue
Jul 15, 2022
template for message enrichments and hub
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-documentation
Issues related to fixing or improving documentation for the client library.
In readme.md at the end of the last paragraph before section titled "OS platforms and hardware compatibility" there is a broken link to the API reference documentation. I've encountered this same link other places and I'm really getting frustrated because there seems to be no documentation whatsoever on the .NET Azure IoT Hub sdk. If anyone could point me in the right direction I would be really grateful.
The text was updated successfully, but these errors were encountered: