Visual Studio 2015 CTP 6, LLBL 4.1

Trying to see what's involved in moving to asp.net 5 and so far I feel like I'm dead in the water. Referencing stuff in vNext seems to have been turned completely inside out and nothing works now. I tried creating an asp.net 5 class library project and then referencing the nugget llbl 4.2 libraries, but a bazillion errors.

Has anybody got LLBL working inside an asp.net 5 solution?

Admin-Please edit title, should say asp.net 5

Which LLBLGen libraries did you reference? Could you please provide an example of these errors?

"SD.LLBLGen.Pro.DQE.SqlServer": "4.2.20150303.0", "SD.LLBLGen.Pro.ORMSupportClasses": "4.2.20150303.0"

1>D:\Source\Applications\Websites\WebApplication1\src\BusinessObjects\DatabaseGeneric\FactoryClasses\EntityFactories.cs(713,15): ASP.NET 5.0 error CS0534: 'ElementCreator' does not implement inherited abstract member 'ElementCreatorBase.CreateDynamicRelation(IEntityFieldCore, JoinHint, DerivedTableDefinition, string, IPredicate)'

Keep in mind, I can't the project as generated by LLBL to be seen by asp.net 5 so I had to create a new asp.net 5 class library and copy all the generated source (from 4.1) over.

Is there anything special that is needed to get llbl working in an asp.net project? Do you have any docs, step, anything to help get it working? Any working sample app that I could download to pick apart to see what I have wrong?

AFAIK, asp.net 5 and .net core are not officially supported yet. From Microsoft's site, it seems that it has backwards compatibility for older .net versions. I never tried though, so I will wait and see what happens to that VSNet approach.

there are two versions of asp.net v5: one for .net full (.net 4.6) and .net core. The one for .net full v4.6 should be able to use our runtimes. The one for .net core isn't as .net core is a different runtime/framework, and we need to port our runtime to .net core. At the moment we can't do that as there's no real ado.net framework released yet for .net core.

.net full v4.6 isn't available so I assume you're trying asp.net 5 on .net core. You can forget that at this point: ado.net is completely broken at this point for .net core. EF7 dev uses a private build sqlclient but there's no OSS ado.net provider/common available yet, so how it works is not even known: there is dbproviderfactory planned but I don't think they really have a clue what they're doing w.r.t. ado.net. For one: where to define the factories if every app has its own runtime (no machine.config!)? They don't plan to include dbdataadapter/dataset/datatable (and thus also no datareader.GetSchemaTable()) so there are serious limitations in this api.

So TL;DR: it should be possible (when it's released) to use our runtime on .net full 4.6 and asp.net 5 on .net full 4.6. If new project file formats are needed we obviously will provide those. Support for .NET core is currently not planned for .net core v1.0 release (the EF team also has said their initial release on .net core will be very limited, which is no surprise, there's barely an ADO.NET design/api formulated yet!)

I understand the difference between asp.net 5 core and full. When I originally added the references to the existing llbl projects, the references were added to a frameworks.aspnet50 section, not the aspnetcore50. I'm not wanting to use core, I want to use full, but I am confused as to what this ctp build is actually using as nowhere do I see how to pick what I want to target. I guess it's only support core.

To my knowledge it indeed only supports core (and it's currently broken in a lot of places).