You can try the Text Macros for Visual Studio 2012-2019 extension (I am the author). It basically does the same thing as the Notepad++ macros (text editing, no UI automation). The code is open source (GitHub), so feel free to contribute improvements 🙂
The Visual Studio Build tools are a different download than the IDE. They appear to be a pretty small subset, and they’re called Build Tools for Visual Studio 2019 (download). You can use the GUI to do the installation, or you can script the installation of msbuild: vs_buildtools.exe –add Microsoft.VisualStudio.Workload.MSBuildTools –quiet Microsoft.VisualStudio.Workload.MSBuildTools is a “wrapper” … Read more
Open the history tab in Team Explorer from the Branches tile (right-click your branch). Then in the history right-click the commit before the one you don’t want to push, choose Reset. That will move the branch back to that commit and should get rid of the extra commit you made. In order to reset before … Read more
In my case, it turned out that I simply had to upgrade my test adapters and test framework. Done. Example using the NuGet Package Manager:
In Visual Studio Professional or Enterprise you can enable CodeLens by doing this: Tools → Options → Text Editor → All Languages → CodeLens This is not available in some Community Edition versions
I started to see this on a fresh Windows and Visual Studio 2013 Ultimate with Update 2 installation (although others have also reported it on Updates 3 and 4, as well as the Professional version). To resolve the problem, close all Visual Studio instances, then delete all files in the following folder: Visual Studio 2013 … Read more
For Visual Studio 2022 and the latest version of Visual Studio 2019: From the help menu, select Privacy > Privacy Settings In the Visual Studio Experience Improvement Program dialog, select No, I would not like to participate. Note: You can’t opt out in pre-release versions by this mechanism. For older versions of Visual Studio From … Read more
As you’ve already noticed, you can control most of these settings in .csproj. If you’d rather keep these in AssemblyInfo.cs, you can turn off auto-generated assembly attributes. <PropertyGroup> <GenerateAssemblyInfo>false</GenerateAssemblyInfo> </PropertyGroup> If you want to see what’s going on under the hood, checkout Microsoft.NET.GenerateAssemblyInfo.targets inside of Microsoft.NET.Sdk.
For me, the solution (workaround) is to turn off JavaScript debugging on Chrome, which I believe is a new feature introduced in VS 2017. Go to Tools > Options > Debugging > General and turn off the setting for Enable JavaScript Debugging for ASP.NET (Chrome and IE). This is a known issue already, and seems … Read more
For .NET 4.6.2 or lower, .NET Core 1.x, and .NET Standard 1.x you need to install the NuGet package System.ValueTuple: Install-Package “System.ValueTuple” Or using a package reference in VS 2017: <PackageReference Include=”System.ValueTuple” Version=”4.4.0″ /> .NET Framework 4.7, .NET Core 2.0, and .NET Standard 2.0 include these types.