Please add support for MVC 6 projects

[weitzhandler]

Hi,

I tried adding the NuGet package (1.2.1) to my ASP.NET 5 MVC 6 (vNext) project, but looks like the project is doesn't support DNX.

Please update the projects frameworks.

Thanks

[JSkimming]

@weitzhandler I'm not familiar with how to target multiple frameworks in a class library, certainly not DNX. Do you know how?

If you submit a PR the build system, AppVeyor, will pick it up and build it. AppVeyor also provides a NuGet feed, so your PR can be included within you own project by referencing he build NuGet feed. See the readme for more details.

[weitzhandler]

@JSkimming I really don't know how to upgrade this, and anyway, MVC, is CTP stage, so it's alpha-beta version anyway.

And BTW, should we change the namespace to Microsoft.AspNet.Identity.EntityFramework.MultiTenancy, as in my code?

Here are the classes that match the ASP.NET MVC 6 class library. https://gist.github.com/weitzhandler/f9ebca6936ed0489d42d

[JSkimming]

@weitzhandler I'll have a look to see how to create multi targeted NuGet class libraries, it's the future so worth checking out.

Regarding namespaces, I dropped the Microsoft off the front, because this is not a Microsoft Library. And Multitenant vs MultiTenancy, well, does it make a difference? This is one of the two hardest things in computer science :smile:

To be honest, the merits of namespace changes are mostly moot, changing them would introduce a breaking change, that would mandate code changes on existing clients. Unless there's a hugely compelling reason to do so, I'm reluctant to change namespaces.

[weitzhandler]

Multitenant is actually a fair choice.

The reason I'd like to see the Microsoft prefix although this is not a MS product, is because I strongly believe this project should become part of the .NET foundation.

[JSkimming]

I know what you mean, I also feel this would be better supported in the Identity framework.

One benefit, of dropping the Microsoft off the front off this library, would mean the two libraries could work side-by-side to aid migration.

Microsoft often do this, they often try out a new library that's in a Microsoft.XXX namespace, then if they choose to move it to the core, they change it to System.XXX,

[weitzhandler]

@JSkimming That's not the case with the DNX and Core libraries. They will remain under Microsoft permanently. See this: https://github.com/aspnet/EntityFramework/issues/2665#issuecomment-124568413.