Frans,

If you fetch an Entity or a EntityCollection with a bunch of prefetches... what is the best way to set ConcurrencyPredicateFactoryToUse on each of the fetched and prefetched entities?

Do you have to iterate over each of the collections and set it manually?

[Edit: this is in the context of a recursive save...]

Marcus

The best way to do it is using a derived entity factory class which sets the concurrencypredicatefactory instance when the entity is created. You can pass a factory when adding a node to the prefetch path (using an overload of Add()). At least that's the least amoung of effort I think.

Entity's InitClass methods will be split up into an include template pretty soon which will make it possible to 'inject' code at instantiation time for an entity which then allows to create an instance of a concurrencypredicatefactory class without worries.

Otis wrote:

The best way to do it is using a derived entity factory class which sets the concurrencypredicatefactory instance when the entity is created. You can pass a factory when adding a node to the prefetch path (using an overload of Add()). At least that's the least amoung of effort I think.

Entity's InitClass methods will be split up into an include template pretty soon which will make it possible to 'inject' code at instantiation time for an entity which then allows to create an instance of a concurrencypredicatefactory class without worries.

Okay Thanks.

You've mentioned a few times now about a new version "soon"... Have you got any timeframe in mind for this yet?

I hope to be done crunching code at the end of january which will then be the start of teh beta of 1.0.2004.2 Mainly a maintenance release with a lot of tiny 'convenience' features added like single click catalog refresh, unattended refresh, multiple catalogs per project (or schemas per catalog in oracle), multiple join same entity in typed lists, remove schema from catalog, better log viewer etc. etc.

Otis wrote:

I hope to be done crunching code at the end of january which will then be the start of teh beta of 1.0.2004.2 Mainly a maintenance release with a lot of tiny 'convenience' features added like single click catalog refresh, unattended refresh, multiple catalogs per project (or schemas per catalog in oracle), multiple join same entity in typed lists, remove schema from catalog, better log viewer etc. etc.

Table inheritance???

That will come in april/may, as it will require quite a bit if changes and therefore would delay the other enhancements too much.

Is .NET Beta 2 out yet?

heh no way Beta 2 is expected end Q1 2005. Final is expected end august 2005 (but think september)

Otis wrote:

heh no way Beta 2 is expected end Q1 2005. Final is expected end august 2005 (but think september)

LOL - do you honestly think its going to be 2005??? In August 2005, they will announce another name change... "Visual Studio 2006"

Heh, no way, they'll ship in 2005. Yukon has to ship in 2005, so does vs.net, and it's possible, they're on track. MS is however very radical in this: if shipdates aren't met, features have to go. But I'm confident they'll make 2005. I also hope they will, 2003 really gets more annoying every day and as Dan Fernandez (VC# MP) told me: there is no-one working on service packs for that IDE nor for 2002.

Otis wrote:

Heh, no way, they'll ship in 2005. Yukon has to ship in 2005, so does vs.net, and it's possible, they're on track. MS is however very radical in this: if shipdates aren't met, features have to go. But I'm confident they'll make 2005. I also hope they will, 2003 really gets more annoying every day and as Dan Fernandez (VC# MP) told me: there is no-one working on service packs for that IDE nor for 2002.

You said it... I've got a Solution with 100+ projects including Enterprise Template projects and the IDE keeps unchecking the Configuration Manager "Build" checkbox... on selected projects every now & then. How bloody annoying is that .

Recently it has even started to throw exceptions and close... At least it performs an automatic save before each compile.

Marcus wrote:

Otis wrote:

Heh, no way, they'll ship in 2005. Yukon has to ship in 2005, so does vs.net, and it's possible, they're on track. MS is however very radical in this: if shipdates aren't met, features have to go. But I'm confident they'll make 2005. I also hope they will, 2003 really gets more annoying every day and as Dan Fernandez (VC# MP) told me: there is no-one working on service packs for that IDE nor for 2002.

You said it... I've got a Solution with 100+ projects including Enterprise Template projects and the IDE keeps unchecking the Configuration Manager "Build" checkbox... on selected projects every now & then. How bloody annoying is that .

aaaaaarg!!!

but.. 100+ projects? Why don't you chop it up into smaller pieces? There is a hotfix for the IDE btw, which solves some probs in large solutions: KB 822690

You have to call PSS but I think the fix will help you.

[quotenick="Otis"]

Marcus wrote:

There is a hotfix for the IDE btw, which solves some probs in large solutions: KB 822690

Will give it a try... but I really need to bite the bullet on that project and build a makefile using NAnt or something...

Does that fix also fix the fact that VS.NET doesn't always clean up properly between builds and leaves old versions of project outputs hanging around to mess with your head...

I have no idea what it fixes exactly, but I've heard it does fix problems with large solutions, i.e.: the problems no-one runs into unless your solution is really huge, like the one you're working with.

Most problems start when solutions grow beyond 30 projects or so. As you have over a 100, I'd chop up the solution into smaller ones, as most of the time you don't need the sourcecode of all projects into one solution.