Hi there

After having browsed the forums most of the night for a solution for this problem, I can see that I am not alone in this boat

Anyways, I have been using LLBLGenPro for 1½ years now for a big corporate VB.NET application with MSSQL, and now I am making a smaller project with MySql and would like to use LLBLGenPro here as well.

At first I had problems when trying to create the LLBL project and pressing the "test connection" button. It threw the exception that most other people here have posted as well. Then I tried installing the CoreLab version found at their website (4.50) and voila! it worked fine. Heck I could even compile my application and retrieve data from the MySql database.

But from experience I wanted to make sure that when releasing the application it can be run on a "clean" machine, so I copied the CoreLab.MySql and CoreLab.Data to a folder within the project and pointed all references in my solution to there - still I could compile and run the application. Then I tried to uninstall CoreLab and now I'm back to where I started (or well almost) because now I get the exception again

Could not load file or assembly 'CoreLab.MySql, Version=4.0.9.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I tried searching around to see if I could find where the reference is that I must have missed, but I can't really find it

• LLBL project - CoreLab.MySql
• LLBLDatabaseSpecific - CoreLab.MySql + CoreLab.Data

I have no way of installing CoreLab on the webserver that will initially run this application so I have to get all dll's included in the release package for it to work.

Any ideas where to look and what to do?

1- Place CoreLab.MySql.dll and CoreLab.Data.dll in the bin folder of your web project.

2- If you get an error message which says it can't find a specific version (eg. Version=4.0.9.0) of corelab while you have another version in the bin, then your application needs to have an assembly redirect from the version in the error message to the version you actually have.

1 - They already are (version 4.50.*)

2 - The thing is that the references from the LLBLDatabaseSpecific and all other projects within the website are all pointing at version 4.50.* and not the version 4.0.9.0 that the exception mentions? What exactly do you mean by an assembly redirect?

If I do a search in the whole project repository for "4.0.9.0" I find zero results in any files. Where is that hidden reference

1 - They already are (version 4.50.*)

2 - The thing is that the references from the LLBLDatabaseSpecific and all other projects within the website are all pointing at version 4.50.* and not the version 4.0.9.0 that the exception mentions?

Most probably that's the version referenced by LLBLGen Pro MySQLDQE dll. So you have 2 options: 1- Re-build the MySQLDQE dll after modifying the references to reference your 4.5 version 2- Use an assembly redirect. (sometimes you'll have to use option #1).

What exactly do you mean by an assembly redirect?

Some settings written in your application config file, to redirect any references to a version of an assembly to another available version of the same assembly.

eg.

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
     <assemblyIdentity name="CoreLab.MySql" culture="neutral"/>
     <bindingRedirect oldVersion="4.0.9.0" PublicKeyToken="09af7300eec23701" newVersion="4.5.0.0"/>
    </dependentAssembly>
</assemblyBinding>

Similar threads: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=11803 http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=10283

Sorry I haven't tried it out untill now, but I decided to keep CoreLab installed and to just develop the past few days

But now I unintalled it to give a whirl again.

I had just written the longest post to reveal my entire folder structure and reference pattern because I couldn't get it to work.

But in the end it worked out when I rebuild the MySqlDQE.dll and ORMSupportClasses.dll to point to the CoreLab version I have.

Thx alot for the always so very nice help here at LLBLGenPro!

Or maybe I was to fast there.

It works on my local machine wihtout having CoreLab installed (I did have a trial version installed, but removed it).

When I release it to the webserver I get a licensing error, do I need to have a CoreLab license besides my LLBLGenPro license?

Please cHeck the corelab docs for license errors in webapps. It's very crappy, how they've forced their licensing...

Thx got it working now, but still, do I need a CoreLab license to go along with LLBLGenPro to use MySql?

Right now the CoreLab.MySQL.dll is a trial version I found at their site.

Does the LLBLGenPro installation include that dll? I can't seem to find it.

ts_mjolner wrote:

Thx got it working now, but still, do I need a CoreLab license to go along with LLBLGenPro to use MySql?

Right now the CoreLab.MySQL.dll is a trial version I found at their site.

Does the LLBLGenPro installation include that dll? I can't seem to find it.

You need a license indeed. We don't distribute the dll, as you need a license to write an application using their provider.

Okay thx. Good thing the Dollar is at such a low right now

Hello,

I just downloaded llblgen 2.6 ( 10-jul-2008 )

And i buy the latest version of Corelab version 4.70.30.0

Like previous post ... local everything works fine. but when i publish my source to my host i get :

Could not load file or assembly 'CoreLab.MySql, Version=4.0.9.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

After that i found this forum topic on this problem.

And i investigate the sources in my Solutions Design folder.

I found somewhere that you can change the references there ... But i found out that they use the same versions of Corelab.

(So that is good news ... i got the same version of dll's.)

But my problem is still not fixed.

Sow this is what i have in my config file:

<assemblies>
        <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
        <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="CoreLab.MySql, Version=4.70.30.0, Culture=neutral, PublicKeyToken=09AF7300EEC23701"/>
        <add assembly="CoreLab.Data, Version=4.70.23.0, Culture=neutral, PublicKeyToken=09AF7300EEC23701"/>
</assemblies>

and some other place in the config file i have this:

<runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
                <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
                <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
            </dependentAssembly>
    
      <dependentAssembly>
        <assemblyIdentity name="CoreLab.MySql" PublicKeyToken="09af7300eec23701" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.70.30.0" newVersion="4.70.30.0"/>
      </dependentAssembly>
    

      <dependentAssembly>
        <assemblyIdentity name="CoreLab.Data" publicKeyToken="09af7300eec23701" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.70.30.0" newVersion="4.70.23.0"/>
      </dependentAssembly>
    
    </assemblyBinding>
    </runtime>

I use log4net to catch my exceptions.

Now i get always: Could not load file or assembly 'CoreLab.MySql, Version=4.0.9.0

I do not have the version of 4.0.9.0.

Can somebody tell me what i do wrong ?

because i would like to use version 4.70.23.0 of corelab.

thanks

Kris

Hello Kris

Have you tried examining the CoreLab.MySql.dll that you have distributed along with your application to the webserver?

I have had somewhat of the same problem where VS for some odd reason distributes a wrong version of that dll file when I publish my website. I never found out why it does this, I just replace the CoreLab.MySql.dll with the proper version after I've published my website and then it works.

Maybe this is your problem, maybe it's not

And i investigate the sources in my Solutions Design folder.

I found somewhere that you can change the references there ... But i found out that they use the same versions of Corelab

SD.LLBLGen.Pro.DQE.MySql.NET20 was built against (references): CoreLab.Data, Version=4.0.8.0 CoreLab.MySql, Version=3.20.7.0

So I think you should try to re-build it against the version in your possession. (As described earlier in this thread).

So I think you should try to re-build it against the version in your possession. (As described earlier in this thread).

Ok let's try.

This is what i did:

First install version 2.6 of llbl gen ( 10-jul-2008 ) Location C:\Program Files\Solutions Design\LLBLGen Pro v2.6

I installed Corelab my direct for .net. I has Corelab.Data version 4.70.23.0 and Corelab.Mysql version 4.70.30.0 Location C:\Program Files\CoreLab\MyDirect.NET2

I go to location: C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\Net2.x

There you can find LLBLGenProRuntimeLibraries 2.6.sln (and i open it)

Go to Project MySqlDQE and open AssemblyInfoDotNet20.cs

Remove this line: assembly: AssemblyKeyFile("C:\Myprojects\mystrongkey.key") and save the file.

Go to ORMSupportClasses and open all AssemblyInfo files located in the AssemblyInfo folder. again remove this line: _assembly: AssemblyKeyFile("C:\Myprojects\mystrongkey.key") _and save the file. (this will give otherwise an error)

I changed the reference of original CoreLab.Data.dll --> C:\Program Files\Common Files\CoreLab\Data Providers\4.70\Net2\CoreLab.Data.dll to _C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.Data.dll _

Now you can build the 2 projects:

• MySqlDQE
• ORMSupportClasses

Now i investigate the folder MySqlDQE.

There you can find make20.cmd. I go to my visual studio 2008 command prompt. en execute the bat file.

I get this result:

C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\N
et2.x\MySqlDQE>make20.cmd

C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\N
et2.x\MySqlDQE>mkdir DotNET2.0\bin
Er bestaat al een submap of bestand DotNET2.0\bin.

C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\N
et2.x\MySqlDQE>mkdir DotNET2.0\bin\v355
Er bestaat al een submap of bestand DotNET2.0\bin\v355.

C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\N
et2.x\MySqlDQE>nmake /nologo /f makefile_20 clean
        del /Q DotNET2.0\bin\SD.LLBLGen.Pro.DQE.MySql.NET20.*
Kan C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibrari
es\Net2.x\MySqlDQE\DotNET2.0\bin\SD.LLBLGen.Pro.DQE.MySql.NET20.* niet vinden

C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\N
et2.x\MySqlDQE>nmake /nologo /f makefile_20
        csc /t:library /out:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.MySql.NET20.dll /do
c:DotNET2.0\bin\SD.LLBLGen.Pro.DQE.MySql.NET20.xml /d:TRACE /o /lib:..\ORMSuppor
tClasses\bin\release /r:SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll,"C:\Program F
iles\CoreLab\MySQLDirect.NET2\CoreLab.MySql.dll","C:\Program Files\CoreLab\MySQL
Direct.NET2\CoreLab.Data.dll" AssemblyInfoDotNet20.cs DynamicQueryEngine.cs MySq
lSpecificCreator.cs
Microsoft (R) Visual C# 2008 Compiler version 3.5.21022.8
for Microsoft (R) .NET Framework version 3.5
Copyright (C) Microsoft Corporation. All rights reserved.

warning CS1668: Invalid search path 'C:\Program Files\\Microsoft
        SDKs\Windows\v6.0A\lib' specified in 'LIB environment variable' -- 'Het
        systeem kan het opgegeven pad niet vinden. '
error CS0006: Metadata file 'C:\Program
        Files\CoreLab\MySQLDirect.NET2\CoreLab.MySql.dll' could not be found
error CS0006: Metadata file 'C:\Program
        Files\CoreLab\MySQLDirect.NET2\CoreLab.Data.dll' could not be found
NMAKE : fatal error U1077: 'C:\WINDOWS\Microsoft.NET\Framework\v3.5\csc.EXE' : r
eturn code '0x1'
Stop.

C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\N
et2.x\MySqlDQE>nmake /nologo /f makefile_20 all355
        csc /t:library /out:DotNET2.0\bin\v355\SD.LLBLGen.Pro.DQE.MySql.NET20.dl
l /doc:DotNET2.0\bin\v355\SD.LLBLGen.Pro.DQE.MySql.NET20.xml /d:TRACE /o /lib:..
\ORMSupportClasses\bin\release /r:SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll,"C:
\Program Files\CoreLab\MySQLDirect.NET2_355\CoreLab.MySql.dll" AssemblyInfoDotNe
t20.cs DynamicQueryEngine.cs MySqlSpecificCreator.cs
Microsoft (R) Visual C# 2008 Compiler version 3.5.21022.8
for Microsoft (R) .NET Framework version 3.5
Copyright (C) Microsoft Corporation. All rights reserved.

warning CS1668: Invalid search path 'C:\Program Files\\Microsoft
        SDKs\Windows\v6.0A\lib' specified in 'LIB environment variable' -- 'Het
        systeem kan het opgegeven pad niet vinden. '
error CS0006: Metadata file 'C:\Program
        Files\CoreLab\MySQLDirect.NET2_355\CoreLab.MySql.dll' could not be found
NMAKE : fatal error U1077: 'C:\WINDOWS\Microsoft.NET\Framework\v3.5\csc.EXE' : r
eturn code '0x1'
Stop.

Now it's getting strange... i get these errors that my dll file does not exist at the location of the corelib.dll

Now i have some questions :

• Do we need the .bat files to build it with the right references ?
• Now that i can build manualy in visual studio where do i have to copy my dll's and what is the location to paste in

Now i am this far ... can anybody guide me further ?

Thanks,

Kris

Hi Kris

When I rebuilt mine using a new version of CoreLab, I did not use the .bat file. I just rightclicked the ORMSupportClasses and the MySqlDQE projects and rebuilt those.

The outcome dll's will then be found in the corresponding bin or bin/debug folders.

It's been a while since I did it, but I think I remember something about the outcome dll's had a slightly different name than the ones shipped with LLBGenPro, but then you just rename then accordingly.

Please check the steps in this post

Thanks for the post but i still get errors.

But first i write down what i did. In every thread you are talking about references. (it's the only thing i do wright now)

First of all: I build with succes 2 projects: * MySqlDQE * ORMSupportClasses Now i build first the ORMSupportClasses because the MySQLDQE has 1 reference to it.

(In the ORMSupportClasses are no changes to make about references.)

After the first build i removed 3 references in the MySqlDQE project.

• CoreLab.Data
• CoreLab.MySql
• ORMSupportClasses

And I create 3 new one's: 1) CoreLab.Data ==> C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.Data.dll 2) CoreLab.MySql ==> C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.MySql.dll 3) ORMSupportClasses ==> C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\Net2.x\ORMSupportClasses\bin\Release\SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll

First i did clean and after that i build in release mode. No problems so far.

Ok Next step is create my new project where i need the new created fresh dll's.

Just 1 simple ASP.NET page (inside Web application 3.5)

Default page has a button and label. the butten will update the label with some data retrieved from the database. (If it works LOL)

Now when i compile with the new ddl references to my new project i get this 6 Errors:

Error   1   The type 'SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase' is defined in an assembly that is not referenced. You must add a reference to assembly 'SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.6.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27'.   E:\Projects\corelabDLLTest\CorelabDLL\Default.aspx.cs   44  17  CorelabDLL

Error   2   The type 'SD.LLBLGen.Pro.ORMSupportClasses.EntityBase2' is defined in an assembly that is not referenced. You must add a reference to assembly 'SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.6.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27'. E:\Projects\corelabDLLTest\CorelabDLL\Default.aspx.cs   46  17  CorelabDLL

Error   3   The type 'SD.LLBLGen.Pro.ORMSupportClasses.IEntityFields2' is defined in an assembly that is not referenced. You must add a reference to assembly 'SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.6.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27'.  E:\Projects\corelabDLLTest\CorelabDLL\Default.aspx.cs   46  17  CorelabDLL

Error   4   The type 'SD.LLBLGen.Pro.ORMSupportClasses.IValidator' is defined in an assembly that is not referenced. You must add a reference to assembly 'SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.6.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27'.  E:\Projects\corelabDLLTest\CorelabDLL\Default.aspx.cs   46  17  CorelabDLL

Error   5   'LeMoustique.DAL.DatabaseSpecific.DataAccessAdapter' does not contain a definition for 'FetchEntity' and no extension method 'FetchEntity' accepting a first argument of type 'LeMoustique.DAL.DatabaseSpecific.DataAccessAdapter' could be found (are you missing a using directive or an assembly reference?) E:\Projects\corelabDLLTest\CorelabDLL\Default.aspx.cs   47  21  CorelabDLL

Error   6   'LeMoustique.DAL.DatabaseSpecific.DataAccessAdapter' does not contain a definition for 'Dispose' and no extension method 'Dispose' accepting a first argument of type 'LeMoustique.DAL.DatabaseSpecific.DataAccessAdapter' could be found (are you missing a using directive or an assembly reference?) E:\Projects\corelabDLLTest\CorelabDLL\Default.aspx.cs   49  21  CorelabDLL

This is the code from the cs file: protected void Button2_Click(object sender, EventArgs e) { try { DataAccessAdapter DAA = new DataAccessAdapter(); int nr = Convert.ToInt32(TextBox1.Text); UsersEntity UE = new UsersEntity(nr); DAA.FetchEntity(UE);

            DAA.Dispose();

            Label2.Text = "hello " + UE.FirstName + " " + UE.LastName;
        }
        catch (Exception ex)
        {

            log.Fatal(ex.Message);
        }
    }

• Now i deleted my references and created all 3 again in (LLBLGenProRuntimeLibraries 2.6)
• Removed existing data from Bin folder.(LLBLGenProRuntimeLibraries 2.6)
• Build with succes. for .net Framework 2.0

after that: - Created new web application 3.5 and added 4 references:

1) added CoreLab.Data ==> C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.Data.dll in the DBSpecific project.

2) CoreLab.Data ==> C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.Data.dll 2) CoreLab.MySql ==> C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.MySql.dll 3) ORMSupportClasses ==> C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Sourcecode\RuntimeLibraries\Net2.x\ORMSupportClasses\bin\Release\SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll

• cleaned up before build and i still get errors.

Now correct me if i did something wrong or forget something.

Are there other references i need to make ?

TBC

Kris

About the original error: CoreLab installs a policy assembly as well to redirect references from 4.* to 4.50. Because you just copied over the assemblies, you don't have that policy assembly in the gac, so references to an earlier version aren't redirected. Uninstalling has that effect: the policy file is removed.

To overcome this, you can add an assembly redirect yourself to the application's .config file:

<configuration>
  <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="CoreLab.Data" publicKeyToken="09af7300eec23701" culture="neutral"/>
            <bindingRedirect oldVersion="4.0.0.0-4.49.9.9" newVersion="4.50.0.0"/>
         </dependentAssembly>
      </assemblyBinding>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="CoreLab.MySql" publicKeyToken="09af7300eec23701" culture="neutral"/>
            <bindingRedirect oldVersion="4.0.0.0-4.49.9.9" newVersion="4.50.0.0"/>
         </dependentAssembly>
      </assemblyBinding>
  </runtime>
</configuration>

or something like that. Use reflector to get the real version numbers of the corelab data/mysql dlls you're using.

Ok, i found where my reference where wrong.

So i create new dll files:

• SD.LLBLGen.Pro.DQE.MySql.NET20.dll
• SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll

I have no compile errors.

I use these files with llblgen.

But when i generate files for my project i get this error: Error 1 The type or namespace name 'DQE' does not exist in the namespace 'SD.LLBLGen.Pro' (are you missing an assembly reference?)

Now what is wrong ...

It's just a using, an i look if some name is change instead of DQE .. but no result there.

using SD.LLBLGen.Pro.ORMSupportClasses; using SD.LLBLGen.Pro.DQE.MySql;

and yes, Reflector is a great tool to view your created dll's.

thanks for the info... but can somebody help me out with this problem ?

Kris

But when i generate files for my project i get this error: Error 1 The type or namespace name 'DQE' does not exist in the namespace 'SD.LLBLGen.Pro' (are you missing an assembly reference?)

Compiling which project gave you this error?

That compile error comes from the fact that most probably you didn't add a reference or that you reference two different versions of the same dll file (one is the original for example, and one is the custom build you've made).

I got it to work.

Remove all references. and Created again with the correct references dll's.

Compiled the project again.

Generated the project in llbl gen.

Remove and added references to my personal project.

Compiled my personal project.

And it works .

Thanks for the support.

I think the assembly redirect with the official dlls is IMHO a better solution (as you now have to recompile the dlls every time), the redirects I posted, didn't they work for you?

Nope it did not work with the assembly redirect.

If i have some time left on my project i try to get it to work with assembly redirect.

I will send some small application if you like to show the problem.

Kris

If references don't work, and fuslogvw.exe (.net sdk folder) isn't giving any details, also consider discussing this with corelab (which is called devart these days).

Hello again,

I have found some time to test again with the corelab dll.

And now i used a newer version (4.85.35.0) of Corelab and it works !!

Here is what i used in my config file.

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="CoreLab.Data" publicKeyToken="09af7300eec23701" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-4.70.23.0" newVersion="4.70.24.0"/>
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="CoreLab.MySql" publicKeyToken="09af7300eec23701" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-4.85.35.0" newVersion="4.85.36.0"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime> 

Good news ...

greets

Kris