Install-package Fontawesome Free

Install-Package Mvc.RazorTools.FontAwesome which has installed fine and i now have the.css added to content and the appstart - razor tools - fontawesome.cs added I have added the following to the top of my layout; @Styles.Render('/Content/ fontawesom e') and then tried the following inside the page @Html.FontAwesome(FontAwes omeIconSet.Star). NuGet.NET CLI Paket CLIR Direct Download. Install-Package FontAwesome.Sharp. Dotnet add package FontAwesome.Sharp. Paket add FontAwesome.Sharp. FontAwesome.Sharp Download (Unzip the 'nupkg' after downloading). Install-Package Font.Awesome -Version 5.8.2. Font awesome FontAwesome FortAwesome. Got questions about NuGet or the NuGet Gallery?

Microsoft is doing a good job in shipping standard front-end libraries with Visual Studio 2012 “ASP.NET MVC 4 Web Application” and “ASP.NET Web Forms Application” templates, they are raising the bar for the .NET web developers.

The VS template is a good starting base, however, I have been adding the libraries of this post to every new web project, they act as a completion to the ones shipped with VS and I wanted to share them with you.

1 – CSS Normalizer

One common problem we used to face is the fact that every browser has different default settings. If you don’t explicitly style an element (a tag), it may not look the same cross-browsers.

The image above shows the following code with and without resetting:

Today, the de facto CSS resetting tool is Normalize.css, it does much more than my demo above to target cross-browsers differences. Quoting the authors: Normalize.css makes browsers render all elements more consistently and in line with modern standards. It precisely targets only the styles that need normalizing.

N.B. Normalize is meant to replace what was called as “CSS Reset” so, never call it “Reset” or you will be accused of being uncool!


Nuget: PM> Install-Package normalize.css

Recuva free download offline installer. CDN:

2 – HTML5 on legacy IE Browsers

It is a shame that IE versions prior to IE9 will not recognise HTML5 new elements such as <nav>. However, fear not, html5shiv to the rescue. You can use it in the document <head> like this:

If you are using Modernizr then it does contain the html5shiv and you do not need to reference it separately, unless you have downloaded a custom version of Modernizr. Modernizr that comes with VS 2012 web templates already has html5shiv.


Nuget: PM> Install-Package html5shiv


3 – CSS Generators

CSS has to maintain backward compatibility, it cannot break the web. CSS is verbose and not DRY.

LESS and SASS are two popular CSS generators, they use more modern language that will render plain old CSS when compiled.


The web is divided on which is better LESS, SASS or not using a generator at all. I am personally with the LESS generator as it is straight forward to learn and covers the gaps of CSS, such as the lack of variables, rather than replacing it with completely new syntax. Here is a very simple example that would give you a flavour of LESS:

This will compile to the following CSS:

I use this wonderful Visual Studio 2012 plugin to compile LESS to CSS the moment I hit Save : Web Essentials 2012. You can use it to compile SASS as well, but I never tried it for SASS.

Websites: & The websites contain good tutorials that will get you up to speed.

Online LESS Compiler (for learning purpose):

4 – Icon Fonts

A new trend in the web has started recently which is using font for icons (well, I am saying started, however, Webdings came in 1997). The icons are vector graphics which means they will scale well at any size and on any platform (in theory), such as the mobile platform. They are quite useful for menus, bottoms, forms and whenever you want to break the text silence with a small icon. They speed up your site and your design process.

Npm Fontawesome Free

There are plenty of font icons, just Google it, my favourite is Font Awesome, here is an example of using it:


Nuget: PM> Install-Package FontAwesome

5 – CSS Frameworks

If you’ve reached so far, then congratulations, here is the ultimate library that will save you time and will make you deliver faster.

A CSS Framework is meant to get you up to speed with the basic stuff that you do every time you start a new website. Things like normalizing CSS (check point 1 of this post), setting padding and margins, forms design, making your site responsive (reacts well when resized to mobile and slate devices), animation, cool buttons, modal dialogs, font icons (check point 4 of this post), they rely on CSS generators (check point 3), modern alerts, and more!

There are hundreds of CSS frameworks some of them are generic and some of them focus on certain areas (such as being more responsive or have special features for the mobile), the top competing two are Twitter Bootstrap and Zurb Foundation. A complete comparison between the two is beyond the scope of this post (Google “Bootstrap vs Foundation” and enjoy), here are some quick points:

  • Twitter Bootstrap is more popular due to the brand and the amount of plugins.
  • Zurb Foundation has better layout grid, however, at the time of this writing, Bootstrap is preparing for a new grid in release 3 which is currently in beta.
  • Bootstrap uses LESS (review point 3).
  • Foundation uses SASS.
  • Both use CSS3 and jQuery.
  • While you can’t compare them like-to-like, using one of them will cancel the need to use jQuery UI (I am talking about jQuery UI and not jQuery).

You could even find free and commercial templates based on these two framework that will definitely save you more time, especially if the project is a low-budget and/or for intranet use. This is a popular Bootstrap templates site {wrap}bootstrap.

There is much more to say about CSS frameworks, but the point here is to get you interested versus being a tutorial or a reference.

Websites: &

Nuget: PM> Install-Package Twitter.Bootstrap.Less & PM> Install-Package Foundation4.MVC4


DRY and don’t reinvent the wheel are the points I wanted to make by this post. I hope I did highlight at least one library you didn’t know about and I hope that will make your day, please feel free to mention more libraries that you think are missing, in comments.

Note: Before continuing please make sure that you already have a Blazor project created. If not please go to the official Blazor site and learn how to create one.

Blazorise is designed to work with different CSS frameworks. Each of the supported CSS framework is defined by a different NuGet package. Please see the usage page to find a list of supported frameworks and how to use them.

The setup process is similar for all of the supported frameworks, you will just replace Bootstrap sources with the one you need.



1. NuGet packages

First step is to install a Bootstrap provider for Blazorise:

You also need to install the icon package:

2. Source files

The next step is to change your index.html or _Host.cshtml file and include the CSS and JS source files:

Note: When Blazor project is created it will also include it’s own Bootstrap and FontAwesome files that can sometime be of older versions. To ensure we’re using the appropriate bootstrap and FontAwesome files, you need remove them or replace them with the links from above. If you forget to remove them it’s possible that some components will not work as expected.

3. Using’s

In your main _Imports.razor add:

Install-package Font Awesome Free Download

4. Registrations

Starting from .Net Core 3.2 there was some changes regarding the setup process for Blazor WebAssembly project types. Specifically the Startup.cs file is removed and all registrations are now done in the Program.cs.

Depending on the hosting model of your Blazor project you only need to apply either step 4.a or 4.b. You should not include both of them as that is generally not supported.

To Learn more about the different project types you can go to the official documentation.

4.a Blazor WebAssembly

This step is mandatory for Blazor WebAssembly(client-side) and also for ASP.NET Core hosted project types. You should place the code into the Program.cs of your client project.

4.b Blazor Server

This step is going only into the Startup.cs of your Blazor Server project.