Bug fixed (SocksPort) and add the DataDirectory command

[PsykotropyK]

Fixed a bug in ClientCreateParam.cs (SocksPort hardcodded which prevented the user to specify its socks port)

Add the DataDirectory command option (ConfigurationNames.cs & Configuration.cs)

[tkowalczyk]

@PsykotropyK is this lib work for you?

`ClientRemoteParams remoteParams = new ClientRemoteParams();
        remoteParams.Address = "127.0.0.1";
        remoteParams.ControlPassword = "";
        remoteParams.ControlPort = 9051;

        Client client = Client.CreateForRemote(remoteParams);

        client.Proxy.Port = 8182;

        using (WebClient webClient = new WebClient())
        {
            if (client.Proxy.IsRunning)
                webClient.Proxy = client.Proxy.WebProxy;

            Console.WriteLine(webClient.DownloadString("http://bot.whatismyipaddress.com/"));
        }`

running the above code will give you a IP address of Tor node actually conected to?

[PsykotropyK]

@tkowalczyk

I did not try your specific piece of code, but when I start usting the library I realized that I could not use webClient.Proxy = client.Proxy.WebProxy;. I had to recreate the proxy for the http client.

Something like this should work :

webClient.Proxy = new Webproxy() { Address = new Uri(client.Proxy.Address) };
Then It showed a Tor exit node ip instead of my ip.

Hope it will help you.

Ciao

[tkowalczyk]

@PsykotropyK by WebProxy class you mean this or some custom?

[PsykotropyK]

Yes, System.Net

[knocte]

So then does this lib work or not? It seems abandoned.