Fix #33 & #32 - building site.min.js and site.min.css for release builds and Append version for included styles

[ghost]

No description provided.

[maraf]

Thanks a lot, @nicotravassos!

Looks good to me, but I would like to discuss one thing:

Is there any benefit in using attribute names on environment instead of include and exclude? When I generate a new ASP.NET Core site from official template, it uses include and exclude.

[ghost]

Hello @maraf,

names accepts a single hosting environment name or a comma-separated list of hosting environment names that trigger the rendering of the enclosed content.

include & exclude attributes control rendering the enclosed content based on the included or excluded hosting environment names.

Please see this asp-net-core-environment-tag-helper

It seems names was used in ASPNETCORE 1 and include and exclude ASPNETCORE 2 see environment-taghelper-exclude-and-include-attributes-in-asp-net-core-2

You can always exclude it from the pull-request 😄

[maraf]

So, please remove the change regarding include/exclude replacement and I'm going to merge it.

[ghost]

@maraf,

Sorry about all the random commits my brain is not in a right place right now. I have removed Staging and Production will add this in next pull request when I implement bootstrap layout.