I first saw this on Scott Hanselman’s blog the other day and wanted to share the tip. Additional details can be found from his blog here. Please note that this feature is only available on Visual Studio 2015 Update 3 and up.
Steps to Enable:
1. Launch Visual Studio 2017
2. Select Tools > Options
3. Select Text Editor > C# > Advanced
Now Visual Studio will give you an additional choice when you try and use a type that doesn’t exist to use a NuGet package that has that defined type. Awesome!
Some may note that this feature has been in Resharper for awhile now but seeing this integrated into the default IDE is a huge plus.
If you ever run into a scenario where you need to run your TeamCity build configuration step against a particular build agent there is a simple solution for you built right into TeamCity.
1. Navigate to your build configuration step by either selecting it from the Overview page or selecting your project, and then the build configuration step.
2. Select “Edit Configuration Settings” at the top-right of the page.
3. Select “Agent Requirements” from the left-hand side of the page.
4. Underneath the “Explicit Requirements” section, select “Add new requirement”.
5. Select the parameter name “teamcity.agent.name”.
6. Use the default condition of “equals”.
7. Within the value field, add the name of your TeamCity build agent that you would like your process to run against.
Note: These steps are based on TeamCity 9 but have been verified to still work with the latest version of TeamCity 10.