-LLBL 2.6 final. -VS 2008, C# -MS Sql 2005 -SubVersion 1.6

We're using the Subversion as the source control in our project.

Any time we add/change any column to a table and generate the code all the files are found to be changed when change should be only in the files related to the tables changed.

When I did the diff to see the difference between the old and new files there were none, other than some spaces and some extra lines.

So when we have to commit all of the generated files again to repository whenever we make little change in some tables. Is there any properties that we can set in LLBL so that other files dont get changed ?

Thanks Shekhar

HI Shekhar,

When you generate code in LLBLGen, All files are generated even if they didn't change. That is for code consistency. Now, the reason SVN sees all files changed is coz the DateAndTime impressed in the header of the files.

You must set the **TdlEmitTimeDateInOutputFiles **flag to false at Propject properties/User Preferences.

Hope helpful.

daelmo wrote:

HI Shekhar,

When you generate code in LLBLGen, All files are generated even if they didn't change. That is for code consistency. Now, the reason SVN sees all files changed is coz the DateAndTime impressed in the header of the files.

You must set the **TdlEmitTimeDateInOutputFiles **flag to false at Propject properties/User Preferences.

Hope helpful.

Thanks, Daelmo, I already set that to false, but there were some extra lines and spaces detected as difference. I need to check that with mutiple generations and then I will let you know.

If possible, also download the latest LLBLGen Full Instaler, as I think some changes about this were made.

It's only the second time that differences are found. This is indeed unfortunate, we did fix some of them, but we had to postpone another one because it's a breaking change. So the second time will look different, the 3rd shouldn't.

Otis wrote:

It's only the second time that differences are found. This is indeed unfortunate, we did fix some of them, but we had to postpone another one because it's a breaking change. So the second time will look different, the 3rd shouldn't.

Otis, Yeah! that one is true, the third and next generation seems to be working. The thing is, everyday we have to start file generation from the begining and go through the 2nd time and face the issue. Now we've just noticed it only happens 2nd time.

Can't wait to have new fixed version installed.

Thankyou