Automatically attach to process in Visual Studio - asp.net

I have searched this site, and numerous others, looking for a solution to this problem. When I press F5 to start debugging my web app it will launch the default browser (IE in this case) with the web site. But if I want to debug the code I must goto Tools > Attach To Process.
In my previous job I was able to press F5 and the debugger would automatically start and I could step through the code, but I can't seem to do that here. To add to matters, there is someone else in the office whose also works as I would hope but he says he didn't do anything and doesn't know how to sort it.
I have tried numerous things, like adding debug="true" in the web.config but to no avail.
There must be a definitive way of achieving this, without having to resort to macros and the like.

I think it's not related to the button itself but could be the preferences you chose on startup. Go to Debug > Start Debugging on the menu. What button appears on the right of the menu?
HTH.

Ok I figured out a workaround to get it to work...Don't know why this occurs, maybe someone will be able to enlighten me.
But I closed all other Visual Studio solutions I had open and now it debugs properly. It was actually a colleague who put me onto this as he was in a similar scenario and just tried a lot of different things.
Any idea why this would be happening?

Related

Unable to build ASP.Net apps

I am trying to build and compile an ASP.Net solution. The solution is new. Here is how I create it:
For this demonstration I avoid creating anything post-creating the project,
And here are the errors that I am getting:
All errors above, lead to the following place:
Any direction would be greatly appreciated!
Thanks!
Ok, assuming you looking to create a asp.net webforms app?
Your screen caps look ok, and it not clear why your resulting application has errors, or build issues.
I would try to create another project, different name. See if that works.
Better, try tapping windows key, type in 2022, and then right click and try run as administrator, and see if that helps. (the default source folder might for some reason require elevated rights to work).
And if above does not work?
then I would try a repair, or even re-install of VS. Perhaps the templates are messed up.
Following your exact steps, my vs2022 created asp.net web applcation without issues.
best guess:
Your VS install is messed up, re-install, or repair.
tools->get tools and features.
Then: close the modifying window, and you should see this:
Try a repair.
Thanks Albert and everyone attempting to help!
What I did that solved the issue is to click the errors, and I was redirected to the following document:
Here, I deleted every tag that was highlighted in any of the errors, more specifically, things related to Video Builder Cloud Services (VBCS), and off I go :)

VS2015 Design view unresponsive issue

I am able to work in the Source view with no problems. However, as soon as I click Design the source freezes and hangs. The same thing happens when I switch to Split as well. I cannot find much documentation/support for this issue and wondered if anyone else ran into this as well or has a potential fix?
Firstly please make sure you have selected the project/solution you are working on ,on the left bar (esp. if working with multiple projects.)
When that is done, clean and rebuild your solution. When this is done , try again.
If all fails, restart your machine and IIS (in that order) and try again.

VS2010 opens website in notepad? bad hotfix?

I am using VS2010 on Windows XP pro (sp3, x86), and I just installed the hotfix kb2106584. This fix was reported by some people, example here, as having a fix for an issue I had with Asp.Net Development Server not getting opened properly from VS, which I was having previously. My issue was being caused by ESET NOD32 messing with the http traffic from devenv.exe and causing all the ports in my computer to get used up, however.
Anyway, as soon as that was finished, I opened my website back up, and clicked debug. Asp.Net Dev server pops up, which was what the hotfix was supposed to make happen, and then notepad++ opens with the tabs I had last time I used it, and IE never shows up. "Wait, what?" try it again. and again. Always notepad++, never IE, always with no new documents opened, just some completely unrelated stuff.
I've seen one other post on SO about this happening, here, but his issue was corrupted files/filesystem. My project is in source control, so I tried a delete&revert to yesterday's revision. Still opens notepad++, so that's not my issue.
I've also tried rebuilding, which did nothing, and deleting my local Solution files, which also did nothing. I restarted the program and then the computer, both to no avail.
I start to believe that this is the hotfix screwing things up, so I try to do a system restore to a couple days ago. Once again, no dice; it's still pulling up notepad++ instead of IE.
So, the questions become:
Is there a setting or two I can try changing to make it open the proper program again?
Or was this a bad/improper hotfix, and if so, how do I uninstall it? It doesn't show up in the Add/Remove Programs dialog, and I don't see an option to uninstall it in VS, or in the installer.
Thanks in advance.
[edit] Also note: Notepad++ is not actually opening the website file, it's just getting opened with whatever I left in it last time. I dunno if this helps at all, but I felt like details would be appreciated. [/edit]
Fixed:
Uninstalling n++, deleting EVERY registry entry & folder containing 'notepad++' (except one, from whose string I removed ";notepad++.exe"), then reinstalling n++ made VS stop opening notepad++.
Now it opens the default web-browser again.
[edit]
Note for anyone else out there who ends up with this specific and bizarre problem:
It would be worth a shot to try changing the "Browse With..." setting in VS, by r-clicking on Default.aspx to "Internet Explorer". My list included Notepad++ as an available internet browser.
This might be a better solution than the previous, if it does in fact work.
I didn't know this setting would allow Notepad++ as an option until I had to set it back to IE again after all this, and that may have been the problem all along. Apparently, VS just changes this setting sometimes. How or why N++ got put in as an internet browser is completely beyond me, but I did myself the favor of 'Remove'ing NotePad++ from the list, and you may wish to do the same.
Again, I'll never truly know whether or not I nuked everything when I could have changed a single setting that got mysteriously reset, but may this [lesson?] at least be recorded for posterity.
[/edit]
It took all of that to figure out that it [was?] a bogus registry entry somewhere that [may have been?] modified by the hotfix; a registry entry that neither notepad++ nor visual studio 2010 ultimate would clean up on uninstall or replace on reinstall
Which was it? I have no idea. Like I said, I didn't even use n++ this week until VS started opening it for me, and the only change I made was to install that hotfix.

Can't debug ASP.NET in VS2005 won't stop at break point

I have an puzzling problem. I have a new ASP.NET web application in VS2005 that runs fairly well, but I am having a problem and would like to set a break point to see what is going on. I have compiled the project in Debug mode. I have debug=true set in the web.config. But it appears that the IDE is not attaching to the process at all. Have I overlooked something? I am using the development server and not IIS. This has never been a problem in the past, but is this time.
Have I overlooked anything? Thanks for any help.
Rob
I had this issue a while back with VS2005. I don't remember where I got the following instructions from (copied them to a file which I'm now copying to you) but doing the following steps worked for me. It has something to do with IE8 attaching itself to multiple processes and messing up the debugger. Word of warning, this has you editing the registry, so use at your own risk / take all your normal precautions, etc.
Open RegEdit
Go to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet
Explorer -> Main
Add a dword under this key called TabProcGrowth
Set TabProcGrowth to 0
If you run into the same problem on
Vista or newer, you will also need to
turn off protected mode.
Please note also that I was/am running XP at the time, so I did not have to use the "Vista or newer" clause there. No idea if that has any adverse effects either.
Sorry if I am stating the obvious, but you need to Start Debugging <F5> rather than just running the executable after compiling. Are you doing this?
If you don't hit the breakpoint, you are either not debugging (F5) or your code isn't reached at all. If you want to know which of the two is happening you can throw an exception right at the code where your breakpoint is. If your application is failing at the exception, you know you are not running it with the debugger. If it doesn't fail at the exception you are simply not reaching that piece of code and you will have to look harder for which code you are actually running.
throw new Exception("if I see this exception, I am not running the debugger");
Or maybe you are running two instances of the development server. I've had that sometimes. Look in the Windows system tray for the icon. If you see two (or more) you can right click to stop them and restart debugging.

Visual Studio 2008 - The breakpoint cannot be hit

I know that many people have had this problem... but I am now having it and cannot solve the issue. VS 2008 is randomly giving me an error after working on a project for weeks. When I set a debug point, I get a warning: The breakpoint will not currently be hit. No symbols have been loaded for this document.
I have re-built the solution with no debug points and re-tried. I have also tried to Load Symbols from path and that has not worked either... Can someone please help walk me through the necessary steps to getting my debug function working again.
Thanks.
Delete the solutions suo file. This has fixed weird debugging problems with breakpoints every time for me. Note, you will lose your solution settings, such as bookmarks, breakpoints, and such.
1) Does creating a new project work? If so, you have a corrupted settings somewhere. Moving your files over to your new project would be the easiest procedure to resolve your issue.
2) Does taking your solution to another PC work? If so, then you have an issue with your environment.
Try these checks in order:
1) Select your Configuration Manager, check if your CPU is "Any" or your "x86" or "x64" depending on your hardware.
2) Try remove all the other configuration other than Debug. Add a new Configuration based on your Debug and the CPU as Any
3) Drastic move.. close your visual studio and run the following
devenv /ResetSettings
4) Even more drastic move...
devenv /Setup
Good luck
There is a hotfix for Visual Studio SP1 regarding debugging issues here. It did fix issues I had with catching breakpoints in multithreaded source code. It also fixes other potential causes for breakpoints to be missed, so it is definitely worth a try.
Also, have a look at this SO question.
Regards.
I run into this occasionally and each time the solution is a bit different. This time I was using a different user profile to develop than I normally do in Visual Studio 2008 and found that I couldn't debug (breakpoints cannot be hit) shortly thereafter - on a solution with 2 vb.net projects. I ended up doing 2 things but I think the latter did the trick for me.
In the main projects properties, go to the Advanced Compile
Options button on the Compile tab and ensure the "Generate debug
info:" is set to Full.
Right-click on the main project and
select "Set as a startup project"

Resources