Is there any way to attach debugger to intergrated terminal? Every time I run debugger in VS, it opens cmd windows for me, but I want it to run in intergrated terminal, is it possible to do so?
Related
On a Windows machine, I'm heavily using the "open folder in container" functionality of Visual Studio Code, with Docker managed by Rancher Desktop.
For this to work, I always run Visual Studio Code as administrator.
Since today, however, it doesn't work any more, and the "Docker returned an error code EACCES, message" is reported.
As a workaround, I changed the properties of
C:\Users\<userName>\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\Docker.exe
by unchecking the "Run this program as an administrator" checkbox:
This, however, seems to me not to be a good solution to the problem.
What is the proper way of fixing the issue?
We are trying to get functional coverage for our .NET Core application using Open Cover. Able to get coverage with dotnet command as well as application executable running in local machine setup.
In one of the server, we have hosted the website and planning to running End to End functional automation using the script from another machine.
Tried the steps mentioned in the document to run Open Cover along with IIS process(in debug mode): https://github.com/OpenCover/opencover/wiki/IIS-Support
It didn't work for me. Application is not getting up and running. Worker Process is not showing up under machine node in IIS manager though able to see it in task manager Running with command line 'C:\Windows\System32\inetsrv\w3wp.exe -debug -s 2".
It didn't show up with command 'appcmd.exe list wp' also.
Has anyone tried with IIS 10 and Windows 2016 server? is there any new workaround?
Any help would be great. Thanks in advance
**Command tried : **
OpenCover.Console.exe -target:C:\Windows\System32\inetsrv\w3wp.exe -targetargs:"-debug -s 2" -targetdir:{WebsiteBinFolder} -output:FuncCoverage.xml -filter:+[] -register:user -oldstyle
I have converted a .NET Core console application to a Dockerized application using Visual Studio 2017's built in Container Orchestration features. VS created a Dockerfile and a docker-compose file. I am able to run the application within the container successfully.
The problem is that in some cases the application requires input at the console (e.g. it asks a question and the user must answer yes or no). The app uses Console.ReadKey() or Console.ReadLine() as appropriate.
When running a .NET Core console app traditionally, a terminal window pops up that displays the app's output and accepts input. However, when I switched to Docker, the console output now appears in one of the debug panels on the bottom of the screen, and I'm not able to provide any input.
The app does not fail to run, it simply blocks indefinitely at the Console.ReadLine() command.
Is there a way to make Visual Studio run the container within a traditional terminal that can accept user input?
Kahbazi is right, you need to run the docker container with -i (interactive mode) and -t (tty mode). For example: docker run -i -t --name containerName imageName
Ensure not to run it in detached mode too, or else you won't be prompted for input since the container will run in the background.
I was unable to find a way to do this through Visual Studio, so I used docker through the command line instead.
I have Jenkins CI server which builds various .net projects. The server is on Virtual Machine, connected to ActiveDirectory and Jenkins is running in the context of domain user which is also a local administrator.
Software used:
Windows 10 Professional
Visual Studio 2015 14.0.25431.01 Update 3
Jenkins 1.625.3
Solutions are build using devenv.com (currently msbuild is not an option), e.g.:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com" "xxxxx.sln" /rebuild "Release|Any CPU"
My issue is, that quite often I receive an error, just after running devenv.com:
Microsoft Visual Studio has detected a configuration issue. To correct this, please restart as Administrator. For more information please visit: http://go.microsoft.com/fwlink/?LinkId=659046Build
It started to happen after one of Windows 10 updates. I found out, that when someone is log in to build server with the remote desktop using the same domain account, the builds run OK. After logout, the builds run OK for some time and then the errors are back.
Any clue what's going on?
It may be related to this apparent bug in a recent Windows update:
Connect: Visual Studio 2015 and SSMS 2016 RTM (VS 2015 shell) not running under "Run as different user" on Windows 10 Anniversary, Windows 2016 CTP 5
UPDATE 2017-09-08
As #Florian points out, the above link is broken. I can't even find the Connect issue cached on Google, Bing or archive.org.
The Connect issue Unable to start SSMS as another user (cached copy on archive.org) makes me think it would be worth checking whether the problem resolves after updating Windows 10 to 1703 (Creators Update) and ensuring that April 25, 2017—KB4016240 (OS Build 15063.250) has been applied. If this works, anyone running Jenkins on Windows Server 2016 will have to wait for Microsoft to publish 1703 and KB4016240 (or equivalent) for that OS.
Excerpts from Connect page "Unable to start SSMS as another user". I have bolded the error details, which match those in the original question (except for the LinkId in the supplied URL) even though the product is SSMS rather than VS:
Version: SQL Server 2016 CTP3
Operating System: Windows 10
Steps to Reproduce:
Right-click SQL Server Management Studio, select "More", then "Run as
a different user"
Actual Results:
Error message: "This task requires the application to have elevated
permissions" with two options: Restart under different credentials,
and Cancel the task and return to Microsoft SQL Server Management
Studio. Pressing either option closes the window with no further
result. Error information is:
Microsoft SQL Server Management Studio has detected a configuration issue. To correct this, please restart as Administrator. For more information please visit: http://go.microsoft.com/fwlink/?LinkId=647011.
When I go to that page and try the fix suggested there, I can't find
ieproxy.dll. The fix is for Windows 7 / Internet Explorer 8, and I'm
on Windows 10 with Internet Explorer 11, so that may be why it's not
there.
[...]
Posted by Microsoft on 4/28/2017 at 6:26 PM
Hi Jake, It turned out that this issue has been resolved (on the Windows side) very recently - like 3 days ago :)
If you are running Win10 "1703", just make sure you get the latest
updates (specifically, KB4016240) and you should be able to run
ssms.exe using "runas" just fine. This will work with any version of
SSMS.
Currently, the fix is not available on older versions of Win10 (e.g.
1607) or WS2016 (also 1607).
Thanks,
-Matteo
[...]
Posted by Microsoft on 4/27/2017 at 7:35 PM
Hi Jake, Yes, we are aware of this issue (in Windows 10).
We've engaged with the Visual Studio and Windows folks (which is there
the issue is) and hopefully will have a way to fix this issue in SSMS
(you should not need an updated SSMS, just an update in Windows 10).
I'm going to keep this issue open until I have more concrete updates
on it.
Thanks,
-Matteo
If the Windows updates do not solve the problem or are not available to you, I would suggest trying repair operations on Windows as well as Visual Studio.
I'm running into the same error after updating my Windows 10 to 1607, in that I cannot run Visual Studio as a different user. I'm not building solutions at the time though, but still running the VS program as I think you would be calling.
Using this command: runas /netonly /user:domain \ account devenv.exe
as outlined here Unable to launch Visual Studio 2015 as a different user works for me. Not as convenient but does the trick.
I installed WinDDK 7600 in my Windows XP operating system.Now,when I double click the devcon.exe(Location- D:\WinDDK\7600.16385.1\tools\devcon\i386),the command prompt is just showing up and suddenly disappears.Can anyone resolve this issue.
As far as I'm aware devcon is a command-line only program. You have to run it from a command window (cmd.exe) with the appropriate parameters. Once you know the parameters you want to use, you can write a batch file to easily recreate the command you want.
I ran across this post because Win7 has a similar problem even when running in cmd.exe.
There is a solution found on Microsofts website here:
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/devcon-not-working-correctly-in-windows-7/9abcc12c-d7db-4249-aec4-fc4ff0ea6ee8
I have not been able to verify it yet.
The same (a windows open and automatically close) happens even if using a normal command prompt. However opening the command prompt with administrator rights and then run devcon works.