Although I could successfully create a console app, when I tried to import the references to the Windows Store app, it gave me compile errors because some references could not be resolved. This means that, since Windows Store has a limited .NET API, it can't use some of the features this library is using (at least the way IKVM generated it).
Either I find a way to generate a Windows Store compatible library, or I'm afraid I'll have to manually port the library.
I stopped developing for Windows Store because so many important methods are missing from the Windows Store version of .NET. System.Security.Cryptography, which was required for my app is a good example.
I think there may be alternative methods, but they made it very hard to port programs by not using the same ones. Hmm, I wonder why there are no good Windows Store apps?
Razick, porting NBitcoin to Portable library is not complicated and definitively feasable thanks to the unit tests.
I say that because I did it for a customer of mine, it took approximately 7H.
To do that, you need to fetch the sources of BouncyCastle, and strip every thing that does not compile in portable.
Then, do the same with NBitcoin, strip every class you don't need.
Then, do the same with NBitcoin.Tests, so you can be sure you did not broke anything by porting or stripping too much. Run tests with Core and UnitTests traits.
For my customer, NBitcoin works on xamarin (IOS, Android, Windows Phone). I wanted to make it open source directly, but he pays the bill, so he got a private copy of this work. I might release the code in open source when the project is finished if he agrees.
If not, I will redo the port from scratch.
Some goodies : NBitcoin signature verification and generation, and all crypto ECC operations are manifold more performant thanks to the most recent version of BouncyCastle
All security stuff is implemented in BouncyCastle so no dependance on System.Security.Crypto.
One problematic thing is the Random generation, RandomUtils will not compile because generating a random number with enough entropy is plateform specific. Luckily, for the sig creation I implement determinitstic RFC. (
http://tools.ietf.org/html/rfc6979)
