Home > Visual Studio > Visual Studio 2012 Breakpoints Not Working

Visual Studio 2012 Breakpoints Not Working


My boss asks me to stop writing small functions and do everything in the same loop North by North by North by South East Where do all these electrons come from? You should describe how you turned off Code Coverage. –jamesrom Aug 6 '13 at 3:14 add a comment| up vote 4 down vote I have a very specific scenario that resulted Click the [Advanced] button at the bottom of the Build tabpage. New Verification Code sent. have a peek at this web-site

View All Notifications Email : * Password : * Remember me Forgot password? Choose "Properties". When changing the latter to "Automatic" (which still pointed me to "Native code"), it suddenly worked. I can open up Debug > Window > Modules, but what do I do from there? http://stackoverflow.com/questions/14025734/vs2012-breakpoints-are-not-getting-hit

Visual Studio Breakpoint Not Hit No Symbols Loaded

Looking for a movie of about futuristic city and alien society GO OUT AND VOTE Navigation in insert mode Can a spellcaster switch between multiple foci? The Art of Word Shaping 5 Favorite Letters more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Can a spellcaster switch between multiple foci?

share|improve this answer edited Jan 3 '13 at 4:33 answered Jan 2 '13 at 23:21 chue x 14.6k63250 add a comment| up vote 0 down vote Some more stuff to try: You can restart SPTimerV4 service for restarting SharePoint Timer Job, write following in Command Prompt: net stop SPTimerV4 net start SPTimerV4 share|improve this answer answered Feb 25 '14 at 9:51 Arsalan How come nothing in MyService gets hit? Visual Studio 2015 Breakpoint Not Working Reply GaurangNaik Participant 1559 Points 603 Posts Re: Breakpoint not working - very strange issue!

It was even criazier: the debugger went inside a library function, but somehow skipped one line in the middle of it. Breakpoint Not Hitting In Visual Studio 2013 Permalink Posted 19-Sep-14 22:14pm iscool1.6K Rate this: Please Sign up or sign in to vote. But of course I have been doing other things on ASP.net. read this article The breakpoint issue sounds like it could be from you referencing the DLL in bin, but your project is building to bin/debug.

Solution 1 Accept Solution Reject Solution Refer: Check list, to make the breakpoints hit[^] Breakpoint Will Not Currently Be Hit[^] Permalink Posted 3-Sep-12 4:55am Prasad_Kulkarni115.3K Updated 3-Sep-12 4:56am v2 Rate this: Breakpoint Not Working In Visual Studio 2010 Do the guest schools spend an entire academic year in the host school during the Triwizard Tournament? For most development using Visual Studio, the project properties define whether debugging is turned on or not. Is Pluto a "proto-planet"?

Breakpoint Not Hitting In Visual Studio 2013

Visual studio uses the symbols saved in the pdb-files to find the exact position of the break point. The solution, in my case, was silly, and with as much LINQ as I use I should have figured this out sooner. Visual Studio Breakpoint Not Hit No Symbols Loaded This should create a new dll along with PDB. Visual Studio 2013 Not Stopping At Breakpoints In the code I have put breakpoints at the start on oninit() and pageload() methods.

What game did I see in Verona, Italy? Check This Out Please check your Inbox. It is almost as if it is using an old file from a cache of some sort.... The workaround is to use aspnet_compiler with the -v and -d parameter. -d will generate the symbols for you. 3. Breakpoint Not Hitting In Visual Studio 2015

So in such a situation, you will notice that the debugger may sometimes hit the breakpoint and sometimes it will not. If that's the case you can have your assembly loaded, so breakpoints would be solid red circles but another copy of the assembly, running in a separate process is actually handling Permalink Posted 3-Sep-12 8:43am Sandeep Mewara505.5K Rate this: Please Sign up or sign in to vote. Source Below is a screenshot of an example and Visual Studio's dropdown list of build configurations.

I just recreated the project reference and everything was fixed. Visual Studio Breakpoints Not Being Hit The best explanation I have for why this worked apart from pure luck is that we migrated projects from one version of VS to another many, many times over the years If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem.

In our case, we have Release configurations that remove the debug attribute from the web.config's compilation section.

  1. It turned out that for me it was a bad migration from VS2010 to VS2012 with the *.testrunconfig file.
  2. Aug 13, 2012 05:54 AM|coolblue|LINK Ok, I have still not solved this issue, however I have noticed something slightly odd about the web project (ie the startup project) in the solution.If
  3. If it is development then you might have to adjust the Project Properties -> click advance setting -> change debug info to 'full' in [output tab].
  4. Hope this posting was helpful.
  5. Why do governments not execute or otherwise permanently contain super villains?
  6. share|improve this answer answered Dec 31 '12 at 5:53 Ark-kun 3,7091431 add a comment| up vote 1 down vote You need to make DoStuff static.
  7. What should I pack for an overland journey in a Bronze Age?

Close and reopen Visual Studio or reboot and see if that clears it up. Please click here to request a new code. Try debugging again and see if that helps. Visual Studio Breakpoint Will Not Be Hit Source Code Different Test assembly was .NET 4.5, tested assembly was .NET 3.5, couldn't set breakpoints in either.

Any interpretation of data presented that leads to an investment is at your own risk and Wealth-Lab® will not be responsible for any losses that occur from such investments. Your right if he is using 2013! –ali Jafer Feb 25 '14 at 10:26 add a comment| up vote 0 down vote Are you sure you're attaching to the right w3wp Then do a dumpbin /PDBPATH:VERBOSE MyServiceExecutable.exe and scan the output for "PDB age mismatch" (Ref: http://msdn.microsoft.com/en-us/library/44wx0fef.aspx) Not sure about VS 2012, but older versions of VS had a bug where the have a peek here How to check whether a partition is mounted by UUID?

share|improve this answer answered Feb 25 '14 at 10:39 Danny Jessee 1,701915 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Now, I have a unit test: [Test] public void MyTest() { var results = MyService.GetStuff(); } I set breakpoints on my unit test, and I can see that results has data. The account information you provide will never be shared. The other projects honored breakpoints but this 1 didn't.

Login using C# Corner In Focus DOWNLOAD: C# Corner Android App Version 0.5.4 Why Developers Should Focus On Communication LEARN: How to become a Microsoft MVP C# Corner share|improve this answer edited Aug 6 '13 at 14:30 Nate 2,52621130 answered Dec 28 '12 at 19:59 Alan 5,77611542 8 +1 for "Make sure it's a debug build" - whoops! share|improve this answer edited Feb 25 '14 at 9:59 Robert Lindgren♦ 19.3k63154 answered Feb 25 '14 at 9:54 Nadeem Yousuf 14.8k31442 ya i have selected all w3wp.exe services –luckydeveloper No symbols have been loaded for this document".

I'm running the solution and IIS 8.5 on my own local machine so I wouldn't think that this has anything to do with our network. I've even tried making MyService constructor public and taking away all static methods, and it still doesnt work. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Check your assembly to see if symbols are loaded.

Or do I have 2 seperate issues? This works for me! share|improve this answer answered Dec 31 '12 at 0:16 sa_ddam213 28.4k45383 add a comment| up vote 8 down vote accepted It turns out this was related to Code Coverage being on. Ended up being an incorrect configuration selected in the debug menu.

It does concern me a bit though because we recently hired a new IT guy that's been making a lot of changes to everyone's machine.