AddOrchardCms overload with a configure action.

[jtkech]

Here i also suggest to re-introduce this line in OC.Cms.Web.csproj so that it fixes #1156.

<MvcRazorExcludeRefAssembliesFromPublish>false</MvcRazorExcludeRefAssembliesFromPublish>

Normally we don't need it but if a module didn't use the Sdk.Razor and / or forgot a direct reference to Microsoft.AspNetCore.Mvc, its views are not precompiled and then this line is needed. This because its views will be compiled at runtime, so the refs folder with compilation libraries needs to be generated when publishing the application. So, let me know.

[sebastienros]

I reverted the change that was not necessary.

[sebastienros]

Why?

[jtkech]

@sebastienros

• So, i confirm that we still need to publish razor pages (not views) defined by the application even if they are precompiled. It is required to be found and selected by mvc even if the file only contains a @page (which is required) directive which proves that at the end this is the precompiled page which is used.

• Then i was also publishing the razor views imported as Linked Items in the application which were not precompiled by the old tool. But i assume that it is done by the new Sdk.Razor, so i removed this part. Anyway for this case we would need to publish again the refs folder that we decided not to do.

• Update There is also PreserveCompilationContext = true which is also related to razor compilation at runtime, but we need it while in dev mode. But just saw that now Sdk.Web set it to true by default. So i also removed this line from our web applications project files.

• The last case i didn't tried is a razor page (not a view) imported as a Linked Item in the application. But it's too much ;)

Otherwise this PR is ready.

[sebastienros]

FYI dotnet/AspNetCore.Docs#6746