Hi Darek and all, Bouncy Castle in my experience presents an invaluable toolset for .NET security. Providing support for current and future mobile devices for example in my view is imperative.
.NET 3.5 in my view should be maintained. In my area of work (distributed computing and applications), NET 3.5 is a strong foundation runtime and is used in commercial and research frameworks. By the same token the parallel capabilities and other CLR features of NET 4.0 and more recently 4.5 are very important as well and should be extended by Bouncy Castle. Perhaps maintain NET 3.5 to have full support including legacy NET 2.0 and earlier. Then have a separate release for NET 4.0 as well. I think Bouncy Castle should be across the board. Kind regards, Jean-Paul ________________________________________ From: Skwarek Dariusz-HVT786 [dskwa...@motorolasolutions.com] Sent: Thursday, September 19, 2013 9:18 PM To: dev-crypto-csharp@bouncycastle.org Subject: RE: [dev-crypto-csharp] Status in general and specifically for release 1.8? We are using Bounce Castle with .NET Compact Framework 3.5. It is not compatible with .NET 4.0 and portable libraries. We would like to port our code to the device which supports .NET portable libraries but it is a long way to go. Regards, Darek -----Original Message----- From: Peter Lindgren [mailto:pe...@norrskenkonsult.com] Sent: Thursday, September 19, 2013 12:02 PM To: dev-crypto-csharp@bouncycastle.org Subject: Re: [dev-crypto-csharp] Status in general and specifically for release 1.8? Peter Dettman skrev 2013-09-18 16:42: > 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? Microsoft BizTalk 2006R2 is still in production on many customer sites, it uses .Net 3.5 SP2. So from my point of view, 3.5 is sufficient. /Peter -- Peter Lindgren Norrsken konsult pe...@norrskenkonsult.com 0703-393940
