From: Mike Hearn <mike@plan99•net>
To: solar <laszlo.hanyecz@heliacal•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
nathan.baulch@gmail•com
Subject: Re: [Bitcoin-development] [ANNOUNCE] BitCoinSharp
Date: Tue, 28 Jun 2011 08:34:14 +0200 [thread overview]
Message-ID: <BANLkTik4m832G_C_P8+oXSt+6QA4QtpC7Q@mail.gmail.com> (raw)
In-Reply-To: <DA6FEDE0-8C45-4416-B8BC-FDABC857A87A@heliacal.net>
Sure.
On Tue, Jun 28, 2011 at 2:49 AM, solar <laszlo.hanyecz@heliacal•net> wrote:
> Great work on this guys! I have a small request though.. could you please include the recent fix to join a random #bitcoinXX channel on IRC (instead of #bitcoin)? It is in the c++ code that way, it's just a randomly selected number from 00 to 99.
>
> Thanks,
> Laszlo Hanyecz
>
>
> On Jun 27, 2011, at 5:04 PM, Mike Hearn wrote:
>
>> 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.
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists•sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
prev parent reply other threads:[~2011-06-28 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 21:04 Mike Hearn
[not found] ` <DA6FEDE0-8C45-4416-B8BC-FDABC857A87A@heliacal.net>
2011-06-28 6:34 ` Mike Hearn [this message]
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=BANLkTik4m832G_C_P8+oXSt+6QA4QtpC7Q@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laszlo.hanyecz@heliacal$(echo .)net \
--cc=nathan.baulch@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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