Of course I wasn't being literal with the suicide thing... :-)
Anyway, let's remember that switching to .NET 4.5 doesn't mean XP users
won't be able to use NHibernate anymore. They'll just have to stick with NH
3.x, just like they are stuck with IE 8, VS2012 and many other pieces of
outdated or soon-to-be-outdated software.
Diego
On Mon, Apr 23, 2012 at 13:13, Richard Birkby <[email protected]> wrote:
> I'm writing this from a corporate Windows XP machine (which was new in
> March 2011).
> The current plan in this corporate is to go to Win7 towards the end of
> this year...probably after Win8/IE10 has been released.....
>
>
> Richard
> ps Yes, it's frustrating, but suicide is going a bit far
>
>
> On Mon, Apr 23, 2012 at 5:06 PM, Diego Mijelshon
> <[email protected]>wrote:
>
>> Windows XP's mainstream support ended 3 years ago, even before NH 3.0
>> release.
>> NH is used more in the server (for web apps) than in the PC [citation
>> needed]
>> XP support will be retired entirely by April 8, 2014 (less than two years
>> from now)
>> I'd personally kill myself if I had to work for a company that was still
>> on XP
>> Do you still think it's a good idea to plan the future of NH based on the
>> practice of companies that haven't renewed their PCs since 2006?
>>
>> Diego
>>
>>
>>
>> On Mon, Apr 23, 2012 at 12:56, Ricardo <[email protected]> wrote:
>>
>>>
>>> Windows XP is not compatible with framework 4.5. The market share of XP
>>> is still strong in many companies.
>>>
>>> Do you think the new features of .net 4.5 are so important to Nhibernate
>>> ?
>>>
>>> I think you could move to .NET 4.0 for next major version of
>>> Nhibertante and abandon XP compatibility when Microsoft launch .NET 5.0.
>>>
>>> Ricardo
>>>
>>> Em domingo, 22 de abril de 2012 10h28min02s UTC-3, Fabio Maulo escreveu:
>>>
>>>> after use parallel
>>>>
>>>> On Sun, Apr 22, 2012 at 9:00 AM, Diego Mijelshon <
>>>> [email protected]> wrote:
>>>>
>>>>> I see a couple ways to benefit from .NET 4.5:
>>>>> - Targeting the Portable Class Library
>>>>> - Taking advantage of (and exposing) async methods
>>>>>
>>>>> Both require considerable effort.
>>>>>
>>>>> The latter can result in interesting improvements. Consider:
>>>>> var results = await session.CreateQuery(...).List<**Foo>();
>>>>> Internally, this could use async ADO.NET methods, so a good part of
>>>>> the processing would not hold a thread.
>>>>>
>>>>> Diego
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Apr 22, 2012 at 01:14, Fabio Maulo <[email protected]>wrote:
>>>>>
>>>>>> That mean just: "wait some more months after you have waited one
>>>>>> year".
>>>>>> btw,
>>>>>> which are the specific features of .NET4.5 you are thinking about and
>>>>>> how they may benefit NH ?
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 22, 2012 at 12:22 AM, Julian Maughan <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Another option to consider is skipping .NET 4, and going straight to
>>>>>>> 4.5?
>>>>>>>
>>>>>>> On Sunday, 22 April 2012 04:10:13 UTC+8, Fabio Maulo wrote:
>>>>>>>>
>>>>>>>> In general after a release we have some other 2 or 3 minor releases
>>>>>>>> (for some reason was not the case for 3.2.0).
>>>>>>>> For vNext I'm strongly oriented to make another "big" breaking
>>>>>>>> change... NH4.0.0 .NET4 with bye bye to Iesi.Collection, drop of some
>>>>>>>> custom threadsafe collection to use those implemented in .NET4 ...
>>>>>>>> NH4.1.0 drop of IDictionary for dynamic object and the usage of
>>>>>>>> .NET4 dynamic ,
>>>>>>>> NH4.2.0 the usage of parallel to hydrate collections after queries.
>>>>>>>>
>>>>>>>> On Sat, Apr 21, 2012 at 4:00 PM, Oskar Berggren <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> So what do we do now that NH 3.3.0GA is released?
>>>>>>>>>
>>>>>>>>> There are already several interesting pull requests lined up, some
>>>>>>>>> of
>>>>>>>>> which are new features. I propose that the next planned version
>>>>>>>>> will
>>>>>>>>> be 3.4.0.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> What about possible as yet undetected regressions in NH 3.3.0GA? Do
>>>>>>>>> you think it would be a good idea to hold of merging to the master
>>>>>>>>> branch for a week or so in case any important regressions pops up
>>>>>>>>> and
>>>>>>>>> we want to do a 3.3.1? One can do this from a branch of course, but
>>>>>>>>> without the assistance of the excellent build server.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Oskar
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Fabio Maulo
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Fabio Maulo
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Fabio Maulo
>>>>
>>>>
>>
>
