I have been entertaining the idea of using Bouncy castle on the .NET Gadgeteer, running .Net Micro framework. If .NET Micro supports 4.0 I don't have any concern with it.
Regarding .NET 1.1, I looked at MSFTs support lifecycle and it appears that it is supported if installed on a modern OS which is suprising. Did I read that correctly? http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=.NET+Framework -----Original Message----- From: Peter Dettman [mailto:peter.dett...@bouncycastle.org] Sent: Wednesday, September 18, 2013 10:43 AM To: dev-crypto-csharp@bouncycastle.org Subject: Re: [dev-crypto-csharp] Status in general and specifically for release 1.8? Hi Peter, Yes, we're still maintaining it and looking to resume more active development after a couple of quiet years. Really there's not much keeping back 1.8. We're looking to improve the packaging (nuget) and to move to the Portable Class Library as the primary release platform, but I think we'll just release 1.8 as a roll-up of the improvements so far and look at those things for a 2.0 release. However this may be a good time to ask the list: to what extent are users relying on BC.NET running on .NET 1.1, or really on any version before 4? Regards, Pete Dettman On 11/09/2013 4:55 PM, Peter Lindgren wrote: > Hi! > I just joined, and when I look at the issues in Jira and Github, it > appears like the project is somewhat maintained, and the only thing > that hinders the 1.8 release is > http://www.bouncycastle.org/jira/browse/BMA-89, updating the README > file, an issue from 2011. Is that correct? > > > /Peter ********************************************************************** Notice: This e-mail message and any attachment to this e-mail message may contain information that is confidential, proprietary, privileged, legally privileged and/or exempt from disclosure under applicable law. If you are not the intended recipient, please accept this as notice that any disclosure, copying, distribution or use of the information contained in this transmission is strictly prohibited. NFP reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. Any views or opinions expressed in this e-mail are those of the sender and do not necessarily express those of NFP. Although this transmission and any attachment are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by NFP, its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you have received this e-mail in error, please immediately contact the sender by return e-mail or by telephone at 212-301-4000 and destroy the material in its entirety, whether electronic or hard copy format.
