Hi Otis.

I installed the latest LLBLGen on one of our test server (Win 2003 Standard Server) yesterday.

LLBLGen could not open the DAL project file - it was giving some error about "possible version mismatch" the exception was raised out of mscorlib.

After uninstalling and installing LLBLGen again - that did not help - we did a windows update and found that the server was missing a critical update on the .Net Framework.

After installing the patch LLBLGen worked again..weird.

So this is possibly a bug with the latest release needing the critical patch but seeing that it worked after the critical update of the .net framework - it is propably not that important.

Hmmm. Did you get the crap with some Comparer class, which should have 1 member but had 0 or something?

Which patch did you install now, SP1 for .NET 1.1?

Otis wrote:

Hmmm. Did you get the crap with some Comparer class, which should have 1 member but had 0 or something?

Which patch did you install now, SP1 for .NET 1.1?

Yes, we got the crap message about the Comparer class which should have 1 member but had 0.

We installed the .Net 1.1 patch.

Seems like your compiler is making the new compiles dependant on the latest .net framework version. Not sure if this can be changed.

DId you have by any chance biztalk server 2004 or client installed on that box as well?

Nope.

Well, it's good to know there is a fix for this issue, as it pops up sometimes

It's not clear from this post whether or not it is the same problem as mentioned in another post (where SP1 was installed, the project was opened, and then SP1 was removed). Is the problem due to LLBLGen Pro requiring the SP? I can not/will not install SP on my machines for a while (until a magic number of the remote machines I deal with have installed it) so does this mean I shouldn't/can't install the latest updates for LLBLGen?

The original post doesn't say if that project file had previously been opened on a machine that had SP1 installed, just that SP1 corrected the issue.

sirshannon wrote:

It's not clear from this post whether or not it is the same problem as mentioned in another post (where SP1 was installed, the project was opened, and then SP1 was removed). Is the problem due to LLBLGen Pro requiring the SP? I can not/will not install SP on my machines for a while (until a magic number of the remote machines I deal with have installed it) so does this mean I shouldn't/can't install the latest updates for LLBLGen?

No, LLBLGen Pro doesn't require SP1 for .NET 1.1 because there are some issues with SP1 and I don't want to force SP1 on people.

The original post doesn't say if that project file had previously been opened on a machine that had SP1 installed, just that SP1 corrected the issue.

It's likely this is what happened: - project is created - sp1 is applied - project is opened, altered and saved - sp1 is removed - project is opened again -> causes error, as an assembly with a given version can't be found. - sp1 is applied again - project loads normally.

This is what happened to us:...

1. .Net 1.1 Patch applied on PC1.
2. LLBLGen Project altered and saved on PC1.
3. PC2 opens same LLBLGen Project as PC1 - open fails as PC2 does not have .Net 1.1 Patch
4. PC2 applies .Net 1.1 Patch
5. PC2 opens LLBLGen project - No Problem LLBLGen Works

Bottom line...

If one one of the dev Pc's that work with LLBLGen installs .Net 1.1 Patch then all Dev Pc's that work with LLBLGen project has to apply .Net 1.1 Patch.

@Otis:

I encounter the aforementioned error (mentioned also in these threads: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=1006 http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=1468 ) as well and would like to ask if you could send me the 'workaround' that comes in a dll to the following mail adress?

larsiuncle-llblgen@yahoo.de

I am using the following version of LLBLGen Pro: 1.0.2004.1 Final (September 24th, 2004)

Someone installed BizTalk Server 2004 since this project was last amended and now I cannot open it anymore. Would it help if I de-install BizTalk Server 2004 and try to open the LLBLGen project again? If so, would it effect my latest projects which were created/edited after the BizTalk Server 2004 was intalled?

Thank you very much in advance.

larsiuncle

If you install .NET 1.1 SP1 it should be fixed as well.. Could you try that please ?

Otis wrote:

If you install .NET 1.1 SP1 it should be fixed as well.. Could you try that please ?

But will that affect my projects that were created after the installation of BizTalk? I don't want one project to be running again while the others are not working then!

No, that will be ok.

The problem is this: in Biztalk server 2004 and .NET sp1 (same code), a private member was dropped from the stringcomparer class in .NET. As a .lgp file is a binary serialized blob, if it is created and saved on a machine without .NET sp1, it does have the member. When you then load such a project on a machine with .NET sp1 installed, the deserializer will load it, as it looks at what the class looks like, not what is read in the file.

The other way around won't work: if you save a project on a machine with .NET sp1 installed, it won't have the private member variable. Loading that project on a machine without SP1, will make the deserializer look at the stringcomparer class, see that there is a private member to deserialize but it's not in the filedata, so the error is thrown. Patching that machine with .NET sp1 will fix it, as the stringcomparer class will then not have the private membervariable and the deserializer will not bother about it.

Note: this is all .NET framework related. My code contains flexible deserializer code which can handle any version mismatch.

I did it the 'bad' way by re-creating my project since it contains only about 20 tables/views. Now it seems to work with the new code. Anyway, do you think I should install the SP1 in order to have the latest version of the .NET framework? You mentioned somewhere that there were 'some issues' with the SP1 and therefore you would not urge people to install it, right?

Thank you again.

It's is inevitable, as MS will assume everyone is on SP1. I read about some issues but I have to look them up as I can't remember them (are probably rare). vanilla .NET 1.1 also has a lot of issues, so it depends on what you prefer.