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

Update reference-connect-version-history.md #1408

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rui0122
Copy link
Contributor

@rui0122 rui0122 commented Mar 5, 2025

Modify from .Net runtime to .Net Framework. I confirmed with nualex for this modification.

Modify from .Net runtime to .Net Framework
Copy link
Contributor

@rui0122 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 06b660c:

💡 Validation status: suggestions

File Status Preview URL Details
docs/identity/hybrid/connect/reference-connect-version-history.md 💡Suggestion Details

docs/identity/hybrid/connect/reference-connect-version-history.md

  • Line 120, Column 88: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /sql/connect/oledb/release-notes-for-oledb-driver-for-sql-server?view=sql-server-ver16#1874

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Mar 6, 2025

@billmath

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

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

Successfully merging this pull request may close these issues.

3 participants