-
Notifications
You must be signed in to change notification settings - Fork 6k
VS2017 Getting Started doc updates #1679
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
VS2017 Getting Started doc updates #1679
Conversation
@guardrex, |
|
||
1. Let's try to change the value of the variables to see how this affects our program. If the **Immediate window** is not visible, display it by choosing the **Debug**, **Windows**, **Immediate** menu item. The **Immediate window** lets you interact with the application you're debugging. | ||
1. You can change the value of the variables to see how it affects your program. If the **Immediate Window** is not visible, display it by choosing the **Debug > Windows > Immediate** menu item. The **Immediate Window** lets you interact with the application you're debugging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
choosing 👉 selecting
.openpublishing.redirection.json
Outdated
"redirect_document_id": true | ||
}, | ||
{ | ||
"source_path": "docs/csharp/getting-started/debugging-with-visual-studio-2017.md", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove this redirect .... this one had to stay the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't rename that one (or the publishing one). The debugging-with-visual-studio.md
and the publishing-with-visual-studio.md
are 301 redirecting.
Did you want to ignore that and move the content over to those files anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Double-301? ... If a proxy or a system has a cached 301 on the non-2017 address and they request the 2017-version of the doc ... it then 301's back to the non-2017 doc. Hum. 🤔
EDIT: Should be ok. I expect a cache update when the 301 goes back (I hope).
.openpublishing.redirection.json
Outdated
"redirect_document_id": true | ||
}, | ||
{ | ||
"source_path": "docs/csharp/getting-started/publishing-with-visual-studio-2017.md", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove this redirect .... this one had to stay the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't finished my review, but so far, so good!
|
||
1. On the Visual Studio menu bar, choose **File > New > Project**. | ||
|
||
1. In the **New Project** dialog, expand the **Other Project Types** node, and select **Visual Studio Solutions**. Name the solution "ClassLibraryProjects" and select the **OK** button. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should the project name be inline code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to follow the existing pattern where if the user is directed to type something the text is in quotes. In other places, the project name is in-line code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point.
|
||
## Next step | ||
|
||
You've successfully built the library. Because you haven't called any of its methods, you don't know whether it works as expected. The next step in developing your library is to test it by using a [C# Unit Test Project](testing-library-with-visual-studio.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wondering if we also should start adding the Prev and Next buttons
@guardrex Can you update the merge conflicts here as well? |
@BillWagner Conflicts seem* to be fixed. seem* = I better go back over the changes one more time and see how the report looks after the build finishes. I'll remove the WIP label and ping you when ready. |
@BillWagner ready for 👀 |
Update toc.md Update index.md Update testing-library-with-visual-studio.md Update debugging-with-visual-studio.md Update index.md Update publishing-with-visual-studio-2017.md Update consuming-library-with-visual-studio-2017.md Update with-visual-studio-2017.md Update libraries-with-vs.md Update .openpublishing.redirection.json Update publishing-with-visual-studio.md Update debugging-with-visual-studio-2017.md Create consuming-library-with-visual-studio.md Delete consuming-library-with-visual-studio-2017.md Update debugging-with-visual-studio.md Update toc.md Update index.md Update index.md Update publishing-with-visual-studio-2017.md Update consuming-library-with-visual-studio.md Update with-visual-studio-2017.md Create library-with-visual-studio.md Delete library-with-visual-studio-2017.md Update publishing-with-visual-studio.md Update toc.md Update index.md Update index.md Update consuming-library-with-visual-studio.md Update with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update consuming-library-with-visual-studio.md Update debugging-with-visual-studio-2017.md Update consuming-library-with-visual-studio.md Update library-with-visual-studio.md Update publishing-with-visual-studio-2017.md Update library-with-visual-studio.md Create new_project.png Add files via upload Update library-with-visual-studio.md Add files via upload Delete class_library.png Add files via upload Delete class_library.png Add files via upload Update library-with-visual-studio.md Create use-library.png Delete build_succeeded.png Delete lib_project.png Delete new_project.png Delete string_library.png Create newproject.png Add files via upload Update library-with-visual-studio.md Update consuming-library-with-visual-studio.md Add files via upload Delete buildsucceeded.png Add files via upload Update library-with-visual-studio.md Update consuming-library-with-visual-studio.md Create debugmode.png Add files via upload Update debugging-with-visual-studio-2017.md Create toolbar1.png Add files via upload Update publishing-with-visual-studio-2017.md Delete publish2.png Delete toolbar1.png Add files via upload Update publishing-with-visual-studio-2017.md Update publishing-with-visual-studio-2017.md Create testproject.png Add files via upload Update testing-library-with-visual-studio.md Delete uittestwindow.png Add files via upload Update library-with-visual-studio.md Update consuming-library-with-visual-studio.md Update consuming-library-with-visual-studio.md Update consuming-library-with-visual-studio.md Update consuming-library-with-visual-studio.md Update consuming-library-with-visual-studio.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update debugging-with-visual-studio-2017.md Update consuming-library-with-visual-studio.md Update library-with-visual-studio.md Update publishing-with-visual-studio-2017.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update testing-library-with-visual-studio.md Update debugging-with-visual-studio-2017.md Update testing-library-with-visual-studio.md Update getting-started.md Update toc.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall. I'd agree with @mairaw that the Prev and Next buttons would be useful for readers. Adding them would be a good idea, but not a blocker to merging.
Fixes #1480
(Attempting a squashed commits version here.)
Notes
I'll remove the
WIP
label after the build runs and I fix any broken links.I'll ping when it's ready for a 👀 look 👀.