I am using Windows Remote Desktop (RDP) to connect to my office computer via a Cisco Gateway. In VS2012, my project is open and I clicked Build/Publish Web menu. The Publish Web wizard window flashed for a second then disappeared. It seems to go behind the main VS2012 and made the main VS2012 go into modal mode. It does not respond to any mouse or keyboard commands. I had to use Task Manager to kill it then relaunch it to regain control. This doesn't happen when I am in front of my office computer. I can see the Publish Wizard in front of the main VS2012 window. This doesn't happen to my coworkers who are also telecommuting via RDP. I tried to look up VS2012 log, but there is no such a log file on my computer. Windows Application Log doesn't say too much either. There are 2 devenv.exe *32 in the Task Manager Processes tab. I killed the one with smaller memory size. It still wouldn't make the main VS2012 come out of modal mode. Please help. Thanks.
Related
So here is the setup. This is for Cyber Essentials (and Cyber Essentials plus).
We have a product that requires local admin access to run. We need to log into the PC as a non admin. So first of all I have done the devenv.exe trick for compatibility to mark it as 'run as admin'. So when we run Visual Studio it will now prompt to enter login details of an admin user. I enter the details of my 2nd user who is a local admin on the machine.
Visual Studio 2022 starts and I get the admin badge in the corner. Our product runs (it's running under the other user) successfully, but I have a problem with areas of the product that launch in a web browser.
First of all, any process.start(url) style command will run (without any errors or events in event viewer) except the web browser just doesn't appear.
Also, manually selecting a web project in the solution and running it will run IIS express except again, it will not open the web browser (there is a workaround to this in that I can open the browser myself and grab the localhost:port address from the IIS Express system tray icon).
But basically running in this scenario, no projects can open a browser. Anyone else come across this and have a solution? Thank you.
I have built an outlook addin, and I'd like to remote debug it running inside a vm on my dev machine (the vm is xpsp3 x32 and outlook 2010, my dev machine is 7 x64 with outlook 2007)
I have (after quite a bit of messing about with user accounts etc) got remote debugging working between vs2010 and the virtual box vm. I can attach to a simple test application and set breakpoints, and they get hit.
However, I can't seem to do the same with the outlook addin. I can't just attach to the outlook.exe process running on the machine as that does not seem to load the addin modules so the breakpoints never get hit.
I can't figure out how to get VS2010 to start outlook on the remote machine from a locally built project, I tried to follow these msdn docs but the instructions to set the working directory don't seem to work, so if I set it as the example suggests and start debugging it comes up with a message saying that the folder does not exist.
If instead I set the Start Action in the debug properties for the outlook addin project to 'Start External Program' and point it at the outlook exe, then VS2010 will successfully start the app, however, the breakpoints are not hit, even though it seems to indicate that they have been successfully set.
Has anyone been successful in remote debugging vsto addins? What am I doing wrong?
I know this is quite an old question, but just in case someone comes across this post, here is a solution:
On the host machine, in the VSTO project, add this at the top of the startup method.
MessageBox.Show("Debug");
Deploy the add in to the remote machine, open Outlook and the MessageBox should display
Run the Visual Studio Remote Debugging Monitor on the remote machine
On the host machine, set a breakpoint on the line after the MessageBox
In Visual Studio, select Debug/Attach to Process from the menu and attach to the Outlook process running on the remote machine
On the remote machine, click on the OK button on the MessageBox you added in step 1
The breakpoint you set in step 5 will now be hit
when i push F5 in a VS2005 web service project,
a new explorer window opens and the Web service i try to debug opens.
but the VS2005 doesn't stay attached to the new window. it just stays like i didn't run the service.
when i use the service in the new window that opened , the breakpoints in the project doesn't work.
its like ,when i pushed F5 i opened a new process that is notattached to my project
(using "Attach to Process" doesn't solve the problem).
it worked before but now it doesn't...
the project and the service page are both "Set as Startup Project/Page".
I found the problem. it is The windows Explorer 8!
The windows explorer 8 doesn't let two projects of VS2005 be debugged together.
i had two VS2005 projects that one is the simulator of the other.
i needed both applications to run together - each project that runs (and debugged) opens a different Explorer window. The problem was that when one project opened, the other couldn't be attached to its window.
uninstall windwos explorer 8 and roll back to 7 version of explorer. it solves the problem!
I'm testing a web service in Visual Studio, and stepping through using the debugger.
Then I click stop debugging. This stops the debugging session, but the program continues to run like a runaway train.
Is this a "bug" or a "feature" of Visual Studio 2008? If it's a feature, how can I tell Visual Studio to halt execution when I click on 'stop debugging'?
The web server that visual studio uses will keep running in the background. You should be able to stop it using the icon in the task bar.
Or if you have lots of instances running, my favourite little trick is to pop open the run command and type:
tskill webdev
When you run webservices, even when you stop them, they still run on the background, what you can do is look in the taskbar on the right hand side and close out the instances of the webservice that are running by right clicking on the icon and pressing stop.
While you've stopped debugging the application chances are that the asp.net developement server is running. you should be able to stop that from its tray icon
I'm using Visual Studio 2008 to develop ASP.NET applications. Currently I'm debugging with running on IIS. I would like to switch to the development web server (Cassini) for debugging, so that I can use features like edit and continue. The reason that I'm not, is because the development web server only starts up when you are in debug mode. Is there any way to keep it running all the time, and just have Visual Studio attach to the existing server process like it does with IIS?
Rihan is partially correct...
In your Project Property page, Web tab: Enable Edit and Continue
If checked - The Development server will close when the app (not VS) stops.
If unchecked - Development server keeps running
You can also start your cassini server from the command line which takes alot of pain out of the whole "debug" effort...
Check out a good snippet here on how to do this: https://thoughtjelly.wordpress.com/2009/05/13/launch-cassini-from-the-command-line/
Once started, the built-in web server continues executing even when you stop debugging, as long as your VS2008 project is still open. Just start up the debugger when you want to start debugging again. I typically have another browser window open and interact with the built-in web server from there instead of the browser window that it opens so I can keep working with the application in the same state even after turning off the debugger (which closes the opened browser window).
I'm running VS2008 on Windows XP SP3.
The simplest way I have found to acheive that is by launching the debugger as normal. Then in Visual Studio goto the Debug menu, and select detach all. It detaches from the Cassini web engine, but it does not shut it down, as it does when stopping debugging.
I am quite sure you are know that there is command line swithces that you can you use to launch the cassini engine, but my guess is you are looking for something slightly easier.
Detaching does not close the browser window that visual studio launched, and if you do close that spesific web window then it will stop debugging.
I am running VS 2008 SP1 on Vista 64x SP1 without IIS.
Hope it helps
Rihan Meij
I have 3 web sites, with Single sign on between each site so I need to start all 3 with attach to process. However, there was no process to attach the debugger to, and whenever I started a project with F5 then stop it, the visual studio web server closed.
The Enable Edit and Continue option didn't change anything.
So to start the web server and keep it running so that you can attach the web project to the process, I simply did a "view in Browser" (ctrl+shift+W). This started the server process but not the project nor the debugger. I could then attach to process easily.
In Visual Studio 2015 you do this by going to Tools > Options > Debugging > General and unchecking the "Enable Edit and Continue" option: