
## Table of Contents

1. [Introduction](#introduction)
2. [Steps](#steps)
3. [Result](#result)
4. [Bonus: For Git Users](#bonus-for-git-users)
5. [Conclusion](#conclusion)

## Introduction

When you build a solution in Visual Studio, NuGet restores packages and downloads DLLs into a `packages` folder. You should **not** check these files into source control — they can be restored automatically, and committing them bloats your repository.

This guide shows how to properly ignore the NuGet `packages` folder when using **TFS (Team Foundation Server)** as your source control.

## Steps

### 1. Create the `.nuget` Folder

At the root of your Visual Studio solution, create a `.nuget` folder and add a `NuGet.config` file inside it.

### 2. Create the `.tfignore` File

At the root of your Visual Studio solution, create a `.tfignore` file.

Your solution structure should look like this:

```
MySolution/
├── .nuget/
│   └── NuGet.config
├── .tfignore
├── MySolution.sln
├── MyProject/
└── packages/          ← This folder will be ignored
```

### 3. Add `NuGet.config` Content

Inside `.nuget/NuGet.config`, add the following to disable source control integration for the packages folder:

```xml
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <solution>
    <add key="disableSourceControlIntegration" value="true" />
  </solution>
</configuration>
```

### 4. Add `.tfignore` Content

In the `.tfignore` file, add the packages folder path:

```
\packages
```

## Result

After adding these two files, when you check in your changes via TFS, files and folders under the `packages` directory will **no longer appear** in your Pending Changes window.

## Bonus: For Git Users

If you're using **Git** instead of TFS, add this line to your `.gitignore` file:

```
packages/
```

Most Visual Studio `.gitignore` templates already include this by default.

## Conclusion

| File           | Location              | Purpose                                   |
| -------------- | --------------------- | ----------------------------------------- |
| `NuGet.config` | `.nuget/NuGet.config` | Disables NuGet source control integration |
| `.tfignore`    | Solution root         | Tells TFS to ignore the `packages` folder |

This simple setup keeps your repository clean and avoids unnecessary package files in source control.


How to exclude the NuGet packages folder from source control in Visual Studio using .tfignore and NuGet.config.

A Tip for Ignoring NuGet Packages Folder in Visual Studio


## Table of Contents

- [Introduction](#introduction)
- [Install and Uninstall a Package](#install-and-uninstall-a-package)
- [Update a Package](#update-a-package)
- [Update Project by Defined Nuget File](#update-project-by-defined-nuget-file)
- [Install Nuget Package to All Projects](#install-nuget-package-to-all-projects)
- [Install Nuget Package to Certain Projects](#install-nuget-package-to-certain-projects)
- [Conclusion](#conclusion)

## Introduction

Nuget is a dependency management system for web development. If you use it, you'll already be familiar with the following commands.

## Install and Uninstall a Package

The first Nuget command is to install Angular, and the second one is to uninstall a Nuget package.

```
Install-Package angularjs -Version 1.4.6
```

```
UnInstall-Package angularjs
```

## Update a Package

Nuget actually has more useful commands, like the following. Update a particular package in a project to the latest version:

```
Update-Package jQuery -ProjectName MyProject
```

This command is very useful too because it is able to reinstall all the packages for a specific project.

```
Update-Package -ProjectName MyProject -reinstall
```

## Update Project by Defined Nuget File

```
Update-Package -ProjectName Pokemon.Shared -reinstall
```

```
update-package -reinstall -ignoreDependencies
```

## Install Nuget Package to All Projects

Install a Nuget package to all projects in the current solution:

```
Get-Project -All | Install-Package Autofac
```

## Install Nuget Package to Certain Projects

Install a Nuget package to specific projects in the current solution:

```
Get-Project ProjectA,ProjectB,ProjectC | Install-Package Autofac
```

For more commands, see the following links:

- Nuget Update command
- Nuget command line reference
- Package Manager Console Powershell Reference
- Nuget Create and Publish command

## Conclusion

Nuget provides a rich set of commands for managing packages in your .NET projects. From installing and uninstalling individual packages to batch operations across multiple projects, these commands can significantly streamline your dependency management workflow.


Nuget is a dependency management system for web development. If you use it, you'll already be familiar with the following commands. The first Nuget command is to install Angular, and the second one is to uninstall a Nuget package.

List of Useful Commands for Nuget


PM> Install-Package CSharpMongo.dll

Start create my own nuget dll, since I have worked with MongoDB a little bit.
So I'm trying to create useful library that I don't need to write code same
code at my different solution. Unlike the original or old deployment,
development, you'll chec-in your application's dependency dll. Nuget
development is different! You don't need to check-in the dependency dlls, you
will manage as package file which contains list of dependency dll of your
current projects.

So, when you build the solution of your visual studio, if you setup nuget
correctly, visual studio will go to network to download the necessary dll to
your local, by default should be inside the package folder. In additional, at
the end of the build, these dll will copy to your bin folder.

Following instructure is about how to manully deploy to nuget.

1. Register to get Nuget account

Anyway, this blog I try to write how to simple create your own nuget package.
First you need to go to nuget.org to register.

2. Make sure your application is build and able to deploy to nuget

You have to make sure your application is build successfully, so when people
get the dll by nuget won't break stuff. You should, think it as deploy to
Production.

3. Create and publish a package.

See here for publish nuget package.


NuGet

A Tip for Ignoring NuGet Packages Folder in Visual Studio

List of Useful Commands for Nuget

How to Create Your First Nuget Package