The 2.6 assemblies don't seem to be compatible. Is there DynamicData support with V3?

The dyanmicData assembly isn't ported to V3 yet. However you can make it work:

1. Follow all steps in the readme.txt, use all references from LLBLGen V3, except of course the SD.LLBLGen.Pro.DynamicDataSupportClasses.NET35.dll (that only exist for v2.6)

2. In your LLBLGen DynamicData project, add these redirects in the web.config:

<runtime>
...
      <assemblyIdentity name="SD.LLBLGen.Pro.LinqSupportClasses.NET35" publicKeyToken="ca73b74ba4e3ff27"/>
      <bindingRedirect oldVersion="2.6.0.0-2.6.0.0" newVersion="3.0.0.0"/>
    </dependentAssembly>
    <dependentAssembly>
      <assemblyIdentity name="SD.LLBLGen.Pro.ORMSupportClasses.NET20" publicKeyToken="ca73b74ba4e3ff27"/>
      <bindingRedirect oldVersion="2.6.0.0-2.6.0.0" newVersion="3.0.0.0"/>
    </dependentAssembly>
    </assemblyBinding>
</runtime>

I'm trying to get Dynamic Data SD.LLBLGen.Pro.DynamicDataSupportClasses.NET35.dll working with LLBL v3.1. Is it possible?

I got wollowing error: Could not load file or assembly 'SD.LLBLGen.Pro.LinqSupportClasses.NET35, Version=2.6.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

  <runtime>
    <assemblyBinding>
      <dependentAssembly>
        <assemblyIdentity name="SD.LLBLGen.Pro.LinqSupportClasses.NET35" publicKeyToken="ca73b74ba4e3ff27"/>
        <bindingRedirect oldVersion="2.6.0.0-2.6.0.0" newVersion="3.1.0.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="SD.LLBLGen.Pro.ORMSupportClasses.NET20" publicKeyToken="ca73b74ba4e3ff27"/>
        <bindingRedirect oldVersion="2.6.0.0-2.6.0.0" newVersion="3.1.0.0"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

**Edit: ** I forgot xmlns: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> Works now.

But another question: Some time ago I have read about some plans about releasing source codes for Dynamic Data Support Classes. What about it? I had been working with DD quite a lot in v2.6. There were some issues with the metadata provider. Now i'm trying to start new project with asp.net 4 (new DD engine) and It would be nice to be sure I could fix possible issues. It's important to us as we have to decide between Entity Framework Runtime and LLBLGen Pro Runtime

I don't recall seeing anywhere about us releasing the code for DynamicData, but I'll check for you, and we'll get back to you.

Matt

We have no plans to port it to v3 at this point, as DynamicData is a moving target: it's unclear whether it's supported in the future by Microsoft (as the team who initially wrote it is now working on other things, like nuget). We can't support every framework MS cooks up and abandons a year later. I am aware of the fact that it is still 'available' from MS but as MS has made no publication about it in the past year or so, not a lot of people know about the framework.

That said, you have a great point about the sourcecode not being available. We'll upload that sourcecode right away to the v2.6 customer area. Just a minute.

I uploaded the sourcecode and the vs.net package source into 1 archive. It's in the v2.6 -> Extras section in the customer area. This should make it possible to simply re-compile the code to use it with v3.x. As said, we don't support it anymore and from the looks of it, neither does MS.

Otis wrote:

I uploaded the sourcecode and the vs.net package source into 1 archive. It's in the v2.6 -> Extras section in the customer area. This should make it possible to simply re-compile the code to use it with v3.x. As said, we don't support it anymore and from the looks of it, neither does MS.

Thanks for that - I just has a play with it with v3.1 and there are a few quirks that need ironing out so I'll want to make changes to the source code. Given that you don't support it anymore do you mind if I put my source modifications in my codeplex project?

Sure go ahead.

Let me know the exact url, so I can add it to the list of open source on our main site If I need to alter the license on the sourcecode, let me know too.

talking about codeplex and sourcecode, we'll fork your LinqPad driver (which is buried inside a bigger project) and include it with v3.5. Of course you'll get full credit. We have to see whether we ship it as sourcecode (if the license is too restrictive) or binary only. This way more people will be able to use it as it's installed by default.

Codeplex is incredibly slow at the moment (<20KB / sec), so I couldn't pull the full sourcecode (31mb) of the complete project with the linqpad driver. As far as I could see the linqpad driver still contains a tremendous amount of code. Is all that necessary to make it work with linqpad? (like: it needs to get a complete model?) If so, I can help with that, as I've done this 3 (or even more) times already for various frameworks (Dyn. data, ria services, and now with OData) so I think I can optimize it properly with code borrowed from one or all three. (so no reflection necessary)

Is there a separate project for the linqpad driver or do I need the complete 31 MB of code and cut it out of it?

Otis wrote:

Sure go ahead.

Let me know the exact url, so I can add it to the list of open source on our main site If I need to alter the license on the sourcecode, let me know too.

Will do, thanks.

Otis wrote:

talking about codeplex and sourcecode, we'll fork your LinqPad driver (which is buried inside a bigger project) and include it with v3.5. Of course you'll get full credit. We have to see whether we ship it as sourcecode (if the license is too restrictive) or binary only. This way more people will be able to use it as it's installed by default.

I've replied to that back in the LinqPad thread http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=15083