I normally run the tests via the test explorer, but then I tend only to be working on specific things. I gather full testing is still a bit of work to set up - dealing with some of the build issues is on the list though. We just want to get 1.8 out the door first, it will clear quite a backlog.
With CCM the simplest place to look for usage information might be crypto/test/src/test/AESTest.cs and you can delve further from there as required. Regards, David On 23/10/15 02:18, Edward Ned Harvey (bouncycastle) wrote: >> From: den...@dennislandi.com [mailto:den...@dennislandi.com] >> >> I just joined the list. I am a C# developer who has been tasked with >> implementing AES CCM encryption/decryption. >> >> I have started an empty console app project and installed the Bouncy Castle >> Nuget Package. >> >> So I am ready to test some code! >> >> Can someone please give me some guidance on how to get started >> exercising the AES CCM code? >> >> Is there some sample code available? >> >> I am using VS2015 (if that matters) > The first advice I'd give is, since you're doing BC development, instead of > using the NuGet package, fork & clone the BC source. The .sln file is > archaic, but a one-time conversion process works, and then the project > builds. I don't know how David or anyone tests the code - because in my > experience the tests are mostly broken - so I'm sure I'm just doing it wrong. > > The advantage of building from source is that you'll be able to step through > BC code, which is often very useful.
