.net compact framework support
Brought to you by:
sheda0
Menu
▾
▴
It will be very nice.
I'll see if this can be incorporated in the future but first I have to address the current bugs. Thanks for the input!
I've given a quick look at the viability of this given the current contents of the repository. For the .NET CF 1.0, getting it to work would be a chore. The CF 1.0 lacks all of Microsoft.Win32.
On the other hand, for the .NET CF 2.0, it almost works already. The only problems are the lack of System.Environment.NewLine (used in the QP conversion methods) and the lack of ToBase64Transform and FromBase64Transform in System.Security.Cryptography. The crypto stuff could be rewritten, and perhaps it's not necessary to worry about Environment.NewLine since the library is already tied to Windows through the use of the registry.
Is there any interest in making the couple of changes required to get this working on the .NET CF 2.0?
After a bit of hacking about I've been able to get this to run on .net CF 2.0. The changes I needed to make were:
Environment.NewLine is replaced with "\r\n" - Not exactly a problem as it is designed to run on a Windows Mobile device.
The line Encoding oEncoding = Encoding.GetEncoding(charset); in MailEncoder.cs threw an error, replaced with Encoding.UTF8.
The ConvertToBase64 and ConvertFromBase64 methods were replaced, check out http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemconvertclasstobase64stringtopic.asp for replacement code.
In GetConnection() in smtp.cs ... setting the timeouts for the TcpClient generated errors. Commending them out worked.
These may not be the best / correct way to do it, but it has worked for me.