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 README #24

Merged
merged 1 commit into from
May 20, 2015
Merged

Update README #24

merged 1 commit into from
May 20, 2015

Conversation

roncain
Copy link
Contributor

@roncain roncain commented May 20, 2015

No description provided.

@roncain
Copy link
Contributor Author

roncain commented May 20, 2015

cc: @richlander @martinwoodward @iamjasonp for feedback

@@ -51,7 +57,7 @@ The repo contains the following library components.

## License

Windows Communication Foundation (including the wcf repo) is licensed under the [MIT license](LICENSE).
This WCF repo is licensed under the [MIT license](LICENSE).
Copy link
Member

Choose a reason for hiding this comment

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

"This project is licensed..."

@martinwoodward
Copy link
Member

Overall, love these changes. Some minor nits but otherwise +1


The version of WCF in this repo runs on top of the [.NET Core](http://github.com/dotnet/core) platform, namely the [.NET Core Runtime (CoreCLR)](https://github.com/dotnet/coreclr) and [.NET Core Framework (CoreFx)](http://github.com/dotnet/corefx)
It's a subset of the .NET Framework version of Windows Communication Foundation and currently supports the same functionality available for Windows 8.1 Store apps. It is used to build .NET Core apps, including [Windows UWP](https://msdn.microsoft.com/en-us/library/windows/apps/dn609832.aspx) and [ASP.NET 5](http://weblogs.asp.net/scottgu/introducing-asp-net-5). These client libraries are suitable for mobile devices or on mid-tier servers to communicate with existing WCF services.
Copy link
Member

Choose a reason for hiding this comment

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

Consider "currently supports the same functionality..." -> "will support the same functionality" or "currently implements the same contract... " ?

I'm at a loss for words right now, but I want to say that we currently support the same contract as Windows Store 8.1 apps but the functionality is still work in progress.

@iamjasonp
Copy link
Member

👍 - really like the new updates.

@iamjasonp
Copy link
Member

Consider updating dotnet-foundation/foundation#23 with "WCF Client Libraries" once we have our name at the top of the README finalized.

@roncain
Copy link
Contributor Author

roncain commented May 20, 2015

Thanks for the suggestions. I've incorporated them in this update to the PR.


The version of WCF in this repo runs on top of the [.NET Core](http://github.com/dotnet/core) platform, namely the [.NET Core Runtime (CoreCLR)](https://github.com/dotnet/coreclr) and [.NET Core Framework (CoreFx)](http://github.com/dotnet/corefx)
It's a subset of the .NET Framework version of Windows Communication Foundation and currently supports the same API surface available for Windows 8.1 Store apps. It is used to build .NET Core apps, including [Windows UWP](https://msdn.microsoft.com/en-us/library/windows/apps/dn609832.aspx) and [ASP.NET 5](http://weblogs.asp.net/scottgu/introducing-asp-net-5). These client libraries are suitable for mobile devices or on mid-tier servers to communicate with existing WCF services.
Copy link
Member

Choose a reason for hiding this comment

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

👍 - "the same API surface" sounds great!

@iamjasonp
Copy link
Member

ACK. We are good to merge.

iamjasonp added a commit that referenced this pull request May 20, 2015
@iamjasonp iamjasonp merged commit 5651770 into dotnet:master May 20, 2015
@roncain roncain deleted the readmeupdate branch May 20, 2015 21:00
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.

4 participants