Skip to content

Porting date and time topics from MSDN #992

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

Merged
merged 9 commits into from
Sep 6, 2016
Merged

Conversation

stevehoag
Copy link
Contributor

Previously reviewed - closes #224

@BillWagner
Copy link
Member

testing close & reopen to trigger build.

@qinezh
Copy link
Contributor

qinezh commented Sep 1, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@mairaw
Copy link
Contributor

mairaw commented Sep 1, 2016

There's a bunch of warnings on the OPS build report. Our builds were clean this morning so probably this PR is introducing them. Once those are fixed, I can review this.

@qinezh
Copy link
Contributor

qinezh commented Sep 1, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@qinezh
Copy link
Contributor

qinezh commented Sep 1, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@qinezh
Copy link
Contributor

qinezh commented Sep 1, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@@ -18,7 +18,7 @@ Successfully working with a designated time zone requires that information about

## To enumerate the time zones present on the local system

1. Call the [TimeZoneInfo.GetSystemTimeZones](xref:System.TimeZoneInfo.GetSystemTimeZones) method. The method returns a generic [ReadOnlyCollection<T>](xref:System.Collections.ObjectModel.ReadOnlyCollection%601) collection of [TimeZoneInfo](xref:System.TimeZoneInfo) objects. The entries in the collection are sorted by their [DisplayName](xref:System.TimeZoneInfo.DisplayName) property. For example:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this link was correct. you cannot use the url of the API for xref links, you need to use the uid which is found here: https://github.com/docascode/coreapi/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so in this case, the uid is System.Collections.ObjectModel.ReadOnlyCollection`1. since you have a backtick, it needs to be encoded using %60.

@qinezh
Copy link
Contributor

qinezh commented Sep 2, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@qinezh
Copy link
Contributor

qinezh commented Sep 2, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@qinezh
Copy link
Contributor

qinezh commented Sep 2, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@stevehoag
Copy link
Contributor Author

@mairaw Build is clean and issues on stage resolved.


[Instantiating a DateTimeOffset Object](instantiating-a-datetimeoffset-object.md) - Discusses the ways in which a [System.DateTimeOffset](xref:System.DateTimeOffset) object can be instantiated, and the ways in which a [System.DateTime](xref:System.DateTime) value can be converted to a [System.DateTimeOffset](xref:System.DateTimeOffset) value.

[Performing Arithmetic Operations with Dates and Times]performing-arithmetic-operations.md) - Discusses the issues involved in adding, subtracting, and comparing [System.DateTime](xref:System.DateTime) and [System.DateTimeOffset](xref:System.DateTimeOffset) values.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this link is broken

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@mairaw
Copy link
Contributor

mairaw commented Sep 2, 2016

Did a quick review pass on stage and left some comments.

@qinezh
Copy link
Contributor

qinezh commented Sep 2, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@stevehoag
Copy link
Contributor Author

@mairaw Addressed issues - ready to merge?

@@ -1,6 +1,6 @@
---
title: How to: access the predefined UTC and local time zone objects
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We established as a pattern to enclose the title with quotes in these cases. See our style guide

@mairaw
Copy link
Contributor

mairaw commented Sep 2, 2016

Left one feedback about the metadata section. The rest of the changes looks good.

@qinezh
Copy link
Contributor

qinezh commented Sep 6, 2016

Open Publishing Build Service: The pull request content has been published and here are some sample preview links:

@stevehoag
Copy link
Contributor Author

@mairaw Fixed metadata in 6 files - good to go?

@mairaw
Copy link
Contributor

mairaw commented Sep 6, 2016

That was my only comment, everything else looked good.

@stevehoag stevehoag merged commit c40c28d into dotnet:master Sep 6, 2016
@stevehoag stevehoag deleted the port-doc3 branch September 6, 2016 17:56
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

Successfully merging this pull request may close these issues.

Porting .NET MSDN docs to Core - Date/Time
5 participants