blob: 251f431b66780aa9306a707034047ff842ad50aa (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QbIz5-0003jg-EP
for bitcoin-development@lists.sourceforge.net;
Mon, 27 Jun 2011 21:04:43 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
helo=mail-vx0-f175.google.com;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QbIz4-0007ge-Jx
for bitcoin-development@lists.sourceforge.net;
Mon, 27 Jun 2011 21:04:43 +0000
Received: by vxa37 with SMTP id 37so5459481vxa.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 27 Jun 2011 14:04:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.98.102 with SMTP id eh6mr8934765vdb.298.1309208676972; Mon,
27 Jun 2011 14:04:36 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.169.40 with HTTP; Mon, 27 Jun 2011 14:04:36 -0700 (PDT)
Date: Mon, 27 Jun 2011 23:04:36 +0200
X-Google-Sender-Auth: bXdOwkuSu47S6UeXduE_oanCcf0
Message-ID: <BANLkTi=zdn-ELG4xsVS7oyNQKO6dwtt99g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.2 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QbIz4-0007ge-Jx
Cc: nathan.baulch@gmail.com
Subject: [Bitcoin-development] [ANNOUNCE] BitCoinSharp
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2011 21:04:43 -0000
This evening I'd also like to announce the BitCoinSharp project by
Nathan Baulch. It's big enough to deserve its own email, IMHO.
Nathan has done a complete port of BitCoinJ into C#, thus opening the
world of Bitcoin up to .NET developers everywhere.
You can browse the code here:
http://code.google.com/p/bitcoinsharp/source/browse/
Visual Studio SLN files are provided to help you get started. The
PingService example is a good place to start reading:
http://code.google.com/p/bitcoinsharp/source/browse/src/Examples/PingService.cs
I'm hopeful that we've now covered nearly all the bases in terms of
languages and platforms. Everyone should be able to write interesting
Bitcoin apps no matter what their background or preferred toolchain.
|
