Sometimes I get the message that the breakpoint will not be hit, and no symbols will be loaded.
The red icon in vs.net changes color, and the debug mode just doesn't work.
what is the reason for this?
You may be running your project in Release mode. If so, then switch to Debug mode
From Visual studio debugging issue with files of the same name by Philip Carney
Do each bullet in the link below ONE AT A TIME, but repeat my steps below with each one you try.
Stop debugging (press red square icon) in Visual Studio
Clean Solution
Build Solution
Tools > Attach to Process (or start with debugging)
Start the program that you're attaching to, and run it such that your code will get hit
If attaching to nunit.exe, then open NUnit and run a test so your breakpoint will be hit
If attaching to w3wp.exe (IIS site), then open your site in the browser and go to the page that will hit your breakpoint
for manage code only - theres a good answer for this problem on the following site:
http://geekswithblogs.net/dbutscher/archive/2007/06/26/113472.aspx
for native + managed code - in the startup solution properties-> Debug tab
make sure that "enable unmanaged code debugging" check box is checked
After trying several suggested fixes for this I did the following to get it working.
Right Clicked my Project in the Solution Explorer and selected "Properties".
Went to the "Web" section and made sure "Start Action" was set to "Current Page".
Spent 3 1/2 hours on that... I'm going to go get a drink now.
I resolved this problem by selecting Automatic:Native Code for the "Attach to" field in "Attach To Process" form
Next to the "Debug/Release" dropdown list, there is another one with "Any CPU/Configuration Manager...". Click "Configuration Manager...", and you will see some of your projects might be in Release mode. Change all of them to Debug.
This can happen if the symbol fiels are different from the assembly (remote debugging), or when there is no "direct path", so the assembly hasent been load, but might be loaded using reflection and loading of the required assembly at run time.
This can also happen if the debugger is not attached to the process for whatever reason. If it's the case, you can always go to Debug - Attach to Process... and choose the right process. Your breakpoints should return to normal once VS determines it can hit them.
What does it say when you hover the mouse over the disabled breakpoint? It will usually tell you the problem. My favorite is the old 'source code is out of date', especially when I'm debugging a DLL. Another favorite is when the file you're looking at isn't the one you're debugging (a copy in another folder?). If it's a case where you can breakpoint a caller routine, but not the callee, stepping into the callee will force VS to open the 'proper' source file and you'll be able to set breakpoints. Confusing, I usually swear at VS at this point, it seems to help.
I had the same problem. Which I know is normally if the build versions are different, and something isn't matching up. I cleaned my project, rebuilt it, and then deployed and that got everything back in-sync.
I do not like to play with knives but the only thing that worked for me involved editing the .csproj file itself. So, unload the project file, edit it by cutting and pasting the three asp.net files so that they are together in the ItemGroup. However, sometimes it is necessary to go further as explained here: http://carnotaurus.tumblr.com/post/4130422114/visual-studio-debugging-issue-with-files-of-the-same - Also, I give a list of other proposed solutions that did not work for me. I hope it helps.
I have tested with both deployed application and service, what I have found out that If the deployed code is different than a code in visual studio then breakpoint will not hit. Even small changes will affect and the breakpoint will not hit. So, It is better to debug the same version which is there on vs code and also in deploy application or service.
To fix this I had to re-create the virtual directory. I'm using Asp.Net 4.7 Framework and IIS Express. Went to Web project > property page > Web tab > clicked the "Create Virtual Directory" button next to Project Url textbox.
I forgot I had clicked this button in my "Main" branch, but then had switched to my "Sprint" branch. It kept running the "Main" code until I clicked "Create Virtual Directory" on my "Sprint" branch.
For me it was giving this because I haven't started the relevant project at start of application , it worked after I added project run on start
In Visual Studio, how can I exit the current project and load another? Something like reloading?
i.e when i'm executiing my project(window application) i need to close the current exe and load another instance of the exe file.
File --> Close Project...
File --> Open Project
I think you're looking for the restart action.
View|Toolbars|Debug will show you the toolbar; the square blue icon with an arrow pointing left is what you're after.
On my system the keyboard shortcut is Ctrl+Shift+F5.
Simply open another project. Visual Studio will automatically close the current project when opening a new one.
I'm still not entirely sure that's what you're asking for though. Here are a couple of related actions and the way to achieve them
Unload project: Right Click and select "Unload"
Remove project from solution: Right click and select "Remove"
Close Solution: Right click on the solution and select "Close"
If you mean how to restart the program currently being debugged, then use the command "Debug -> Restart" or press "Ctrl+Shift+F5".
I have a solution with about 20 projects (that use Devexpress controls) in and when I do a normal solution build (ctrl-shift-B) it says everything is completed sucessfully when in actualy fact it has done nothing. To get it to build i have to right click on the solution and use the batch build option.
I've tried deleting the solution and regetting from TFS and i've even gone as far as reinstalling VS!
Anyone got any clues as to what is going wrong?
Sorry should have added that also tried to build from the main menus aswell.
I've had similar issues. It's a long shot, but right-click your solution and go to Properties -> Configuration Properties. Check to make sure all of your projects have the "Build" option checked.
Perhaps Ctrl+Shift+B has been assigned to one of the "check-to-see-if-it-is-needed-before-building" type of functions?
Check in the keyboard setting:
Right-click the toolbar
Select Customize in the popup menu
Click the Keyboard button in the lower right corner of the dialog
In the new dialog, in the "Press shortcut keys", a bit to the right and below the center, hit Ctrl+Shift+B
Verify that it is bound to Build.BuildSolution
at least that is what it is bound to for me. I notice there is an action named Build.RebuildSolution as well, you should experiment.
Unfortunately it looks like for various reasons I'm going to have to use Visual Studio 6 instead of a newer version of VS.
It's been a long time since I've used it. I'm looking through its menus and don't see any obvious way to set up any custom build steps (pre-build, post-build, pre-link... anything would help actually).
Can anyone give me instructions on how to set up steps like this?
Open your project, then open the Project Settings screen (Project → Settings or ALT-F7). Alternatively, right click on a file in the FileView and select Settings.
From the Project Settings screen, go to the General tab and check "Always use custom build step". This means that the file you just chose will be an input file for a custom build step. From the "Custom Build" tab you can then give the commands to run and specify what files will be generated.
For pre-link, post-build and such, select an executable (or library) from the Project Settings screen. Then use the little arrow button to scroll to the rightmost tabs. From there you'll find the Pre-link and Post-build steps.
It's quite simple, really, I'm sure this is enough to get you started.
My "Start debugging" button and element menu are greyed out... but only on one of my projects (an ASP.NET website). I have no idea what I have done to disable it.
I already checked everything in the Property page of both the solution and project. I even compared it to another project, but nothing seems to do the trick... maybe I missed an option ?
It sounds like your startup projects are all set to "start without debugging", since that would cause the button and element to grey out.
This can be fixed from Solution -> Set StartUp Projects.
Is it a startup project? You can only debug projects that can actually be started.
Right click on the project and click properties. Then click on Start Options (or something similar) to see the settings. If it's an executable project, you probably want to choose the option that will start the project output.
If you're able to start the project, you can usually attach the debugger using Ctrl+Alt+P (Or choose Attach to Process from the Debug-menu) and then choose the process from the list that comes up.
Do you have the COM+ Event System service running?