From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Cc: nathan.baulch@gmail.com
Subject: [Bitcoin-development] [ANNOUNCE] BitCoinSharp
Date: Mon, 27 Jun 2011 23:04:36 +0200 [thread overview]
Message-ID: <BANLkTi=zdn-ELG4xsVS7oyNQKO6dwtt99g@mail.gmail.com> (raw)
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.
next reply other threads:[~2011-06-27 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 21:04 Mike Hearn [this message]
[not found] ` <DA6FEDE0-8C45-4416-B8BC-FDABC857A87A@heliacal.net>
2011-06-28 6:34 ` [Bitcoin-development] [ANNOUNCE] BitCoinSharp Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=zdn-ELG4xsVS7oyNQKO6dwtt99g@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=nathan.baulch@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox