visual-studio-2017

Crashing Visual Studio Live Unit Testing

北城余情 提交于 2021-02-10 08:05:04
问题 I´m a new user in stackoverflow and this is my problem: As part of my work, we recently installed VS 2017 Enterprise Edition. Everything was fine untill few weeks ago the Live Unit Testing module stop working. Does enyone was able to resolve this kind of problems? This is the output console: [17:26:23.170 Info] Live Unit Testing started. [17:26:23.229 Error] - FatalError - System.ArgumentNullException: Value cannot be null. Parameter name: key at System.Collections.Generic.Dictionary'2.Insert

.net core project dependencies - yellow triangle

故事扮演 提交于 2021-02-10 06:47:39
问题 My .Net Core project has a yellow triangle on dependencies, but when I open it up, none of the child entries have a yellow triangle. When I hover over dependencies, I don't see any tooltip telling me what's wrong. How can I check to see what is causing this yellow triangle to show up? I did what @oandreeeee suggested and increased the log level of my build and I noticed this: C:\Program Files\dotnet\sdk\2.2.104\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.ConflictResolution.targets(41,5):

Error launching vschrome_diag when Visual Studio 2017 starts debug on Chrome

筅森魡賤 提交于 2021-02-10 06:46:07
问题 From today, when I start debug of a web application on Chrome this error appear. Then I click on OK and this other error appear In the last day, I've update neither Visual Studio or Chrome. 回答1: Removing the C:\Users...\AppData\Local\Temp\vschrome_diag file worked for me. 回答2: Solved. It was enough to uninstall Chrome, restart the PC and then reinstall Chrome. 来源: https://stackoverflow.com/questions/47154397/error-launching-vschrome-diag-when-visual-studio-2017-starts-debug-on-chrome

Visual Studio 2017 for Dymola cannot open stdio.h

穿精又带淫゛_ 提交于 2021-02-10 06:44:14
问题 I am trying to use Visual Studio 2017 as a compiler in Dymola 2019. I have installed all the components in VS2017 for C++ (as far as i could find). But when i try to test compiler in Dymola, I get an error message as follows : Compiling and linking the model (Visual C++). ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.9.11 ** Copyright (c) 2017 Microsoft Corporation *****************************************************

Visual Studio 2017 for Dymola cannot open stdio.h

不想你离开。 提交于 2021-02-10 06:44:12
问题 I am trying to use Visual Studio 2017 as a compiler in Dymola 2019. I have installed all the components in VS2017 for C++ (as far as i could find). But when i try to test compiler in Dymola, I get an error message as follows : Compiling and linking the model (Visual C++). ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.9.11 ** Copyright (c) 2017 Microsoft Corporation *****************************************************

Missing some components in SSIS toolbox in Visual Studio 2017

旧城冷巷雨未停 提交于 2021-02-09 11:12:36
问题 I am using Visual Studio Community 2017 for developing SSIS packages and I use SQL Server 2016. Some of components are not in SSIS Toolbox. This is that I have now: and this is my colleges have(They don't have the same version of Visual Studio that I have): For example: I need to add a XML Source component to one of my Data Flow but there is not anymore in Other Sources sector in SSIS Toolbox. I tried to add the missing components (Tools -> Choose Toolbox Items ->) but I don't have the tab

Missing some components in SSIS toolbox in Visual Studio 2017

怎甘沉沦 提交于 2021-02-09 11:11:58
问题 I am using Visual Studio Community 2017 for developing SSIS packages and I use SQL Server 2016. Some of components are not in SSIS Toolbox. This is that I have now: and this is my colleges have(They don't have the same version of Visual Studio that I have): For example: I need to add a XML Source component to one of my Data Flow but there is not anymore in Other Sources sector in SSIS Toolbox. I tried to add the missing components (Tools -> Choose Toolbox Items ->) but I don't have the tab

dotnet restore not using PackageReference condition

落花浮王杯 提交于 2021-02-09 09:21:06
问题 my project has multiple target frameworks, 2 of the package reference need to use a different version for .net461 when building in VS 2017 everything works and the dependency shows using the right versions. but when build using dotnet cli, the dependency shows the wrong version is being use for .net461. is this a bug in dotnet cli? I also try putting those 2 pkg in another ItemGroup tag with condition but still the same update: for anyone else running in to this issue, I ended up using

Visual studio 2017: Cannot open include file 'd3dx9.h' no such file or directory in a static library used by .exe application

為{幸葍}努か 提交于 2021-02-08 10:27:02
问题 I am using Visual Studio 2017 and I'm required to use DirectX9.0 for a school project. I have a solution with 3 projects. One is a static library (.lib), one is an application (.exe) and one is a unit test project: KB01_Game.exe imports KB01_Engine.lib like so: KB01_Game properties KB01_Engine.lib contains the d3dx9 references like so (I have also tried reversing the order of these DXSDK references, with no success): KB01_Engine properties The files in KB01_Engine include the directx 9

Visual studio 2017: Cannot open include file 'd3dx9.h' no such file or directory in a static library used by .exe application

狂风中的少年 提交于 2021-02-08 10:23:03
问题 I am using Visual Studio 2017 and I'm required to use DirectX9.0 for a school project. I have a solution with 3 projects. One is a static library (.lib), one is an application (.exe) and one is a unit test project: KB01_Game.exe imports KB01_Engine.lib like so: KB01_Game properties KB01_Engine.lib contains the d3dx9 references like so (I have also tried reversing the order of these DXSDK references, with no success): KB01_Engine properties The files in KB01_Engine include the directx 9