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.
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 <oskar.bergg...@gmail.com>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.
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 <oskar.bergg...@gmail.com>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.
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 <julian.maug...@gmail.com>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 <oskar.bergg...@gmail.com >> > 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.
Sorry for getting in the middle of your discussion... just wanted to ask one thing: some guys implemented strongly typed update and delete operations on top of LINQ for Entity Framework ( https://github.com/loresoft/EntityFramework.Extended). For example:
//delete all users where FirstName matches context.Users.Delete(u => u.FirstName == "firstname");
//update all tasks with status of 1 to status of 2 context.Tasks.Update( t => t.StatusId == 1, t2 => new Task {StatusId = 2});
//example of using an IQueryable as the filter for the update var users = context.Users.Where(u => u.FirstName == "firstname"); context.Users.Update(users, u => new User {FirstName = "newfirstname"});
Do you think this would be something interesting for NHibernate?
On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
Considering NH already has HQL updates, it's less of an issue... It's a nice feature nonetheless. It can probably be implemented without breaking changes, so it's just a matter of starting it.
On Sun, Apr 22, 2012 at 06:44, Ricardo Peres <rjpe...@gmail.com> wrote: > Hi!
> Sorry for getting in the middle of your discussion... just wanted to ask > one thing: some guys implemented strongly typed update and delete > operations on top of LINQ for Entity Framework ( > https://github.com/loresoft/EntityFramework.Extended). > For example:
> //delete all users where FirstName matches > context.Users.Delete(u => u.FirstName == "firstname");
> //update all tasks with status of 1 to status of 2 > context.Tasks.Update( > t => t.StatusId == 1, > t2 => new Task {StatusId = 2});
> //example of using an IQueryable as the filter for the update > var users = context.Users.Where(u => u.FirstName == "firstname"); > context.Users.Update(users, u => new User {FirstName = "newfirstname"});
> Do you think this would be something interesting for NHibernate?
> Thanks,
> RP
> On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
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.
On Sun, Apr 22, 2012 at 01:14, Fabio Maulo <fabioma...@gmail.com> 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 <julian.maug...@gmail.com > > 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 < >>> oskar.bergg...@gmail.com> 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.
> 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 <fabioma...@gmail.com> 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 < >> julian.maug...@gmail.com> 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 < >>>> oskar.bergg...@gmail.com> 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.
I would second the ability for using linq statements to do deletes / updates. Yes there is hql, but some people don't use hql at all because you can use linq.
On Sunday, April 22, 2012 3:44:46 AM UTC-6, Ricardo Peres wrote:
> Hi!
> Sorry for getting in the middle of your discussion... just wanted to ask > one thing: some guys implemented strongly typed update and delete > operations on top of LINQ for Entity Framework ( > https://github.com/loresoft/EntityFramework.Extended). > For example:
> //delete all users where FirstName matches > context.Users.Delete(u => u.FirstName == "firstname");
> //update all tasks with status of 1 to status of 2 > context.Tasks.Update( > t => t.StatusId == 1, > t2 => new Task {StatusId = 2});
> //example of using an IQueryable as the filter for the update > var users = context.Users.Where(u => u.FirstName == "firstname"); > context.Users.Update(users, u => new User {FirstName = "newfirstname"});
> Do you think this would be something interesting for NHibernate?
> Thanks,
> RP
> On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
On Sun, Apr 22, 2012 at 2:41 PM, Darren Kopp <darrenk...@gmail.com> wrote: > I would second the ability for using linq statements to do deletes / > updates. Yes there is hql, but some people don't use hql at all because you > can use linq.
> On Sunday, April 22, 2012 3:44:46 AM UTC-6, Ricardo Peres wrote:
>> //delete all users where FirstName matches >> context.Users.Delete(u => u.FirstName == "firstname");
>> //update all tasks with status of 1 to status of 2 >> context.Tasks.Update( >> t => t.StatusId == 1, >> t2 => new Task {StatusId = 2});
>> //example of using an IQueryable as the filter for the update >> var users = context.Users.Where(u => u.FirstName == "firstname"); >> context.Users.Update(users, u => new User {FirstName = "newfirstname"});
>> Do you think this would be something interesting for NHibernate?
>> Thanks,
>> RP
>> On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
This is simple enough to implement through extension methods. It probably wouldn't even have to be part of NHibernate core but could easily be provided through an add-on library.
I've implemented a proof of concept in https://github.com/pvginkel/nhibernate-core-testcase. This project has a file named MutationExtensionMethods.cs in the Mutation directory which provides the mutation functionality through extension methods. This is a very rough implementation (the update currently only works on properties and goes through reflection).
On Sunday, April 22, 2012 11:44:46 AM UTC+2, Ricardo Peres wrote:
> Hi!
> Sorry for getting in the middle of your discussion... just wanted to ask > one thing: some guys implemented strongly typed update and delete > operations on top of LINQ for Entity Framework ( > https://github.com/loresoft/EntityFramework.Extended). > For example:
> //delete all users where FirstName matches > context.Users.Delete(u => u.FirstName == "firstname");
> //update all tasks with status of 1 to status of 2 > context.Tasks.Update( > t => t.StatusId == 1, > t2 => new Task {StatusId = 2});
> //example of using an IQueryable as the filter for the update > var users = context.Users.Where(u => u.FirstName == "firstname"); > context.Users.Update(users, u => new User {FirstName = "newfirstname"});
> Do you think this would be something interesting for NHibernate?
> Thanks,
> RP
> On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
On Monday, April 23, 2012 7:32:04 AM UTC+1, pvginkel wrote:
> This is simple enough to implement through extension methods. It probably > wouldn't even have to be part of NHibernate core but could easily be > provided through an add-on library.
> I've implemented a proof of concept in > https://github.com/pvginkel/nhibernate-core-testcase. This project has a > file named MutationExtensionMethods.cs in the Mutation directory which > provides the mutation functionality through extension methods. This is a > very rough implementation (the update currently only works on properties > and goes through reflection).
> Maybe I'll pick this up.
> On Sunday, April 22, 2012 11:44:46 AM UTC+2, Ricardo Peres wrote:
>> Hi!
>> Sorry for getting in the middle of your discussion... just wanted to ask >> one thing: some guys implemented strongly typed update and delete >> operations on top of LINQ for Entity Framework ( >> https://github.com/loresoft/EntityFramework.Extended). >> For example:
>> //delete all users where FirstName matches >> context.Users.Delete(u => u.FirstName == "firstname");
>> //update all tasks with status of 1 to status of 2 >> context.Tasks.Update( >> t => t.StatusId == 1, >> t2 => new Task {StatusId = 2});
>> //example of using an IQueryable as the filter for the update >> var users = context.Users.Where(u => u.FirstName == "firstname"); >> context.Users.Update(users, u => new User {FirstName = "newfirstname"});
>> Do you think this would be something interesting for NHibernate?
>> Thanks,
>> RP
>> On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
> On Sun, Apr 22, 2012 at 9:00 AM, Diego Mijelshon <di...@mijelshon.com.ar>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 <fabioma...@gmail.com> 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 < >>> julian.maug...@gmail.com> 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 < >>>>> oskar.bergg...@gmail.com> 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.
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?
On Mon, Apr 23, 2012 at 12:56, Ricardo <rs...@usa.com> 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 <di...@mijelshon.com.ar>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 <fabioma...@gmail.com> 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 < >>>> julian.maug...@gmail.com> 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 < >>>>>> oskar.bergg...@gmail.com> 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.
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 <di...@mijelshon.com.ar>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 <rs...@usa.com> 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 <di...@mijelshon.com.ar >>> > 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 <fabioma...@gmail.com>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 < >>>>> julian.maug...@gmail.com> 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 < >>>>>>> oskar.bergg...@gmail.com> 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.
I have been in some of such corporates where versions are "slowly adopted" (ie, still on WinXP, Office 2003, SQL2000, etc, etc, you name it). It tends to be a general symptom, not just the software (they generally tend to say things like "we're using proven technology, and not want to come across fresh bugs.."). That's the case at your site as well? If so, then I'd say, dont take into account those situation (too much), as it likely means they wont use the newest version of NHibernate either?
(Just my 2 cents, as a non-contributor, listening on this mailinglist. If this kind of input is not appreciated, please do let me know..)
On Mon, Apr 23, 2012 at 6:13 PM, Richard Birkby <rbir...@gmail.com> 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 <di...@mijelshon.com.ar>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 <rs...@usa.com> 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 < >>>> di...@mijelshon.com.ar> 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 <fabioma...@gmail.com>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 < >>>>>> julian.maug...@gmail.com> 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 < >>>>>>>> oskar.bergg...@gmail.com> 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.
Yes, there's stop-energy and general bureaucracy and fiefdoms where factions form guidelines which must be followed - such as the corp loadset is WinXP or the development tool/platform is VS2008/Net35. I'm even starting to see some guidelines which say EF is the corp standard, therefore we have to move away from NH - no chance of that happening without EF getting a lot faster and gaining ADO batch support.
As to whether our project moves to the latest version of NH - well my VS pending changes window has an upgrade to NH3.3 ready to commit :-)
Richard
On Mon, Apr 23, 2012 at 5:16 PM, Matthijs ter Woord <
matthijsterwo...@gmail.com> wrote: > Richard, just out of curiousity..
> I have been in some of such corporates where versions are "slowly adopted" > (ie, still on WinXP, Office 2003, SQL2000, etc, etc, you name it). > It tends to be a general symptom, not just the software (they generally > tend to say things like "we're using proven technology, and not want to > come across fresh bugs.."). That's the case at your site as well? > If so, then I'd say, dont take into account those situation (too much), as > it likely means they wont use the newest version of NHibernate either?
> (Just my 2 cents, as a non-contributor, listening on this mailinglist. If > this kind of input is not appreciated, please do let me know..)
> On Mon, Apr 23, 2012 at 6:13 PM, Richard Birkby <rbir...@gmail.com> 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 <di...@mijelshon.com.ar>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 <rs...@usa.com> 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 < >>>>> di...@mijelshon.com.ar> 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 <fabioma...@gmail.com>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 < >>>>>>> julian.maug...@gmail.com> 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 < >>>>>>>>> oskar.bergg...@gmail.com> 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.
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.
On Mon, Apr 23, 2012 at 13:13, Richard Birkby <rbir...@gmail.com> 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 <di...@mijelshon.com.ar>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 <rs...@usa.com> 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 < >>>> di...@mijelshon.com.ar> 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 <fabioma...@gmail.com>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 < >>>>>> julian.maug...@gmail.com> 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 < >>>>>>>> oskar.bergg...@gmail.com> 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.
To me it sounds like .Net 4 contain a number of useful things like ISet, and it feels like we should focus on those matters first.
On the other hand, if someone wants to work on features that require Net45, perhaps we could maintain a long-lived branch, or use conditional compilation.
What is the situation with future support for Net35? Should we aim for a release that can be compiled on both Net35 and Net4?
/Oskar
Den 23 april 2012 18:39 skrev Diego Mijelshon <di...@mijelshon.com.ar>:
> 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 <rbir...@gmail.com> 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 <di...@mijelshon.com.ar> >> 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 <rs...@usa.com> 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 >>>>> <di...@mijelshon.com.ar> 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 <fabioma...@gmail.com> >>>>>> 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 >>>>>>> <julian.maug...@gmail.com> 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 >>>>>>>>> <oskar.bergg...@gmail.com> 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.
> 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 <rbir...@gmail.com> 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 <di...@mijelshon.com.ar>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 <rs...@usa.com> 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 < >>>>> di...@mijelshon.com.ar> 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 <fabioma...@gmail.com>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 < >>>>>>> julian.maug...@gmail.com> 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 < >>>>>>>>> oskar.bergg...@gmail.com> 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.
The .NET 4.0 runtime and frameworks have been around sufficiently long that they should be acceptable runtime environments for most organisations. The same certainly cannot be said for the .NET 4.5 generation of products.My inclination would be to focus on .NET 4.0 and drop support for .NET 3.5.
On Monday, 23 April 2012 20:18:01 UTC+2, Oskar Berggren wrote: > To me it sounds like .Net 4 contain a number of useful things like > ISet, and it feels like we should focus on those matters first.
> On the other hand, if someone wants to work on features that require > Net45, perhaps we could maintain a long-lived branch, or use > conditional compilation.
> What is the situation with future support for Net35? Should we aim for > a release that can be compiled on both Net35 and Net4?
> /Oskar
> Den 23 april 2012 18:39 skrev Diego Mijelshon <di...@mijelshon.com.ar>: > > 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 <rbir...@gmail.com> 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 < > di...@mijelshon.com.ar> > >> 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 <rs...@usa.com> 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 > >>>>> <di...@mijelshon.com.ar> 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 <fabioma...@gmail.com> > >>>>>> 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 > >>>>>>> <julian.maug...@gmail.com> 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 > >>>>>>>>> <oskar.bergg...@gmail.com> 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.
> The .NET 4.0 runtime and frameworks have been around sufficiently long > that they should be acceptable runtime environments for most organisations. > The same certainly cannot be said for the .NET 4.5 generation of > products.My inclination would be to focus on .NET 4.0 and drop support for > .NET 3.5.
> Regards, > Gerke.
> On Monday, 23 April 2012 20:18:01 UTC+2, Oskar Berggren wrote:
>> To me it sounds like .Net 4 contain a number of useful things like >> ISet, and it feels like we should focus on those matters first.
>> On the other hand, if someone wants to work on features that require >> Net45, perhaps we could maintain a long-lived branch, or use >> conditional compilation.
>> What is the situation with future support for Net35? Should we aim for >> a release that can be compiled on both Net35 and Net4?
>> /Oskar
>> Den 23 april 2012 18:39 skrev Diego Mijelshon <di...@mijelshon.com.ar>: >> > 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 <rbir...@gmail.com> >> 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 < >> di...@mijelshon.com.ar> >> >> 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 <rs...@usa.com> 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 >> >>>>> <di...@mijelshon.com.ar> 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 <fabioma...@gmail.com> >> >>>>>> 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 >> >>>>>>> <julian.maug...@gmail.com> 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 >> >>>>>>>>> <oskar.bergg...@gmail.com> 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.
Is it really usefull to discuss which framework to target?
I think it is more wise to discuss a roadmap with coming versions and which
features those roadmap versions will contain and let that be the input to
decide which framework(s) to target.
IMO, it _is_ important when it's directly related to the features each framework provides. I believe async will be quickly become a big deal, so that's something to consider. But there's nothing* stopping us from using conditional directives to enable 4.5 features. NuGet also supports painless multi-framework packages out of the box.
On Tue, Apr 24, 2012 at 06:07, Ramon Smits <ramon.sm...@gmail.com> wrote:
> Is it really usefull to discuss which framework to target?
> I think it is more wise to discuss a roadmap with coming versions and > which features those roadmap versions will contain and let that be the > input to decide which framework(s) to target.
On Monday, April 23, 2012 12:05:12 PM UTC+2, Ricardo Peres wrote:
> Hello, pvginkel!
> Thanks for your interest! I have looked at your code, and in it you are > deleting every entity manually, that is, not issuing a DELETE statement:
> foreach (var record in self) > { > session.Delete(record); > }
> Is this just the preliminary version?
> Thanks,
> RP
> On Monday, April 23, 2012 7:32:04 AM UTC+1, pvginkel wrote:
>> This is simple enough to implement through extension methods. It probably >> wouldn't even have to be part of NHibernate core but could easily be >> provided through an add-on library.
>> I've implemented a proof of concept in >> https://github.com/pvginkel/nhibernate-core-testcase. This project has a >> file named MutationExtensionMethods.cs in the Mutation directory which >> provides the mutation functionality through extension methods. This is a >> very rough implementation (the update currently only works on properties >> and goes through reflection).
>> Maybe I'll pick this up.
>> On Sunday, April 22, 2012 11:44:46 AM UTC+2, Ricardo Peres wrote:
>>> Hi!
>>> Sorry for getting in the middle of your discussion... just wanted to ask >>> one thing: some guys implemented strongly typed update and delete >>> operations on top of LINQ for Entity Framework ( >>> https://github.com/loresoft/EntityFramework.Extended). >>> For example:
>>> //delete all users where FirstName matches >>> context.Users.Delete(u => u.FirstName == "firstname");
>>> //update all tasks with status of 1 to status of 2 >>> context.Tasks.Update( >>> t => t.StatusId == 1, >>> t2 => new Task {StatusId = 2});
>>> //example of using an IQueryable as the filter for the update >>> var users = context.Users.Where(u => u.FirstName == "firstname"); >>> context.Users.Update(users, u => new User {FirstName = "newfirstname"});
>>> Do you think this would be something interesting for NHibernate?
>>> Thanks,
>>> RP
>>> On Saturday, April 21, 2012 8:00:38 PM UTC+1, Oskar Berggren 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.
