Changes between Version 5 and Version 6 of XmlRpcPlugin/DotNet


Ignore:
Timestamp:
Jul 19, 2018, 7:56:37 PM (3 years ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • XmlRpcPlugin/DotNet

    v5 v6  
    33= Accessing XmlRpcPlugin from C#
    44
    5 It is possible to access Trac via the XmlRpcPlugin plug-in from Microsoft's .NET framework. This should work for any .NET language, including Visual Basic. The steps below are written in C#.
     5It is possible to access Trac via the XmlRpcPlugin plugin from Microsoft's .NET framework. This should work for any .NET language, including Visual Basic. The steps below are written in C#.
    66
    77== Step 1. Install the Trac XmlRpcPlugin
     
    8080== Step 6. Handling Certificate Problems (if any)
    8181
    82 If your Trac uses https, make sure it has a valid, verifyable certificate. If you use a self-signed or expired certificate, all is not lost, but you have to take a few additional steps.
     82If your Trac uses https, make sure it has a valid, verifiable certificate. If you use a self-signed or expired certificate, you have to take a few additional steps.
    8383
    84 First, you need to create a server certificate validation callback that always says the certificate is OK, even if it's really not:
     84First, you need to create a server certificate validation callback that says the certificate is OK, even if it's really not:
    8585
    8686{{{#!cs
     
    9494}}}
    9595
    96 Second, ''before'' you create the proxy, do this (for example, at the beginning of Main)
     96Second, ''before'' you create the proxy, add this, for example, at the beginning of Main:
    9797
    9898{{{#!cs