Summer of Code
Ankit Singla
anksingla at gmail.com
Tue Mar 25 01:01:19 EDT 2008
John Bailey wrote:
> Richard Laager wrote:
>
>> On Sat, 2008-03-22 at 10:19 -0400, John Bailey wrote:
>>
>>> Using .NET introduces additional challenges for the student. Currently glib and
>>> libpurple on Windows are linked against msvcrt.dll, which is the old Visual
>>> Studio 6 runtime library. .NET applications are linked against
>>> msvcrt7.dll
>>>
>> It might actually be easier to solve these issues and then use .NET than
>> to avoid them and write with MFC. I hope this is not immediately
>> dismissed.
>>
>> Richard
>>
>
> I'm certainly not intending to suggest we completely ignore .NET simply because
> of these issues, but MFC does gain us the advantage of working on Windows NT
> 4.0, Windows 98, and Windows ME (assuming the theoretical MFC-based client ships
> with glib 2.6.x for libpurple), where .NET 3.0 doesn't. I don't recall if .NET
> 2.0 works there.
>
According to the MS .NET 2.0 download page
(http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en#Requirements),
Win98 is supported. I'm inclined to agree with Richard here.
> My main motivation for wanting an MFC-based UI is that MFC works everywhere
> WinPidgin does, but .NET will/may not depending on which .NET is used. As I
> recall, this is why we still link WinPidgin against glib/GTK+ 2.6.x (newer
> versions don't work on these older Windows versions). There may also be a speed
> advantage on older hardware where .NET applications are slow.
>
> John
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/devel
>
Ankit
More information about the Devel
mailing list