Initial documentation for additional tools #3871

mlacouture · 2017-12-04T23:19:53Z

Title

Documentation for .net core additional tools.

Summary

This section is meant to compile information about tools in addition to CLI tools.

Internal Review URL(index.md)
Internal Review URL(wcf-web-service-reference-guide.md)
Internal Review URL(xml-serializer-generator.md)

Suggested Reviewers

@zhenlan

shmao · 2017-12-05T00:42:08Z

docs/core/additional-tools/WCF-Web-Service-Reference-guide.md

@@ -0,0 +1,51 @@
+## Microsoft WCF Web Service Reference Provider
+
+Over the years, many Visual Studio developers have enjoyed the productivity that Add Service Reference provides when their .NET Framework projects needed to access Windows Communication Foundation (WCF) services. The WCF team is excited to introduce the WCF Connected Service for .NET Core and ASP.NET Core, a VS extension providing an experience like the Add Service Reference functionality. This tool retrieves metadata from a WCF service in the current solution, locally or on a network, and generates a .NET Core compatible source code file for a WCF client proxy that you can use to access the service.


... that Add Service Reference provides when their .NET Framework projects needed to ...

It seems to me that either provides should be provided or needed should be need.

This tool retrieves metadata from a WCF service in the current solution, locally or on a network...

This sentence doesn't sound right.

Yeah, maybe something like "This tool retrieves metadata from a WCF service in the current solution, a WSDL file at the local disk or a web service on a network...".

fixed the 'locally' part, the rest is OK.

shmao · 2017-12-05T00:47:30Z

docs/core/additional-tools/WCF-Web-Service-Reference-guide.md

+
+### How to use the extension
+
+The WCF Web Service Reference VS connected service extension is applicable to projects created using the templates under Visual C# -> .Net Core, Visual C# -> .Net Standard and Visual C# -> Web -> ASP.NET CORE Web Application projects.


Visual C# -> .Net Standard and Visual C#

Add a , before and, e.g.,

Visual C# -> .Net Standard, and Visual C#

ASP.NET CORE should be ASP.NET Core

Fixed the 'CORE' part, the rest is OK - thank you!

and .NET is spelled all caps

zhenlan · 2017-12-06T20:45:09Z

docs/core/additional-tools/wcf_web_service_reference-guide.md

+
+Over the years, many Visual Studio developers have enjoyed the productivity that the [Add Service Reference](https://msdn.microsoft.com/en-us/library/bb386382.aspx) tool provided when their .NET Framework projects needed to access Windows Communication Foundation (WCF) services. The WCF team is excited to introduce the **WCF Web Service Reference** tool, a Visual Studio connected service extension providing an experience like the Add Service Reference functionality for .NET Core and ASP.NET Core projects. This tool retrieves metadata from a WCF service in the current solution, from a WSDL file or on a network location, and generates a .NET Core compatible source file containing WCF client proxy code that you can use to access the web service.
+
+> [!!IMPORTANT]


Two !s may mean it's very important but not sure if it will work ;-)

mairaw

Thanks @mlacouture! Finally managed to sit down and review this. Let us know if we can help with the edits.

mairaw · 2017-12-11T21:05:15Z

docs/core/additional-tools/index.md

@@ -0,0 +1,19 @@
+---
+title: .NET Core Additional Tools


use sentence case for title and headings. So it should be .NET Core additional tools

mairaw · 2017-12-11T21:05:44Z

docs/core/additional-tools/index.md

@@ -0,0 +1,19 @@
+---
+title: .NET Core Additional Tools
+description: An overview of the additional tools that support and extend .Net Core functionality.


here and in other places on this PR: .NET needs to be all capital

mairaw · 2017-12-11T21:06:06Z

docs/core/additional-tools/index.md

+---
+title: .NET Core Additional Tools
+description: An overview of the additional tools that support and extend .Net Core functionality.
+author: miguell


your GH alias is mlacouture, so you should this here

mairaw · 2017-12-11T21:06:33Z

docs/core/additional-tools/index.md

+title: .NET Core Additional Tools
+description: An overview of the additional tools that support and extend .Net Core functionality.
+author: miguell
+ms.author: miguell


put mairaw here so I'm responsible for keeping up with feedback, etc.

Do you want me to change this to johalex instead?

mairaw · 2017-12-11T21:07:16Z

docs/core/additional-tools/index.md

+ms.date: 12/04/2017
+ms.topic: article
+ms.prod: .net-core
+ms.technology: .net-core tools.


remove this line. we don't have a specific entry on our BI reports for this yet, so let's keep it blank for now

mairaw · 2017-12-11T22:08:22Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+    ```
+    dotnet new console --name MyApp
+    ```
+1. Edit the .csproj and add a reference to the Microsoft.XmlSerializer.Generator package. For example,


choose one way of doing it. since you're already on CLI, continue to use the CLI.

You can then tell them they can open the project file and see that the following lines were added.

Something like:

Add a reference to the Microsoft.XmlSerializer.Generator package:

dotnet add package Microsoft.XmlSerializer.Generator -v 1.0.0-preview1-25915-02

After running the command, the following lines are added to your project file:

<ItemGroup> <DotNetCliToolReference Include="Microsoft.XmlSerializer.Generator" Version="1.0.0-preview1-25915-02" /> </ItemGroup>

mairaw · 2017-12-11T22:08:42Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+        public int Value;
+    }
+    ```    
+    Now you can create an `XmlSerializer` for MyClass.    


mairaw · 2017-12-11T22:09:50Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+    ```c#
+    var serializer = new System.Xml.Serialization.XmlSerializer(typeof(MyClass));
+    ```    
+1. Build the application by running `dotnet build`. If everything succeeds, an assembly named MyApp.XmlSerializers.dll will be generated in the output folder. You will see warnings in the build output if the tool failed to generate the assembly.


everything -> build

will be -> is

remove last sentence

mairaw · 2017-12-11T22:11:59Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+    ```    
+1. Build the application by running `dotnet build`. If everything succeeds, an assembly named MyApp.XmlSerializers.dll will be generated in the output folder. You will see warnings in the build output if the tool failed to generate the assembly.
+
+Start the application and it will automatically load and use the pre-generated serializers at runtime.


how do you start the application?

it will automatically load and use -> It automatically loads and uses

Start the application by running dotnet run from the project folder ..

mairaw · 2017-12-11T22:13:52Z

docs/toc.md

@@ -114,6 +114,7 @@
 ## [Runtime IDentifier catalog](core/rid-catalog.md)
 ## [.NET Core SDK Overview](core/sdk.md)
 ## [.NET Core CLI Tools](core/tools/index.md)
+## [.NET Core Additional Tools](core/additional-tools/index.md)


this should be moved to line 149 before the Porting from .NET Framework entry

the other two new topics should be under this toc entry with the ###

JRAlexander · 2017-12-11T20:07:18Z

docs/core/additional-tools/index.md

+ms.technology: .net-core tools.
+---
+# .NET Core additional tools
+This section compiles a list of tools that support and extend the .Net Core functionality, in addition to the [.NET Core command-line interface (CLI)](..\tools\index.md) tools.


.Net should be .NET

JRAlexander · 2017-12-11T20:07:39Z

docs/core/additional-tools/index.md

+
+
+### [WCF Web Service Reference](wcf_web_service_reference-guide.md)
+The WCF Web Service Reference is a Visual Studio connected service provider which made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#WCFTools). Similarly to the Add Service Reference tool for classic .Net Framework VS projects, it allows for generating a web service reference containing proxy code that makes it easier for a client to consume the web service's functionality.


.Net should be .NET

You might revise with something like: "The WCF Web Service Reference Tool generates a web service reference containing proxy code for a client to easily consume the web service's functionality, similar to the Add Service Reference tool for classic .NET Framework VS project."

JRAlexander · 2017-12-11T21:23:31Z

docs/core/additional-tools/index.md

+This section compiles a list of tools that support and extend the .Net Core functionality, in addition to the [.NET Core command-line interface (CLI)](..\tools\index.md) tools.
+
+
+### [WCF Web Service Reference](wcf_web_service_reference-guide.md)


Should Tool be included?

Added the recommended changes from the reviewers for this file.

Update based on review feedback and rename wcf_web_service_reference-guide.md to wcf-web-service-reference-guide.md

Update based on review feedback and format tutorial

svick · 2017-12-26T21:53:57Z

docs/core/additional-tools/index.md

+The WCF Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#WCFTools). The WCF Web Service Reference Tool generates a web service reference containing proxy code for a client to easily consume the web service's functionality, similar to the Add Service Reference tool for .NET Framework Visual Studio projects.
+
+### [XML Serializer Generator](xmlserializergenerator-instructions.md)
+Like the [Xml Serializer Generator (sgen.exe)](https://docs.microsoft.com/en-us/dotnet/standard/serialization/xml-serializer-generator-tool-sgen-exe) for .NET Framework, <xref:System.Xml.Serialization.XmlSerializer> NuGet package is the solution for .NET Core and .NET Standard Libraries. It creates an XML serialization assembly for types contained in an assembly to improve the startup performance of XML serialization when serializing or de-serializing objects of those types using XmlSerializer. 


System.Xml.Serialization.XmlSerializer is not a package, it's a class.

The article talks about the Microsoft.XmlSerializer.Generator package, is that what should be mentioned here? (And I think you can't have an xref to a package.)

Yes, good catch.

svick · 2017-12-26T22:07:08Z

docs/core/additional-tools/index.md

+# .NET Core additional tools
+This section compiles a list of tools that support and extend the .NET Core functionality, in addition to the [.NET Core command-line interface (CLI)](..\tools\index.md) tools.
+
+### [WCF Web Service Reference Tool](wcf_web_service_reference-guide.md)


Is this link correct? The link is to wcf_web_service_reference-guide.md, but the actual file name is wcf-web-service-reference-guide.md.

The file has been renamed since the link was added.

svick · 2017-12-26T22:13:27Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+> The **WCF Web Service Reference** option is applicable to projects created using the following project templates:
+ * **Visual C#** > **.NET Core**, 
+ * **Visual C#** > **.NET Standard**
+ * **Visual C#** > **Web** > **ASP.NET Core Web Application** .


I think the formatting here is incorrect: the list will be formatted outside the note. To make it show inside, the items in the list should also start with a >:

> [!NOTE] > The **WCF Web Service Reference** option is applicable to projects created using the following project templates: > * **Visual C#** > **.NET Core**, > * **Visual C#** > **.NET Standard**, > * **Visual C#** > **Web** > **ASP.NET Core Web Application** .

Also, the items should either form a sentence (which means adding a comma to the second item) or not (which means removing the comma from the first item and removing the period from the third item).

svick · 2017-12-26T22:16:14Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+ * **Visual C#** > **.NET Standard**
+ * **Visual C#** > **Web** > **ASP.NET Core Web Application** .
+
+Using the **ASP.NET Core Web Application** project template as an example, This article walks you through adding a WCF service reference to the project:


This -> this

svick · 2017-12-26T22:18:37Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+4. The **Data Type Options** form enables you to refine the generated service reference configuration settings. 
+
+> [!NOTE]
+> The**Reuse types in referenced assemblies** check box option is useful when data types needed for service reference code generation are defined in one of your project's referenced assemblies.  It's important to reuse those existing data types to avoid compile-time type clash or runtime issues.


Missing space before **Reuse.

svick · 2017-12-27T00:25:01Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+public class MyClass
+ {
+    public int Value;
+ }


Nit: the code looks weird with the braces indented.

Indents are gone.

svick · 2017-12-27T00:25:55Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+
+### Build and run the application
+
+Still within the *myApp* folder, run the application via [`dotnet run`](../tools/dotnet-run.md)  and it will automatically load and use the pre-generated serializers at runtime.


Nit: myApp -> MyApp

svick · 2017-12-27T00:27:00Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+
+If everything succeeds, an assembly named *MyApp.XmlSerializers.dll* is generated in the output folder. 
+
+Congratulations! you have just:


svick · 2017-12-27T00:27:14Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+
+Congratulations! you have just:
+> [!div class="checklist"]
+> * Create a .NET Core app.


Create -> Created

svick · 2017-12-27T00:27:43Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+> * Added a reference to the Microsoft.XmlSerializer.Generator package
+> * Edited your MyApp.csproj to add dependencies.
+> * Added a class and an XmlSerializer
+> * Built and ran the application 


Some of the list items are missing a period.

* Updated Note formatting * Fixed capitalization * added space before **Reuse * Update the project file moved to new line

Removed the words "nuget package" from the introduction paragraph.

Corrected and asdded needed entries for TOC

mairaw

It's coming together nicely. A few extra comments 😃

mairaw · 2018-01-09T19:18:06Z

docs/toc.md

@@ -146,6 +146,9 @@
 ##### [dotnet add package](core/tools/dotnet-add-package.md)
 ##### [dotnet remove package](core/tools/dotnet-remove-package.md)
 ### [global.json](core/tools/global-json.md)
+## [.NET Core Additional Tools](core/additional-tools/index.md)
+### [Microsoft WCF Web Service Reference Provider Tool](core/additional-tools/wcf-web-service-reference-guide.md)


nit: I'd probably cut Microsoft and Tool from the TOC

mairaw · 2018-01-09T19:18:34Z

docs/toc.md

@@ -146,6 +146,9 @@
 ##### [dotnet add package](core/tools/dotnet-add-package.md)
 ##### [dotnet remove package](core/tools/dotnet-remove-package.md)
 ### [global.json](core/tools/global-json.md)
+## [.NET Core Additional Tools](core/additional-tools/index.md)
+### [Microsoft WCF Web Service Reference Provider Tool](core/additional-tools/wcf-web-service-reference-guide.md)
+### [Using Microsoft XML Serializer Generator on .NET Core](core/additional-tools/xmlserializergenerator-instructions.md)


nit: I'd cut Using Microsoft and on .NET Core from the TOC

mairaw · 2018-01-09T19:20:49Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+---
+# Microsoft WCF Web Service Reference Provider Tool
+
+Over the years, many Visual Studio developers have enjoyed the productivity that the [Add Service Reference](https://docs.microsoft.com/en-us/visualstudio/data-tools/how-to-add-update-or-remove-a-wcf-data-service-reference) tool provided when their .NET Framework projects needed to access Windows Communication Foundation (WCF) services. The **WCF Web Service Reference** tool is a Visual Studio connected service extension that provides an experience like the Add Service Reference functionality for .NET Core and ASP.NET Core projects. This tool retrieves metadata from a WCF service in the current solution, from a WSDL file or on a network location, and generates a .NET Core compatible source file containing WCF client proxy code that you can use to access the web service.


nit: bold the second Add Service Reference since it's an UI option

remove https://docs.microsoft.com/en-us from the link

mairaw · 2018-01-09T19:41:31Z

docs/core/additional-tools/index.md

+The WCF Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#WCFTools). The WCF Web Service Reference Tool generates a web service reference containing proxy code for a client to easily consume the web service's functionality, similar to the Add Service Reference tool for .NET Framework Visual Studio projects.
+
+### [XML Serializer Generator](xmlserializergenerator-instructions.md)
+Like the [Xml Serializer Generator (sgen.exe)](https://docs.microsoft.com/en-us/dotnet/standard/serialization/xml-serializer-generator-tool-sgen-exe) for .NET Framework, <xref:System.Xml.Serialization.XmlSerializer> is the solution for .NET Core and .NET Standard Libraries. It creates an XML serialization assembly for types contained in an assembly to improve the startup performance of XML serialization when serializing or de-serializing objects of those types using XmlSerializer. 


relative path instead of absolute URL here

Libraries -> libraries

XmlSerializer -> <xref:System.Xml.Serialization.XmlSerializer> or inline quote

mairaw · 2018-01-09T19:42:33Z

docs/core/additional-tools/index.md

+This section compiles a list of tools that support and extend the .NET Core functionality, in addition to the [.NET Core command-line interface (CLI)](..\tools\index.md) tools.
+
+### [WCF Web Service Reference Tool](wcf-web-service-reference-guide.md)
+The WCF Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#WCFTools). The WCF Web Service Reference Tool generates a web service reference containing proxy code for a client to easily consume the web service's functionality, similar to the Add Service Reference tool for .NET Framework Visual Studio projects.


remove locale from url.

mairaw · 2018-01-09T20:05:23Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+ </ItemGroup>
+ ```
+
+ ### Add another ItemGroup section for .NET Core CLI Tool support


nit: funny that this header is not showing in blue

mairaw · 2018-01-09T20:05:35Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+
+ ### Add another ItemGroup section for .NET Core CLI Tool support
+
+ Add the following lines after the `ItemGroup` section that we just inspected.


mairaw · 2018-01-09T20:05:52Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+ </ItemGroup>
+ ```
+
+### Add a class in the application. 


period in the heading?

mairaw · 2018-01-09T20:07:10Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+* Install your favorite code editor, if you haven't already.
+
+> [!TIP]
+> Need to install a code editor? Try [Visual Studio](https://visualstudio.com/downloads)!


the link used by the vsdocs team is this one: https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs

mairaw · 2018-01-09T20:09:47Z

docs/core/additional-tools/xmlserializergenerator-instructions.md

+ $ dotnet run
+ ```
+> [!NOTE]
+> [`dotnet run`](../tools/dotnet-run.md) calls [`dotnet build`](../tools/dotnet-build.md) to ensure that the build targets have been built, and then calls `dotnet <assembly.dll>` to run the target application.


not sure if we should add a note similar to what we have in the end of the following tutorial given that dotnet run is only meant for dev scenarios:
https://docs.microsoft.com/en-us/dotnet/core/tutorials/using-with-xplat-cli

"Note that the commands and steps shown in this tutorial to run your application are used during development time only. Once you're ready to deploy your app, you'll want to take a look at the different deployment strategies for .NET Core apps and the dotnet publish command."

updated description and progress window image

Resyncing changes

svick · 2018-01-13T12:22:51Z

docs/core/additional-tools/xml-serializer-generator.md

+
+```csharp
+var serializer = new System.Xml.Serialization.XmlSerializer(typeof(MyClass));
+```


Just creating a serializer is not useful on its own.

Should this tutorial also include some short code that uses it? Or maybe link to another tutorial that explains that?

Good idea. I linked to some other resources.

svick · 2018-01-13T12:29:33Z

docs/core/additional-tools/index.md

+The WCF Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/news/releasenotes/vs2017-relnotes#WCFTools). The WCF Web Service Reference Tool generates a web service reference containing proxy code for a client to easily consume the web service's functionality, similar to the Add Service Reference tool for .NET Framework Visual Studio projects.
+
+### [XML Serializer Generator](xmlserializergenerator-instructions.md)
+Like the [Xml Serializer Generator (sgen.exe)](../standard/serialization/xml-serializer-generator-tool-sgen-exe.md) for .NET Framework, <xref:System.Xml.Serialization.XmlSerializer> is the solution for .NET Core and .NET Standard libraries. It creates an XML serialization assembly for types contained in an assembly to improve the startup performance of XML serialization when serializing or de-serializing objects of those types using <xref:System.Xml.Serialization.XmlSerializer>.


Maybe I was unclear in my previous comment, I think this should say:

Like the Xml Serializer Generator (sgen.exe) for .NET Framework, the Microsoft.XmlSerializer.Generator NuGet package is the solution for .NET Core and .NET Standard libraries.

Since XmlSerializer on its own does not create the serialization assembly.

svick · 2018-01-13T12:30:02Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+
+2. On the **Connected Services** page, click **Microsoft WCF Web Service Reference Provider**. This brings up the **Configure WCF Web Service Reference** wizard:
+
+![Service Endpoint tab](,/media/wcf-web-service-reference-guide/WCFCS-ServiceEndpointPage.png)


The comma at the start of the link should be a period.

Good catch.

svick · 2018-01-13T12:31:23Z

docs/core/additional-tools/xml-serializer-generator.md

+> * How to add a class and an XmlSerializer
+> * How to build and run the application 
+
+Like the [Xml Serializer Generator (sgen.exe)](https://docs.microsoft.com/en-us/dotnet/standard/serialization/xml-serializer-generator-tool-sgen-exe) for the .NET Framework, <xref:System.Xml.Serialization.XmlSerializer> is the equivalent for .NET Core and .NET Standard projects. It creates an XML serialization assembly for types contained in an assembly to improve the startup performance of XML serialization when serializing or de-serializing objects of those types using <xref:System.Xml.Serialization.XmlSerializer>.


Similarly to my other comment, I think this should say:

Like the Xml Serializer Generator (sgen.exe) for the .NET Framework, Microsoft.XmlSerializer.Generator NuGet package is the equivalent for .NET Core and .NET Standard projects.

mairaw

Approving this PR but there are still some comments left to be addressed.

mairaw · 2018-01-18T23:40:47Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

@@ -0,0 +1,78 @@
+--- 


remove the hidden character here that is causing the metadata section not to render as a table on preview

mairaw · 2018-01-18T23:43:01Z

docs/core/additional-tools/index.md

+The WCF Web Service Reference is a Visual Studio connected service provider that made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/news/releasenotes/vs2017-relnotes#WCFTools). The WCF Web Service Reference Tool generates a web service reference containing proxy code for a client to easily consume the web service's functionality, similar to the Add Service Reference tool for .NET Framework Visual Studio projects.
+
+### [XML Serializer Generator](xmlserializergenerator-instructions.md)
+Like the [Xml Serializer Generator (sgen.exe)](../../standard/serialization/xml-serializer-generator-tool-sgen-exe.md) for .NET Framework, he Microsoft.XmlSerializer.Generator nuget package is the solution for .NET Core and .NET Standard libraries. It creates an XML serialization assembly for types contained in an assembly to improve the startup performance of XML serialization when serializing or de-serializing objects of those types using <xref:System.Xml.Serialization.XmlSerializer>.


typically we'd say "for the .NET Framework" with the article

he -> the

nuget -> NuGet

inline code or create link for Microsoft.XmlSerializer.Generator?

I created a link to the NuGet package page.

mairaw · 2018-01-18T23:44:24Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+---
+# Microsoft WCF Web Service Reference Provider Tool
+
+Over the years, many Visual Studio developers have enjoyed the productivity that the [Add Service Reference](https://docs.microsoft.com/visualstudio/data-tools/how-to-add-update-or-remove-a-wcf-data-service-reference) tool provided when their .NET Framework projects needed to access web services. The **WCF Web Service Reference** tool is a Visual Studio connected service extension that provides an experience like the Add Service Reference functionality for .NET Core and ASP.NET Core projects. This tool retrieves metadata from a web service in the current solution, on a network location, or from a WSDL file, and generates a .NET Core compatible source file containing Windows Communication Foundation (WCF) client proxy code that you can use to access the web service.


remove https://docs.microsoft.com from the link

bold Add Service Reference

mairaw · 2018-01-18T23:47:19Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+
+The **Connected Services** page appears as shown in the following image:
+
+![Connected Services tab](./media/wcf-web-service-reference-guide/WCFCS-ConnectedServicesPage.png)


images are not rendering. they are still not inside a media folder. also here the image name is still using capital letters, it should be lowercase.

also alt text should be more descriptive,

mairaw · 2018-01-18T23:48:46Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+While displaying progress, the tool:
+
+* Downloads metadata from the WCF service. 
+* Generates the service reference code in a file named *reference.cs*, and add it to your project under the **Connected Services** node. 


and add -> and adds

mairaw · 2018-01-18T23:49:03Z

docs/core/additional-tools/wcf-web-service-reference-guide.md

+
+When these processes complete, you can create an instance of the generated WCF client type and invoke the service operations.
+
+## Next Steps


sentence case in headings

mairaw · 2018-01-18T23:52:55Z

docs/core/additional-tools/xml-serializer-generator.md

+var serializer = new System.Xml.Serialization.XmlSerializer(typeof(MyClass));
+```
+
+### Build and run the application


should you show the whole file after all the steps are done so people can verify they did right?

It's a dll.

@JRAlexander I was talking about the source code above this step.

mlacouture added 5 commits December 4, 2017 15:16

Initial documentation for additional tools

88420b7

fixed image links

75f9894

updated service endpoint picture

ff1eabc

Added warning note

a7a88ef

removed text left out accidentally from previous commit

90e9cd6

zhenlan requested review from shmao and mairaw December 5, 2017 00:35

shmao reviewed Dec 5, 2017

View reviewed changes

mlacouture added 2 commits December 5, 2017 12:07

incorporated feedback

252cf8c

updated text formatting and some text edits

a5fbcf4

mlacouture force-pushed the master branch from 94adac4 to a5fbcf4 Compare December 6, 2017 19:22

mlacouture added 4 commits December 6, 2017 11:44

One more formatting fix

9f5197b

renamed file all lowercased

41e5472

fixed target framework reference

3c44868

Added entry to the .NET Core Additional Tools index

057c511

zhenlan reviewed Dec 6, 2017

View reviewed changes

fixed meta char for IMPORTANT tag

0f57448

mairaw requested changes Dec 11, 2017

View reviewed changes

mairaw added the WIP label Dec 13, 2017

JRAlexander self-assigned this Dec 20, 2017

JRAlexander added this to the Sprint 128 (12/04/17 - 12/22/17) milestone Dec 20, 2017

JRAlexander suggested changes Dec 20, 2017

View reviewed changes

JRAlexander added 5 commits December 20, 2017 17:41

Revised with recommended changes from review.

be64c9a

Added the recommended changes from the reviewers for this file.

Update based on review feedback and rename file to remove spaces

9b389e7

Update based on review feedback and rename wcf_web_service_reference-guide.md to wcf-web-service-reference-guide.md

Update based on review feedback and format tutorial

0d18a24

Update based on review feedback and format tutorial

Revised due to feedback

469f6b2

Revised after review feedback

b4bf8ff

JRAlexander approved these changes Dec 22, 2017

View reviewed changes

svick reviewed Dec 27, 2017

View reviewed changes

Updated file name and removed Nuget package

ccedeed

JRAlexander added this to the Sprint 129 (12/25/2017 - 1/12/2018) milestone Jan 3, 2018

JRAlexander added 5 commits January 5, 2018 17:15

Revised based on review feedback

1771995

* Updated Note formatting * Fixed capitalization * added space before **Reuse * Update the project file moved to new line

Revised based on review

a4ddcce

Removed nuget package

10c472d

Removed the words "nuget package" from the introduction paragraph.

Update TOC.md

ee2af80

Corrected and asdded needed entries for TOC

Redid removing spaces from brackets in code snippet

67cf686

mairaw requested changes Jan 9, 2018

View reviewed changes

updated description and progress window image

b6d3d9d

mlacouture closed this Jan 10, 2018

JRAlexander reopened this Jan 10, 2018

jralexander and others added 9 commits January 9, 2018 18:41

Revised based on review feedback

af1978d

Revised production information at bottom

fe7a286

Merge pull request #2 from mlacouture/dev/miguell/dotnetdocs/updates

f0e75c7

updated description and progress window image

revised metadata

4866d47

Merge branch 'master' of https://github.com/mlacouture/docs

9e1ec32

Resyncing changes

TOC changes,feddback revisions,file rename,move images to media

d56e0d6

Fixed relative link

bf0a002

fixed relative links

978e93d

changed media directory and changed filenames to lower case

d5b95ca

svick reviewed Jan 13, 2018

View reviewed changes

jralexander added 2 commits January 17, 2018 13:43

Revising based on review feedback.

3075491

Added Related resources and revised link

d4dc1fd

JRAlexander changed the title ~~[WIP] Initial documentation for additional tools~~ Initial documentation for additional tools Jan 18, 2018

JRAlexander removed the WIP label Jan 18, 2018

JRAlexander modified the milestones: Sprint 129 (12/25/2017 - 1/12/2018), Sprint 130 (1/13/18 - 2/2/18) Jan 18, 2018

mairaw approved these changes Jan 18, 2018

View reviewed changes

jralexander added 2 commits January 19, 2018 12:12

Revised based on review comments

a46dbd0

Revised based on review comments

5e338db

JRAlexander merged commit 28a477c into dotnet:master Jan 19, 2018

		@@ -0,0 +1,51 @@
		## Microsoft WCF Web Service Reference Provider

		Over the years, many Visual Studio developers have enjoyed the productivity that Add Service Reference provides when their .NET Framework projects needed to access Windows Communication Foundation (WCF) services. The WCF team is excited to introduce the WCF Connected Service for .NET Core and ASP.NET Core, a VS extension providing an experience like the Add Service Reference functionality. This tool retrieves metadata from a WCF service in the current solution, locally or on a network, and generates a .NET Core compatible source code file for a WCF client proxy that you can use to access the service.


		### How to use the extension

		The WCF Web Service Reference VS connected service extension is applicable to projects created using the templates under Visual C# -> .Net Core, Visual C# -> .Net Standard and Visual C# -> Web -> ASP.NET CORE Web Application projects.


		Over the years, many Visual Studio developers have enjoyed the productivity that the [Add Service Reference](https://msdn.microsoft.com/en-us/library/bb386382.aspx) tool provided when their .NET Framework projects needed to access Windows Communication Foundation (WCF) services. The WCF team is excited to introduce the WCF Web Service Reference tool, a Visual Studio connected service extension providing an experience like the Add Service Reference functionality for .NET Core and ASP.NET Core projects. This tool retrieves metadata from a WCF service in the current solution, from a WSDL file or on a network location, and generates a .NET Core compatible source file containing WCF client proxy code that you can use to access the web service.

		> [!!IMPORTANT]



		### [WCF Web Service Reference](wcf_web_service_reference-guide.md)
		The WCF Web Service Reference is a Visual Studio connected service provider which made its debut in [Visual Studio 2017 version 15.5](https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#WCFTools). Similarly to the Add Service Reference tool for classic .Net Framework VS projects, it allows for generating a web service reference containing proxy code that makes it easier for a client to consume the web service's functionality.

		This section compiles a list of tools that support and extend the .Net Core functionality, in addition to the [.NET Core command-line interface (CLI)](..\tools\index.md) tools.


		### [WCF Web Service Reference](wcf_web_service_reference-guide.md)


		### Build and run the application

		Still within the myApp folder, run the application via [`dotnet run`](../tools/dotnet-run.md) and it will automatically load and use the pre-generated serializers at runtime.


		If everything succeeds, an assembly named MyApp.XmlSerializers.dll is generated in the output folder.

		Congratulations! you have just:


		### Add another ItemGroup section for .NET Core CLI Tool support

		Add the following lines after the `ItemGroup` section that we just inspected.


		2. On the Connected Services page, click Microsoft WCF Web Service Reference Provider. This brings up the Configure WCF Web Service Reference wizard:

		![Service Endpoint tab](,/media/wcf-web-service-reference-guide/WCFCS-ServiceEndpointPage.png)


		The Connected Services page appears as shown in the following image:

		![Connected Services tab](./media/wcf-web-service-reference-guide/WCFCS-ConnectedServicesPage.png)


		When these processes complete, you can create an instance of the generated WCF client type and invoke the service operations.

		## Next Steps

Initial documentation for additional tools #3871

Initial documentation for additional tools #3871

Conversation

mlacouture commented Dec 4, 2017 • edited by JRAlexander Loading

Title

Summary

Suggested Reviewers

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mairaw left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

JRAlexander Jan 3, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mairaw left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mairaw Jan 9, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mairaw left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mlacouture commented Dec 4, 2017 •

edited by JRAlexander

Loading

JRAlexander Jan 3, 2018 •

edited

Loading

mairaw Jan 9, 2018 •

edited

Loading