
## Table of Contents

1. [Introduction](#introduction)
2. [Common Issue with Git in Visual Studio](#common-issue-with-git-in-visual-studio)
3. [Conclusion](#conclusion)

## Introduction

This post covers a common issue encountered when using Git within Visual Studio and provides steps to resolve it.

## Common Issue with Git in Visual Studio

### Merge or Commit Error

If you're using Visual Studio's Git merge to merge code from a source branch to a target branch and there are new commits on the target branch, you might see the following error:

```
An error occurred. Detailed message: 2 uncommitted changes would be overwritten by merge
```

You'll probably still see this error after trying to pull from the target branch a couple of times. I think this might be a bug when using Visual Studio's Git integration, but some people say it might be caused by a locked file. Either way, it is something that should work, but Git in Visual Studio is not handling it correctly. The following are fixes I have tried that work so far:

1. After checking out the target branch, always pull first, then perform other operations like merge or push.

2. Although #1 should work most of the time, if you forgot to pull or even after you pull someone else pushes their changes, you might still see the above error.

3. **Restart Visual Studio** — this might work.

4. Open the command line from your current source folder and type the following:

```
git status
git pull
```

## Conclusion

When encountering merge or commit errors in Visual Studio's Git integration, the most reliable fix is to always pull before performing other operations. If the issue persists, try restarting Visual Studio or using the command line directly.


Common issues and fixes when using Git with Visual Studio.

Git with Visual Studio


## 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

1. [Introduction](#introduction)
2. [ASP.NET Solution Template](#aspnet-solution-template)
3. [Web Essentials](#web-essentials)
4. [Productivity Power Tools](#productivity-power-tools)
5. [Ionic Tabs Template](#ionic-tabs-template)
6. [Paid Extensions](#paid-extensions)
7. [Conclusion](#conclusion)

## Introduction

Here are a few useful Visual Studio extensions for .NET developers that can improve productivity and streamline development workflows.

## ASP.NET Solution Template

A solution layout for a typical ASP.NET web application, pre-configured
with Git, Gulp.js, NuGet, and StyleCop development tools. It is well suited
for developing a single-page application (SPA).

**ASPNET MVC ANGULAR Project Template** — Installation for ASP.NET MVC Angular project Visual Studio extension.

**CodeMaid** — CodeMaid is an open source Visual Studio extension to clean up, dig through,
and simplify your C#, C++, F#, VB, PHP, JSON, XAML, XML, ASP, HTML, CSS,
LESS, SCSS, JavaScript, and TypeScript coding.

## Web Essentials

[Web Essentials](https://visualstudiogallery.msdn.microsoft.com/359f4304-57d7-4178-9cab-165e2090dce2) — If you ever write CSS, HTML, JavaScript, TypeScript, CoffeeScript, or LESS,
then you will find many useful features that make your life as a developer
easier.

## Productivity Power Tools

**Productivity Power Tools** — A set of extensions to Visual Studio 2013 Professional (and above) which
improves developer productivity.

**Indent Guides** — Adds vertical lines at each indent level.

**Task Runner Explorer** — Provides custom task runner support to Visual Studio.

**GhostDoc** — GhostDoc is a Visual Studio extension that automatically generates XML
documentation comments for methods and properties based on their type,
parameters, name, and other contextual information.

## Ionic Tabs Template

[Ionic Tabs Template](https://visualstudiogallery.msdn.microsoft.com/dbcb8670-889e-4a54-a226-a48a15e4cace) — Build a cross-platform hybrid mobile app for iOS, Android, and Windows
Phone with the Ionic Framework and Apache Cordova. This project comes with
a simple tab-based layout.

## Paid Extensions

Paid extensions for Visual Studio: ReSharper, OzCode, NCrunch, .NET Reflector.

## Conclusion

These extensions can greatly enhance your Visual Studio development experience. Whether you need code cleanup, productivity boosts, or cross-platform tooling, there is an extension to help.


A list of useful Visual Studio extensions for .NET developers, including tools for code cleanup, productivity, and cross-platform development.

Few Useful Visual Studio Extensions for .NET


## Table of Contents

- [Introduction](#introduction)
- [Could Not Load File or Assembly](#could-not-load-file-or-assembly)
- [The Solution](#the-solution)
- [Conclusion](#conclusion)

## Introduction

This blog is for when you deploy ASP.NET MVC with NuGet to a Windows server and get an error that assemblies can't be loaded. For example, if you use ASP.NET's bundle feature, which is `System.Web.Optimization`, this blog might help your problem by changing the project reference setting. Basically, you have to change the reference's "Copy Local" property to true.

## Could Not Load File or Assembly

The long story is that after coding your ASP.NET MVC (4 or 5) application, everything works fine on your local machine or local IIS. You also use NuGet as a package manager for your web application, so that during the build, Visual Studio will automatically get the version from nuget.org or other NuGet package providers. My point is everything works fine on your local machine. Now you want to deploy to a web server, assume a Windows server.

So, most of the time it works fine, but sometimes after your deployment, errors appear.

My problem was that my web application used `System.Web.Http`, `System.Web.Http.WebHost`, `System.Web.Optimization`, and `Newtonsoft.Json`. I noticed that I couldn't find any of these inside my web server's bin folder. So, something was wrong with my NuGet setup, or I thought I wasn't doing something correctly.

## The Solution

Should I copy all the NuGet package folders to the web server? When I thought about it, I just needed all the DLLs to be inside the bin folder. Can NuGet do that? I haven't found a way for NuGet to do this directly, but after NuGet adds project references, if the DLL setting's "Copy Local" is set to false, then changing it to true will copy the DLL to the bin folder during the build.

![](https://d1p0mp3f1fx0hz.cloudfront.net/_1d9o29c1o.png)

## Conclusion

When deploying ASP.NET MVC applications that use NuGet packages, ensure that all required assemblies have their "Copy Local" property set to true in the project references. This ensures the DLLs are copied to the bin folder during the build and are available on the web server after deployment.


If you are getting an error such as "Could not load file or assembly" in IIS when deploying ASP.NET, this blog might help you resolve the issue.

Troubleshooting Issue When Deploy ASP.NET MVC5 to Windows Server


After installed following tools, you should be able to use git with visual
studio 2012.

1. Install Visual Studio 2012 update 4

2. Install Visual Studio Git Tool

3. restart visual studio

Open Team Exploer, then you'll see Git selection.

![](https://d1p0mp3f1fx0hz.cloudfront.net/_08g77sh2o.png)


This is a memo about how to use Git with Visual Studio 2012.

VisualStudio

Git with Visual Studio

A Tip for Ignoring NuGet Packages Folder in Visual Studio

Few Useful Visual Studio Extensions for .NET

Troubleshooting Issue When Deploy ASP.NET MVC5 to Windows Server

Use Git with Visual Studio2012