After having a very traumatic experience with my laptop drive failing AND my backup drive failing at the same time.. I am back with more corrections :-)

Its taken a bit to re-motivate myself to rebuild my app.

So on page http://www.llblgen.com/documentation/2.6/Using%20the%20generated%20code/gencode_auditing.htm

There is an example for Auditing.

There is a line **auditInfo.ActionType **. If you look at the Audit Demo application, its script uses **AuditActionTypeId **. One or the other should be adjusted a few pixels.

also on page : http://www.llblgen.com/documentation/2.6/Using%20the%20generated%20code/gencode_usingdi.htm

The version # should be corrected.

<section name="dependencyInjectionInformation" type="SD.LLBLGen.Pro.ORMSupportClasses.DependencyInjectionSectionHandler, SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27"/>

soon that # might be a 3.0.0 ??? perhaps? maybe to be found under the christmas tree ?

quentinjs wrote:

After having a very traumatic experience with my laptop drive failing AND my backup drive failing at the same time.. I am back with more corrections :-)

Hehe. Morphy

quentinjs wrote:

So on page http://www.llblgen.com/documentation/2.6/Using%20the%20generated%20code/gencode_auditing.htm

There is an example for Auditing.

There is a line **auditInfo.ActionType **. If you look at the Audit Demo application, its script uses **AuditActionTypeId **. One or the other should be adjusted a few pixels.

The example uses another name for the field name, that's not big deal. The documentation code snippet doesn't intend to be exactly the same as the example, and vice-versa. So, you can name the field as you want. As a matter of fact you can do whatever you want inside your audit logic

quentinjs wrote:

also on page : http://www.llblgen.com/documentation/2.6/Using%20the%20generated%20code/gencode_usingdi.htm

The version # should be corrected.

<section name="dependencyInjectionInformation" type="SD.LLBLGen.Pro.ORMSupportClasses.DependencyInjectionSectionHandler, SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27"/>

You're right it should be 2.6.0.0

quentinjs wrote:

soon that # might be a 3.0.0 ??? perhaps? maybe to be found under the christmas tree ?

've been a good boy developer? All we are waiting for that great release

Thanks for your corrections.

In january, not christmas.

Will take care of the corrections

Then I will look under my tree on Ukranian Christmas then

Its okay if its not gift wrapped.

quentinjs wrote:

Then I will look under my tree on Ukranian Christmas then Its okay if its not gift wrapped.

heh It's indeed in january but still a little early, I'm afraid. We target january, but likely late january, as we need to implement changes to the runtime but it's unclear how long this will take: it's likely we complete the work in january on time, however if an unforeseen problem pops up we might slip a few weeks. But things look ok at the moment. (but not january 7th )

(I corrected the typo, btw. Next build.)

For those interested in my computer hiccups. Lost yet-another-drive, otr at the very least the OS is now MIA.. How does an Operating system go missing, I have no idea, but I've only had this new machine 2 weeks, so its not something I'd have expected.

so Ukranian Christmas is out then, ah well I was hoping...