Skip to content

Adding C# version history post - #2867

Merged
BillWagner merged 10 commits into
dotnet:masterfrom
erikdietrich:master
Sep 20, 2017
Merged

BillWagner merged 10 commits into
dotnet:masterfrom
erikdietrich:master

Conversation

@erikdietrich

Copy link
Copy Markdown
Contributor

Per Bill Wagner's request over email, we're adding the C# Version History blog post from NDepend to the documentation.

@dnfclas

dnfclas commented Aug 9, 2017

Copy link
Copy Markdown

@erikdietrich,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.

It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@dnfclas

dnfclas commented Aug 9, 2017

Copy link
Copy Markdown

@erikdietrich, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.

Thanks, .NET Foundation Pull Request Bot

1. Add Metadata
1. Change person
1. Formalize from blog post to docs style language.
@BillWagner

Copy link
Copy Markdown
Member

I made a pass at tightening the language to match the structure of docs.

@mairaw Do you want to take a look?

@erikdietrich I tried to stay honest to your original intent while following our guidelines. If any of the edits are a concern, let me know, or push an update.

@erikdietrich

Copy link
Copy Markdown
Contributor Author

@BillWagner Looks good to me -- no issues here.

@mairaw

mairaw commented Sep 9, 2017

Copy link
Copy Markdown
Contributor

Sorry, I've missed this earlier. I'll get this reviewed soon. Apologies on the delay.

I've just resolved the merge conflicts we had.

@lextm

lextm commented Sep 10, 2017

Copy link
Copy Markdown

If the content can include some reference to Visual J++ and its extensions of Java, then the history would be more naturally showing the transition to C#. The discontinuation of J++ and the birth of C# are associated with each other.

@mairaw mairaw left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Really nice @erikdietrich! Thanks so much.

@BillWagner please let me know if I went too far on trying to bring this in to our style. I'm happy to help to incorporate my suggestions if needed. Please let me know.

ms.devlang: csharp
---

# The History of C# #

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: title and headings should have sentence case, not title case such as "The history of C#"


## C# Version 1

When you go back and look, C# version 1 really did look an awful lot like Java. As [part of its stated design goals for ECMA](http://feeldotneteasy.blogspot.com/2011/01/c-design-goals.html), it sought to be a "simple, modern, general purpose object-oriented language." At the time, it could have done worse thank looking like Java in order to achieve those goals.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

  1. really did look an awful lot like Java -> this is very informal. Suggestion:
    "C# 1 looked a lot like Java"

  2. " -> change to the actual quote? same for other characters that are encoded throughout the topic

  3. thank -> than

  4. what is the intent of the last sentence? that looking like Java wasn't so bad after all? I find it hard to read.


What did the language look like in its earliest incarnations? And how has it evolved in the years since?

## C# Version 1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it would be good to standardize on the way we'd call the versions. C# version 1 or C# 1 or C# 1.0?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

updated to 1.0, etc. Now that we do point releases.


When you go back and look, C# version 1 really did look an awful lot like Java. As [part of its stated design goals for ECMA](http://feeldotneteasy.blogspot.com/2011/01/c-design-goals.html), it sought to be a "simple, modern, general purpose object-oriented language." At the time, it could have done worse thank looking like Java in order to achieve those goals.

But if you looked back on C# 1.0 now, you'd find yourself a little dizzy. It lacked the built in async capabilities and some of the slick functionality around generics that we take for granted. As a matter of fact, it lacked generics altogether. And [Linq](https://msdn.microsoft.com/en-us/library/bb308959.aspx)? Nope. That would take some years to come out.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

  1. looked back -> look back

  2. built in -> built-in

  3. for the msdn linq, perhaps we should link to something internal like https://docs.microsoft.com/en-us/dotnet/csharp/linq/.

  4. Linq -> LINQ

  5. Nope -> very informal


Now things start to get interesting. Let's take a look at some major features of C# 2.0, released in 2005, along with Visual Studio 2005.

- [Generics](https://www.tutorialspoint.com/csharp/csharp_generics.htm)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ideally we'd link to existing topic on docs such as https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/


With versions 3 and 5, C# had added some pretty impressive stuff in an OO language. (Version 2 did as well, but it was fast following Java with those language features.) With version 6, it would go away from doing a dominant killer feature and instead release a lot of features that delighted users of the language. Here are some of them.

- [Static imports (a la Java)](http://geekswithblogs.net/BlackRabbitCoder/archive/2015/04/16/c.net-little-wonders-static-using-statements-in-c-6.aspx)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

a la Java -> we avoid non english terms in our topics. Perhaps replace it with like? or remove that completely?


Taken individually, these are all cool language features. But if you look at them altogether, you see an interesting pattern. In this version, C# eliminated language boilerplate to make code more terse and readable. So for fans of clean, simple code, this language version was a huge win.

Oh, and they did do one other thing along with this version, though it's not a traditional language feature, per se. They released [Roslyn the compiler as a service](https://github.com/dotnet/roslyn). C# now uses C# to build C#, and they let you use the compiler as part of your programming efforts.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

remove Oh

they did do -> they did

per se -> in itself?

- [Expanded expression bodied members](https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-7#more-expression-bodied-members)
- [Ref locals and returns](https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-7#ref-locals-and-returns)

All of these offer cool new capabilities for developers and the opportunity to write even cleaner code than ever. A highlight is condensing the declaration of variables to use with the `out` keyword and by allowing multiple return values via tuple.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

All of these -> All of these features

ms.author: wiwagn
ms.date: 2017/08/09
ms.topic: article
ms.prod: visual-studio-dev-15

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ms.prod should be .net

keywords: C#, .NET, .NET Core, What's New, C# History
author: erikdietrich
ms.author: wiwagn
ms.date: 2017/08/09

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

date format is mm/dd/yyyy. otherwise weird things happen 😄

image

@BillWagner

Copy link
Copy Markdown
Member

@mairaw Thanks for the review. I'll update it today.

@BillWagner

Copy link
Copy Markdown
Member

@mairaw Updates in place.

@mairaw

mairaw commented Sep 13, 2017

Copy link
Copy Markdown
Contributor

I'll go through this PR now but build has some warnings. Wanna take a look @BillWagner?

@mairaw mairaw closed this Sep 14, 2017
@mairaw mairaw reopened this Sep 14, 2017
@dnfclas

dnfclas commented Sep 14, 2017

Copy link
Copy Markdown

@erikdietrich,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@JRAlexander JRAlexander added the ✨ 1st-time docs contributor! Indicates PRs from new contributors to the docs repository label Sep 19, 2017

With generics, you have types and methods that can operate on an arbitrary type while still retaining type safety. So, for instance, having a <xref:System.Collections.Generic.List%601> lets you have `List<string>` or `List<int>` and perform type safe operations on those strings or integers while you iterate through them. This is better than creating `ListInt` inheritors or casting from `Object` for every operation.

C# Version 2.0 brought iterators. To put it succinctly, this lets you iterate through the items in a `List` (or other Enumerable types) with a `foreach` loop. Having this as a first class part of the language dramatically enhanced readability of the language and people's ability to reason about the code.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: first class -> first-class

- [Iterators](https://msdn.microsoft.com/en-us/library/65zzykke(v=vs.100).aspx)
- [Covariance and contravariance](../programming-guide/concepts/covariance-contravariance/)

While C# may have started as a pretty generic Object-Oriented (OO) language, C# Version 2.0 changed that in a hurry. Once they had their feet under them, they went after some serious developer pain points. And they went after them in a big way.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

can we change C# Version to C# version where version is capitalized?


## C# version 3.0

C# Version 3.0 came in late 2007, along with Visual Studio 2008, though the full boat of language features would actually come with C# Version 3.5. This version marked a major change in the growth of C#. It established C# as a truly formidable programming language. Let's take a look at some major features in this version.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: should we introduce these lists with a sentence ending in :?


In retrospect, many of these features seem both inevitable and inseparable. They all fit together strategically. It's generally thought that C# version's killer feature was the query expression, also known as Language-Integrated Query (LINQ).

A more nuanced view examines expression tress, lambda expressions, and anonymous types as the foundation upon which LINQ is constructed. But, in either case, C# 3.0 presented with a fairly revolutionary concept. C# 3.0 had begun to lay the groundwork for turning C# into a hybrid Object Oriented / Functional language.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

presented with -> presented

remove fairly?


A more nuanced view examines expression tress, lambda expressions, and anonymous types as the foundation upon which LINQ is constructed. But, in either case, C# 3.0 presented with a fairly revolutionary concept. C# 3.0 had begun to lay the groundwork for turning C# into a hybrid Object Oriented / Functional language.

Specifically, you could now write SQL-style, declarative queries to perform operations on collections, among other things. Instead of writing a `for` loop to compute the average of a list of integers, you could now do that as simply as `list.Average()`. The combination of query expressions and extension methods made it look as though that list of ints had gotten a whole lot smarter.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

list of ints -> list of integers?

Now things start to get interesting. Let's take a look at some major features of C# 2.0, released in 2005, along with Visual Studio 2005.

- [Generics](../programming-guide/generics/)
- [Partial types](https://www.dotnetperls.com/partial)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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


- [Generics](../programming-guide/generics/)
- [Partial types](https://www.dotnetperls.com/partial)
- [Anonymous methods](https://www.tutorialspoint.com/csharp/csharp_anonymous_methods.htm)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

C# Version 3.0 came in late 2007, along with Visual Studio 2008, though the full boat of language features would actually come with C# Version 3.5. This version marked a major change in the growth of C#. It established C# as a truly formidable programming language. Let's take a look at some major features in this version.

- [Auto implemented properties](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/auto-implemented-properties)
- [Anonymous types](http://www.c-sharpcorner.com/UploadFile/ff2f08/anonymous-types-in-C-Sharp/)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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


C# Version 5.0 was a very focused version of the language. Nearly all of the effort for that version went into another groundbreaking language concept. Here is the major features list.

- [Asynchronous members](https://msdn.microsoft.com/library/hh191443(vs.110).aspx)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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


With versions 3.0 and 5.0, C# had added some impressive features in an Object Oriented language. (Version 2.0 did as well, but it was fast following Java with those language features.) With version 6.0, it would go away from doing a dominant killer feature and instead release many features that delighted users of the language. Here are some of them.

- [Static imports](http://geekswithblogs.net/BlackRabbitCoder/archive/2015/04/16/c.net-little-wonders-static-using-statements-in-c-6.aspx)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@mairaw

mairaw commented Sep 19, 2017

Copy link
Copy Markdown
Contributor

@BillWagner let me know if you'd like me to work on these updates for you. Thanks!

@BillWagner

Copy link
Copy Markdown
Member

@mairaw I just edited and responded to all the feedback.

@BillWagner
BillWagner merged commit 7b7b3ed into dotnet:master Sep 20, 2017
rpetrusha pushed a commit that referenced this pull request Sep 20, 2017
* fix constructor remarks formatting. (#3141)

* fix constructor remarks formatting.

* another instance

* Update String.xml

* Update String.xml

* &#124; didn't render to `|` properly (#3162)

* Added missing space between two words (#3161)

* M10669: Possible typo mistake: 'SC1721' (#3167)

@wiwagn,
It seems that 'SC1721' is a typo of 'CS1721'. Could you help to review this and reply, please?
Many thanks in advance!

* Update sample code for documentation VB.NET "what's new : language features : Tuples" (#3166)

* what's new Tuples : sample use InvariantCulture

* vb tuple example fix new language feature sample

* fixed broken link (#3169)

* fixed pipes in tables (#3163)

* added info about relative paths for output (#3042)

* added info about relative paths for output

* edits

* Update how-to-write-a-simple-parallel-for-loop.md (#3174)

Updated Cut to Copy in Copy/Cut and Paste this code into ...

* fixed formulas (#3182)

* fixed formulas

* fixed formula

* fixed formula

* simplifying version list (#3176)

* Minor fixes : inconsistent wording and some ghost characters (#3171)

* what's new Tuples : sample use InvariantCulture

* vb tuple example fix new language feature sample

* minor typos

* compiler warning corrected to match previously mentioned number
* removed a "ghost" quote

* fixed inconsistent "read-only" and "read only"

* code formatting (missing space)

* Adding C# version history post (#2867)

* Create csharp-version-history.md

* Added the actual text

* Updated TOC with my entry.

* first pass edit

1. Add Metadata
1. Change person
1. Formalize from blog post to docs style language.

* Update csharp-version-history.md

* fix build warnings on links.

* respond to feedback

* fixed build warnings

* fixed version capitalization
OPSTestPPE referenced this pull request in OPS-E2E-PPE/docs Sep 22, 2017
* fixed broken link (#3169)

* fixed pipes in tables (#3163)

* added info about relative paths for output (#3042)

* added info about relative paths for output

* edits

* Update how-to-write-a-simple-parallel-for-loop.md (#3174)

Updated Cut to Copy in Copy/Cut and Paste this code into ...

* fixed formulas (#3182)

* fixed formulas

* fixed formula

* fixed formula

* simplifying version list (#3176)

* Minor fixes : inconsistent wording and some ghost characters (#3171)

* what's new Tuples : sample use InvariantCulture

* vb tuple example fix new language feature sample

* minor typos

* compiler warning corrected to match previously mentioned number
* removed a "ghost" quote

* fixed inconsistent "read-only" and "read only"

* code formatting (missing space)

* Adding C# version history post (#2867)

* Create csharp-version-history.md

* Added the actual text

* Updated TOC with my entry.

* first pass edit

1. Add Metadata
1. Change person
1. Formalize from blog post to docs style language.

* Update csharp-version-history.md

* fix build warnings on links.

* respond to feedback

* fixed build warnings

* fixed version capitalization

* Learn C# Tutorial (#2306)

* First draft of new tutorial

Learn the structure of a C# program, and  explore the string class.

proofread and tighten language.

respond to feedback

2nd draft

Move more code earlier.
Tighten vocabulary discussions.

Update outline

start on the next draft.

add section on searching strings

fix build errors

finish the string tutorial.

reorder: ready for proofread.

proofread

update to use new syntax

Update Tutorial to use the new engine

typo in the title

* build test, try samples

* 2nd draft of the numbers tutorial.

* proofread the second tutorial and create the third

Branching and looping is ready for initial review.

* respond to feedback on first tutorial.

* proof read 3rd tutorial

And add links to other C# Guide content

* Remove links to upcoming tutorials.

* Respond to feedback.

* fix yaml parsing error.

* More feedback.

* feedback from team review

Configure ms.technology for all quick starts to be
devlang-csharp-interactive.
Update .NET home page and C# Guide home page to point to the
interactive tutorials.

* Describe booleans, and update metadata.

* add a tip about compiler messages

* update timings of tutorials, update tip text

* final review.

* Fix typo: AesCrytpServiceProvider -> AesCryptoServiceProvider (#3185)

* Fix typo: AesCrytpServiceProvider -> AesCryptoServiceProvider

* Fix typo: crytopgraphy -> cryptography

* added net core behavior (#3140)

* added net core behavior

* feedback

* feedback

* feedback

* quick link fix to the hub page (#3193)

The link target was updated for the Quick Starts, but the displayed
text was not.

* Removed duplicate entry from 'See Also' section (#3195)

* removed invisible characters (#3192)

* update snippet reference (#3191)

* fixed broken link (#3190)

* clarified example (#3184)

* Updating condition(s) under which the method throws (#3152)

* Updating condition(s) under which the method throws

* Correcting a few hard-to-localize bits of content

* Update mutually recursive functions snippet (#3186)

* Update mutually recursive functions snippet

Correct implementation should be something like (this one)[https://en.wikipedia.org/wiki/Mutual_recursion]

* Typo fix in function name

Event -> Even

* 494407 Corrections to DnsSafeHost and IdnHost (#3143)

* 494407 Corrections to DnsSafeHost and IdnHost

* Actioning all comments :)

* I used the wrong inline code delimiter

* Improve Suits and Ranks definitions (#3197)

* update target framework to 2.0

* Improve Suits and Ranks enumerable definitions

* Revert "update target framework to 2.0"

This reverts commit 008d19d.

* Fixed Kelvin output, make culture independent (#3157)

* Fixed Kelvin output, make culture independent

- Fixed wrong expected output for Kelvin in the sample usage
- Defined current culture in the sample usage to work out-of-the-box for international locales

* Remove obsolete full qualified name

* CurrentThread.CurrentCulture -> CultureInfo.CurrentCulture

* Fixed Kelvin output, make culture independent (#3159)

* Fixed Kelvin output, make culture independent

- Fixed wrong expected output for Kelvin in the sample usage
- Defined current culture in the sample usage to work out-of-the-box for international locales

* Remove obsolete full qualified name

* CurrentThread.CurrentCulture -> CultureInfo.CurrentCulture

* Remove Duplicate Config Definition (#3200)

For whatever reason, the sample XML was duplicated -- this commit removes that duplication so that the example is more readable.

* fixed api link format (#3194)

* Typo in document - IOne instead of One (#3202)

Typo in document - IOne instead of One

* Fix framework in dotnet store command topic (#3188)

Reported by @pauliusnorkus. Thanks to @dasMulli for reminding me about the framework problem here. Using `netstandard2.0` worked during pre-release but no more.
OPSTestPPE referenced this pull request in OPS-E2E-PPE/docs Sep 22, 2017
* fixed broken link (#3169)

* fixed pipes in tables (#3163)

* added info about relative paths for output (#3042)

* added info about relative paths for output

* edits

* Update how-to-write-a-simple-parallel-for-loop.md (#3174)

Updated Cut to Copy in Copy/Cut and Paste this code into ...

* fixed formulas (#3182)

* fixed formulas

* fixed formula

* fixed formula

* simplifying version list (#3176)

* Minor fixes : inconsistent wording and some ghost characters (#3171)

* what's new Tuples : sample use InvariantCulture

* vb tuple example fix new language feature sample

* minor typos

* compiler warning corrected to match previously mentioned number
* removed a "ghost" quote

* fixed inconsistent "read-only" and "read only"

* code formatting (missing space)

* Adding C# version history post (#2867)

* Create csharp-version-history.md

* Added the actual text

* Updated TOC with my entry.

* first pass edit

1. Add Metadata
1. Change person
1. Formalize from blog post to docs style language.

* Update csharp-version-history.md

* fix build warnings on links.

* respond to feedback

* fixed build warnings

* fixed version capitalization

* Learn C# Tutorial (#2306)

* First draft of new tutorial

Learn the structure of a C# program, and  explore the string class.

proofread and tighten language.

respond to feedback

2nd draft

Move more code earlier.
Tighten vocabulary discussions.

Update outline

start on the next draft.

add section on searching strings

fix build errors

finish the string tutorial.

reorder: ready for proofread.

proofread

update to use new syntax

Update Tutorial to use the new engine

typo in the title

* build test, try samples

* 2nd draft of the numbers tutorial.

* proofread the second tutorial and create the third

Branching and looping is ready for initial review.

* respond to feedback on first tutorial.

* proof read 3rd tutorial

And add links to other C# Guide content

* Remove links to upcoming tutorials.

* Respond to feedback.

* fix yaml parsing error.

* More feedback.

* feedback from team review

Configure ms.technology for all quick starts to be
devlang-csharp-interactive.
Update .NET home page and C# Guide home page to point to the
interactive tutorials.

* Describe booleans, and update metadata.

* add a tip about compiler messages

* update timings of tutorials, update tip text

* final review.

* Fix typo: AesCrytpServiceProvider -> AesCryptoServiceProvider (#3185)

* Fix typo: AesCrytpServiceProvider -> AesCryptoServiceProvider

* Fix typo: crytopgraphy -> cryptography

* added net core behavior (#3140)

* added net core behavior

* feedback

* feedback

* feedback

* quick link fix to the hub page (#3193)

The link target was updated for the Quick Starts, but the displayed
text was not.

* Removed duplicate entry from 'See Also' section (#3195)

* removed invisible characters (#3192)

* update snippet reference (#3191)

* fixed broken link (#3190)

* clarified example (#3184)

* Updating condition(s) under which the method throws (#3152)

* Updating condition(s) under which the method throws

* Correcting a few hard-to-localize bits of content

* Update mutually recursive functions snippet (#3186)

* Update mutually recursive functions snippet

Correct implementation should be something like (this one)[https://en.wikipedia.org/wiki/Mutual_recursion]

* Typo fix in function name

Event -> Even

* 494407 Corrections to DnsSafeHost and IdnHost (#3143)

* 494407 Corrections to DnsSafeHost and IdnHost

* Actioning all comments :)

* I used the wrong inline code delimiter

* Improve Suits and Ranks definitions (#3197)

* update target framework to 2.0

* Improve Suits and Ranks enumerable definitions

* Revert "update target framework to 2.0"

This reverts commit 008d19d.

* Fixed Kelvin output, make culture independent (#3157)

* Fixed Kelvin output, make culture independent

- Fixed wrong expected output for Kelvin in the sample usage
- Defined current culture in the sample usage to work out-of-the-box for international locales

* Remove obsolete full qualified name

* CurrentThread.CurrentCulture -> CultureInfo.CurrentCulture

* Fixed Kelvin output, make culture independent (#3159)

* Fixed Kelvin output, make culture independent

- Fixed wrong expected output for Kelvin in the sample usage
- Defined current culture in the sample usage to work out-of-the-box for international locales

* Remove obsolete full qualified name

* CurrentThread.CurrentCulture -> CultureInfo.CurrentCulture

* Remove Duplicate Config Definition (#3200)

For whatever reason, the sample XML was duplicated -- this commit removes that duplication so that the example is more readable.

* fixed api link format (#3194)

* Typo in document - IOne instead of One (#3202)

Typo in document - IOne instead of One

* Fix framework in dotnet store command topic (#3188)

Reported by @pauliusnorkus. Thanks to @dasMulli for reminding me about the framework problem here. Using `netstandard2.0` worked during pre-release but no more.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✨ 1st-time docs contributor! Indicates PRs from new contributors to the docs repository

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants