yiskang / csharp-sqlite

Automatically exported from code.google.com/p/csharp-sqlite
Other
0 stars 0 forks source link

.NET 2.0 support broken #75

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Attempt to target .NET 2.0 in project settings

This used to work but now in file crypto.cs line 146, this declaration:
static AesManaged Aes = new AesManaged();

must be changed to:
static RijndaelManaged Aes = new RijndaelManaged();

Targeting .NET 2.0 after this change is again possible. Please update the file. 
Thanks!

Original issue reported on code.google.com by nicholas...@gmail.com on 13 Aug 2010 at 12:26

Attachments:

GoogleCodeExporter commented 8 years ago
Do you acutally use NET 2.0?  Because RijndaelManaged is not supported in 
Silverlight, that is why it was replaced with AesManaged.

If you actually NEED 2.0, I'll have to #if the code to support both

Original comment by noah.hart@gmail.com on 13 Aug 2010 at 1:28

GoogleCodeExporter commented 8 years ago
If this is doable (e.g. via the use of a 
System.Security.Cryptography.SymmetricAlgorithm abstract class rather than 
concrete AesManaged/RijndaelManaged class) then I think the project would 
benefit from supporting .NET 2.0 as this is good for embedded or otherwise low 
overhead type projects, for which c#sqlite is ideally suited.

Original comment by nicholas...@gmail.com on 13 Aug 2010 at 3:59

GoogleCodeExporter commented 8 years ago
Add a Macro NET_2_0 in Community.CsharpSqlite

modify code in crypto.cs 

#if NET_2_0
    static RijndaelManaged Aes = new RijndaelManaged() { BlockSize = 0x80, FeedbackSize = 8, KeySize = 0x100, Mode = CipherMode.CBC };
#else
    static AesManaged Aes = new AesManaged();
#endif

Original comment by ZGSXTY...@gmail.com on 7 Mar 2011 at 1:37

GoogleCodeExporter commented 8 years ago
This issue was closed by revision e0c70dd3a8.

Original comment by noah.hart@gmail.com on 7 Mar 2011 at 2:36