---
title: "Comment by Dave Murray on \"How to use Nuget assembly as files with visual studio community\" | Hashnode"
description: "Hi. The class that your compiler doesn't recognise should have a red squigly line under it. Mouse over that class and a light bulb should appear with a tria"
url: "https://hashnode.com/posts/how-to-use-nuget-assembly-as-files-with-visual-studio-community/61d8f12640d7142927be744b/comment/61da17ff3c89a32a86818d4d"
---

[Discussion](https://hashnode.com/posts/how-to-use-nuget-assembly-as-files-with-visual-studio-community/61d8f12640d7142927be744b)

Comment [How to use Nuget assembly as files with visual studio community](https://hashnode.com/posts/how-to-use-nuget-assembly-as-files-with-visual-studio-community/61d8f12640d7142927be744b)

[Dave Murray](https://hashnode.com/@Irongut)

[Jan 8, 2022](https://hashnode.com/posts/how-to-use-nuget-assembly-as-files-with-visual-studio-community/61d8f12640d7142927be744b/comment/61da17ff3c89a32a86818d4d)

Hi. The class that your compiler doesn't recognise should have a red squigly line under it. Mouse over that class and a light bulb should appear with a triangle. Click the triangle and it will offer to add the relevant `using` statement if that is what is needed. If installing a Nuget package is needed it _may_ offer to install it and add the `using` statement.

If that doesn't work then right click your project or solution in the Solution Explorer and click **Manage Nuget Packages...** in the menu to open the Package Manager. On the **Browse** tab you can search for public Nuget packages, search for the package you need and click on it in the list. On the right you will now see the projects in your solution, click the checkbox next to the project you need to install it in and then click **Install**.

Clean & rebuild your solution (not always necessary but sometimes helps so I usually do it after installing a Nuget package) then try the light bulb again to add the required `using` statement.