You need to manually edit the project file and add s to the default TargetFramework and basically change it to TargetFrameworks. Then you mention the Moniker with a ; separator. Also you can put the Nuget package references in a conditional ItemGroup manually or using VS Nuget Package Manager. Here is what your .csproj should … Read more
I found the answer in this blog post: See how empty is the regular HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\15.0 key on my machine and notice that there is no 15.0_Config key: Instead, the VS 2017 private registry is stored in your AppData folder: Fortunately, you can use regedit.exe to load a private hive. You need to select the HKEY_USERS … Read more
From documentation: if you wish to specify, for example, some files to get published with your app, you can still use the known mechanisms in csproj for that (for example, the <Content> element). There is a CopyToPublishDirectory attribute for ItemGroup elements that determines whether to copy the file to the publish directory and can have … Read more
Please try below items to narrow down the issue: Remove the TFS related credentials from Credential Manager In Credential Manager add the new updated Generic Credentials for the TFS account. Generally, this would overwrite the cached credentials. Close all Visual Studio instances, delete %LOCALAPPDATA%\.IdentityService as you did. Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\7.0\Cache Clear all the … Read more
The problem you’re facing is related to Visual Studio, especially 2017 which is shipped with System.Net.Http v4.2.0.0. However, adopting the new way whereby any references should be done via NuGet, latest version of System.Net.Http which is 4.3.3 contains the dll version 4.1.1.2. The problem is that VS at build time and at run time as … Read more
In website’s NuGet window: Uninstall Microsoft.CodeDom.Providers.DotNetCompilerPlatform Re-install it In web.config, under: system.codedom > compilers > compiler, change compilerOptions=”/langversion:6 to 7
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 🙂
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 .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.
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.