Skip to main content

Return to Answer

Active reading [<https://en.wiktionary.org/wiki/show#Verb> <https://en.wikipedia.org/wiki/HTTPS>]. Expanded. Added some context. Fixed the weird syntax highlighting (as a result, the diff looks more extensive than it really is - use view "Side-by-side Markdown" to compare).
Source Link
Peter Mortensen
Peter Mortensen
  • 31.3k
  • 22
  • 109
  • 132

I used the Application GUID for my WCFWCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as showshown below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")> 

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exenetsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses HttpsHTTPS via that SSL certcertificate.

I used the Application GUID for my WCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as show below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses Https via that SSL cert.

I used the Application GUID for my WCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as shown below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses HTTPS via that SSL certificate.

added 4 characters in body
Source Link
abatishchev
abatishchev
  • 99.6k
  • 88
  • 300
  • 439

I used the Application GUID for my WCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as show below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses Https via that SSL cert.

I used the Application GUID for my WCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as show below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses Https via that SSL cert.

I used the Application GUID for my WCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as show below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses Https via that SSL cert.

Source Link
atconway
atconway
  • 21.2k
  • 32
  • 163
  • 234

I used the Application GUID for my WCF service that is located within the AsseblyInfo.vb (VB.NET) or AssemblyInfo.cs (C#) file of my hosting application (Windows Service) as show below:

<Assembly: Guid("8fbacae2-bd4e-8ef5-b202-1561845dd04f")>

I used this as the appid parameter for the netsh.exe tool like so:

appid={8fbacae2-bd4e-8ef5-b202-1561845dd04f}

It worked perfectly and my WCF service uses Https via that SSL cert.