markoh

This has been opened on dotless repo too but no reply yet. I agree we should look for an alternative compiler to dotless coz it seems they'll be unable to...

I'll guess and say he's probably talking about these two settings that are required for the "old" membership providers to work in ASP.NET MVC 4: ``` ```

Hey @FransBouma so it's been 2 years, do you think Massive will ever get ported to .NET Core (which has also come a long way since then)? It'd be very...

Attached are the results of the .NET Portability analyzer and those are quite encouraging that a port is likely feasible [ApiPortAnalysis(4).xlsx](https://github.com/FransBouma/Massive/files/2893862/ApiPortAnalysis.4.xlsx)

@FransBouma For my own needs I migrated everything to .net core 2.2 today and it was (almost) straightforward besides some issues with Nuget packages and tests. Feel free to take...

I will but I still have some issues. Most of migration went fine but I had to install the System.Configuration.ConfigurationManager Nuget to support the old way configuration loading. Since Massive...

@FransBouma oic, it is something you've been faced with already https://github.com/dotnet/corefx/issues/4571 What do you suggest, how should we proceed?

Couple of things: 1. What if the current Massive v2 would be kept for .NET Full compatibility and new version was introduced to support .NET Core (eliminating the need for...

Also, what about an option which Rick Strahl discusses, to have specialized assemblies using the required provider factory. Massive already has specialized assemblies/projects, albeit in the same namespace but I...

Just a note. I was able to get it working by adding just the following line to register the factory to my static void Main() in Program.cs of the asp.net...