Frans,

In LLBLGen 2.0 are you going to add an option to the Project File Creater Task Performer to make it so...well im not sur ehow to explain this, but when you create a typed dataset there is a plus symbol next to the file, and you can click and it expands with other files....What i would like to see is an option to do this ( its easy, just add 2 extra xml elements to each file you want listed when expanded in the .csproj file) so that you could generate an entity along with a clean partial class of that entity for editing...i hope i made this clear enough that you understand me

At the moment it already generates partial classes for vs.net 2005, though there's just 1 file . If you want two files, just add one and you'll have the two files as one . But I know what you mean, and more 'partial classes aware code' is indeed planned. I'm not totally convinced having 2 files with generated code for an entity is the best option (like Customer.Sync.cs, Customer.Properties.cs etc. ) I think of Customer.Lgp.cs or similar, but I haven't decided yet. The generation configuration is going to change dramatically anyway so it will be much easier to config things.

i cant wait for this new version hehe

i was thinking alone the lines CustomerEntity.generated.cs would be equivalent to the current CustomerEntity.cs and then of course you could have just CustomerEntity.cs which is where users could add code Then you for sure know, Hey dont touch this file.

I could of course do this now, but with the current project task performer it doesnt add the "dependant" tag to CustomEntity.generated.cs in the project file so i dont get my nice organized drop down from CustomerEntity.cs

Any idea when the betas will start?

Answer wrote:

i cant wait for this new version hehe

i was thinking alone the lines CustomerEntity.generated.cs would be equivalent to the current CustomerEntity.cs and then of course you could have just CustomerEntity.cs which is where users could add code Then you for sure know, Hey dont touch this file.

That will pose the problem of overwriting crap, so I won't add that by default I think. If people want to organize it that way, great, but it's already easy to do manually. The generated name is indeed a good one

I could of course do this now, but with the current project task performer it doesnt add the "dependant" tag to CustomEntity.generated.cs in the project file so i dont get my nice organized drop down from CustomerEntity.cs

You could custom build the task performer of course (source is in the SDK )

Any idea when the betas will start?

Not for several months. Don't expect a beta before march 2006

Yeah, thats my next step, i wanted to find out when the betas were coming out for next version before i spent time custom making a project file performer ( i love having the source ) only to have to redo it again once new version is out...

If people want to organize it that way, great, but it's already easy to do manually. The generated name is indeed a good one

Is there way of making one code file dependant on another without manually editing the project file (.csproj)???

Answer wrote:

If people want to organize it that way, great, but it's already easy to do manually. The generated name is indeed a good one

Is there way of making one code file dependant on another without manually editing the project file (.csproj)???

No, as the file xml tag is added inside the projectfile task performer. So you have to add a small piece of code there.