In Visual Studio 2017 and with .NET Core projects a new way of referencing nuget packages was introduced. Somehow during a .NET project upgrade one of the nuget packages were converted into a PackageReference (referenced in the csproj file and not from package.config). Below are the steps to convert such package reference back into plain old package.config behaviour:
In addition to removing the PackageReferences from the project file, I also had to remove the following files from the $ProjectDir\obj directory: Myproject.csproj.nuget.cache Myproject.csproj.nuget.g.props Myproject.csproj.nuget.g.targets project.assets.json
Visual Studio IntelliCode brings you the next generation of developer productivity by providing AI-assisted development. Every keystroke and every review is informed by best practices and tailored to your code context. You can try it out today by downloading the experimental extension for Visual Studio 2017 that provides AI-powered IntelliSense.
Using ReSharper? See this post:
Visual Studio Live Share
Real-time collaborative development
Collaboration across your entire development workflow Live editing Author and edit code together in real time Independent exploration Navigate across files on your own without interrupting others Follow along Pin to a user to follow their cursor as they navigate Group debugging Set breakpoints and step through code together Shared servers View web apps and databases without exposing ports to the Internet Shared terminal Run commands and tasks, with output streamed to team members
Are you annoyed by the default project location in Visual Studio? Check out this tutorial and learn how to modify it to suit you needs.
A simple WCF test client is included in Visual Studio.
It resides here for my Visual Studio 2017 installation:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\WcfTestClient.exe
A very usable keyboard shortcut when working with html in Visual Studio.
Visual Studio 2015 comes with a new shortcut, Shift+Alt+W wraps the current selection with a div. This shortcut leaves the text “div” selected, making it seamlessly changeable to any desired tag. This coupled with the automatic end tag replacement makes for a quick solution. UPDATE This shortcut is available in Visual Studio 2017 as well, but you must have the “ASP.NET and Web Development” workload installed. Example Shift+Alt+W > p > Enter
In TFS / Visual Studio 2012, you have a few options.
Rollback to a specific version
In Source Control Explorer:
- Right Click the branch you wish to roll back
- Click Rollback…
- Choose Rollback to a specific version
- Enter the changeset number you wish to roll back to.
Rollback a single changeset (you can do this through the dialog loaded above too)
- Right click the changeset you wish to rollback
- Choose Rollback entire changset
Checkin the rollback.
Error in Visual Studio 2017 in output window from task manager:
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 5.x
Found bindings for the following environments:
– Windows 64-bit with Node.js 8.x
For VS 2015
- Go to: Tools > Options > Projects and Solutions > External Web Tools
For VS 2017(.3)
- Tools > Options > Projects and Solutions > Web Package Management > External Web Tools (per @nothrow)
- Reorder so that $(PATH) is above $(DevEnvDir)\Extensions\Microsoft\Web Tools\External
See stackoverflow here:
This is a super simple extension that adds shortcuts to Tools menu to attach to IIS, IIS Express, as well as any exe files found within the currently loaded solution (Attach To Solution).