I know this has been asked before but I just cannot figure this out. I believe I have covered everything that has been brought up already but I'll cover those.
I am getting this message when I try to step into a service that is a project that is currently in my solution:
I have 3 projects in my solution:
SuburbanCustPortal <-- my website
SuburbanHub <-- my serice
WebsiteLogging <-- my logging project (no significance here)
I read that I should check the following items:
Make sure that debug is on. I have this in both of my project's web.config:
Make sure they are both using the same .net version. They are both on the .net framework 4.0.
Make sure Enable Just Your Code is unchecked:
The service is pointed to a local url:
I can pull up the service in my browser without error:
This is my settings for iis:
I have restarted visual studio, the computer and removed the service and added it back.
I cannot, for the life of me, figure this out. If I have missed anything I am willing to give it a shot.
It is very important that I get this resolved so I can get this project out this weekend so any help would be greatly appreciated.
IN RESPONSE TO Sanket Shah
I do not have the option w3wp.exe:
SOMETHING I FORGOT TO MENTION
I have set debug=true in both of my projects:
<compilation targetFramework="4.0" debug="true">
<assemblies>
<add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</assemblies>
</compilation>
Also, I wanted to add that I have been able to step into my service before but since coming back to the project recently, I am not able too. I have a break point on the line that calls the service and when I try to F11 in to it, I get the above message.
IN RESPONSE TO Pawel
I have tried setting symbols the follow ways and neither allowed me to step in:
I have even tried to use the Microsoft symbols:
IN RESPONSE TO Pawel #2
ADDITION INFO
I just noticed this, I'm not sure if it is related:
ADDITIONAL INFO ABOUT DEBUG MODE
I have all projects set in debug mode:
Your solution/project/settings file(s) might be / seems like it is corrupted. If you create a new solution from scratch, adding new projects which mimic your current structure, you can try and see if debugging works properly.
If that works, gradually move the code over while keeping checking that debug keeps working.
I don't know why this doesn't work.
I have a work-around for you, which you verified in the comments: add System.Diagnostics.Debugger.Break() somewhere in your service after it starts. This should pop up some sort of exception window, with a list of Visual Studio instances open. Pick the one with your solution and click OK, and it should attach correctly to that location.
Annoying? Yes. In my experience with Visual Studio, it can be very finicky sometimes about debugging into Windows services. This is the only reliable way to do it that I know about.
In addition to other answers, you can do two things:
Close your solution, delete [solution-name].suo file, reopen solution. See if your problem still persists.
Open a command prompt as admin, cd %windir%\Microsoft.net\Framework\v4.0.30319, execute this aspnet_regiis.exe -i.
In solution, have you tried to set all assemblies (client and server) to start in debug mode rather than trying to attach it after launch ? (right click on solution in the top of Solution explorer, startup, multiple startup project, choose "start" for every assembly which is an entry point : server, client, etc).
Have you tried to run only the "server" part in debug mode (the one which is not debuggable) and call it for example with soap ui ?
You should try to see if you can run it directly and debug it without the "step in" from another process, or if it also fails to load in debugger even if started directly.
FYI, if you use IIS Express it's normal you don't see "w3wp.exe", which is for IIS. You may have a iisexpress.exe process, or in some cases aspnet_wp.exe.
Don't forget to check "show processes for all users" in Debug->Attach to process window if you choose to hook on existing process rather than doing that I was saying first.
Go to Properties of the solution select Multi statup project and select all projects with start, then debug the solution.
I am running an asp.net project onto a local IIS Express server and none of my breakpoints seem to be active. Ive tried switching to normal IIS but to no avail
I managed to get a breakpoint to hit in Global.asax.cs but everything else (such as my BaseController) doesnt get hit.
It directs me to my login page (which I am trying to remove, but seemingly cant) yet the Logon function in the AccountController never gets hit either.
I simply get the hollow red circle where the breakpoint is set that tells me my source doesnt match the original version. Ive tried restarting VS, cleaning the solution, even manually deleting the bin files.
Any ideas?
Answers to questions
Yes I am running debug
<compilation debug="true" targetFramework="4.0"> is in my web.config
I have tried running the website in both Chrome and IE after running
have you wrote in web.config debug = true and check the internet explorer setting is degugging in other is disabled? for internet setting check internet debug settings
How about deleting Temporary ASP.NET files?
Located at: C:\Windows\Microsoft.NET\Framework64\<version_number>\Temporary ASP.NET Files
a few things to try:
CLEAN solution then REBUILD
Debug > Attach to process and attach it to the IIS worker process if you are hosting the site in IIS.
Cleaning the temp ASP.NET files
Making sure that the site is built in DEBUG mode - sometimes even setting it into RELEASE mode will not hit the breakpoints as all the symbols are stripped out but even then other factors to consider in this context
Delete all your breakpoints and just add 1 - what happens?
I simply get the hollow red circle where the breakpoint is set that
tells me my source doesnt match the original version.
This may be the clue to what is going wrong. I had this same exact problem just recently, and I had to turn off "Just My Code" as part of the debugging options. To do this, in Visual Studio, go to:
Tools > Options > Debugging > General
and then clear or enable Just My Code. Clean and Rebuild as others have suggested and that should fix your issue with breakpoints. (It did mine, at least.)
It turns out the issue was due to my build directory, I found this answer which made me check and after fixing this it instantly started to work properly!
Using VS2008 and R# 5 I'm running into an odd situation, where on an aspx page I keep getting
Cannot resolve symbol 'symbolname'
But the code compiles and runs fine. While having a fix for this would be great, I'm just trying to figure out if I'm losing my mind.
The CodeFile directive and Inherits directives are fine. If I compile the app or just let devenv sit for a bit it'll go away, but as soon as I save the aspx [via ctrl+s] R# suddenly has trouble with the Inherits attribute and flips out on every method in the page (OnClick etc).
// Anonymized of course but otherwise intact
<%# Page AutoEventWireup="true" CodeFile="TestPage.aspx.cs" Inherits="TestPage" Language="C#" MasterPageFile="~/MasterPage.master" Title="Test Page Title" %>
This is mostly just a grievance, because since the code compiles it doesn't stop me from doing what I need.
I would post a bug report to the JetBrains site but first I would like to know I'm not alone. It could be my machine. Maybe when I roll to VS2010 in a couple weeks this will go away?
In Resharper you can disable inspection for that file with: Ctrl + Shift + Alt + 8.
So no final resolution yet. According to tech-support this is a known issue and is being researched. Final resolution undetermined at this time. If you're experiencing a similar issue, just hang tight. URL: http://youtrack.jetbrains.net/issue/RSRP-178681
Nothing worked for me until I followed this answer -- removing the related reference from the Project/References and then adding it again.
This worked in my case (Visual Studio 2015):
Go to Menu and select Options.
From the opened window, select ReSharper Ultimate (yours might be different edition) and click Suspend. That will basically suspend all the resharper features. Then click "Resume"
That should work. Otherwise, try to clean Resharper cache.
I just tried something odd and it worked. In your page directive, change the AutoEventWireup to false, SAVE the file, then change it back to true. It's some connection between the aspx file and the designer I think.
Try delete your .vs folder (hidden folder). It will reset config and cache of your solution
Suspend and and restarting Reshaper worked. Issue was resolved.
I have an ASP.NET MVC (beta) application that I'm working on, and am having trouble figuring out if I'm doing something wrong, or if my Application_Start method in Global.asax.cs is in fact not firing when I try to debug the application.
I put a breakpoint on a line in my Application_Start method, and am expecting that when I attempt to debug the application that the breakpoint should get hit... but it never does. Not after I reset IIS, not after I reboot, not ever. Am I missing something? Why is this method never getting called?
Note : a nice easy alternative to using the inbuilt "Visual Studio Development Server" or IIS Express (e.g. because you are developing against IIS and have particular settings you need for proper functioning of your app) is to simply stay running run in IIS (I use the Custom Web Server + hosts file entry + IIS binding to same domain)
wait for debugging session to fire up ok
then just make a whitespace edit to the root web.config and save the
file
refresh your page (Ctrl + F5)
Your breakpoint should be hit nicely, and you can continue to debug in your natural IIS habitat. Great !
If this is in IIS, the app can get started before the debugger has attached. If so, I am not sure if you can thread sleep long enough to get attached.
In Visual Studio, you can attach the debugger to a process. You do this by clicking Debug >> Attach to process. Attach to the browser and then hit your application. To be safe, then restart IIS and hit the site. I am not 100% convinced this will solve the problem, but it will do much better than firing off a thread sleep in App_Start.
Another option is temporarily host in the built in web server until you finish debugging application start.
The following helps in any case (no matter if you're using IIS, Cassini or whatever):
Set your breakpoint in Application_Start
Start debugging (breakpoint most probably is not hit) -> a page is shown in the browser
Change web.config (e.g. enter a blank line) and save it
Reload the page in the browser -> breakpoint is hit!
Why does this work? When web.config is changed, the web server (IIS, Cassini, etc.) does a recycle, but in this case (for whatever reason), the process keeps the same, so you keep attached to it with the debugger (Visual Studio).
I'm too having problems with breakpoints in application_start with IIS a hosted app. A good workaround is using Debugger.Break(); in code instead of the VS breakpoint
I have just the same problem. I have made a lot of renaming in my solution. After it I got two not working web-applications and several another web-applications were all right. I got error that I have wrong routes. When I have tried to setup break point in Application_Start method, and then restart IIS, VS didn't break execution. With workable web-applications break was working. Then I have recalled that "clean solution" and "rebuild" doesn't delete assemblies that left after renaming. And that was solution! I have manually cleaned bin directories of my buggy-web-applications and then saw new error in Global.asax Inherits="" attribute was referenced old dll. I have changed it on new and break began to work. Suppose that, during renaming Global.asax wasn't updated, and IIS took old assembly (with wrong routes) to start application.
Had the same problem in a Project we had taken over after another vendor built it. The problem was that while there were a number of commands written by the previous vendor in Global.asax.cs, which might lead you to believe it was in use, it was actually being ignored entirely. Global.asax wasn't inheriting from it, and it's easy to never see this file if the .cs file is present - you have to right-click Global.asax and click View Markup to actually see it.
Global.asax:
<%# Application Language="C#" %>
Needed to be changed to:
<%# Application Codebehind="Global.asax.cs" Inherits="ProjectNamespace.MvcApplication" Language="C#" %>
Where ProjectNamespace is whatever the namespace is of your Global.asax.cs class (usually the name of your Project).
In our case the file contained a bunch of inline code, some of which was copy-pasted from the .cs file, some not. We just dumped the inline code over to the .cs file and gradually merged our changes back in.
Try switching the managed pipeline mode for the app pool to "Classic" instead of "Integrated". That solved the problem for me. Looking into the reason now...
(Props for this answer belong to Flores (see his comment on his own answer), I just wanted to provide this as a separate answer to draw more attention to it)
Make sure that your global.asax in not under a subdirectory. It has to be placed at root level into your project.
We had a similar problem, where global.asax.cs was being ignored.
It turns out that the site was upgraded from a precompiled .NET 2 web site to a .NET 4.0 site. On the server, the PrecompiledApp.config file had not been deleted from the root folder. After deleting it, and recycling the IIS app pool and touching web.config to restart the application, code in Global.asax.cs started working fine.
I had a problem once where the Global.asax and Global.asax.cs were not actually copied to IIS folder by the deployment scripts...
So it worked when debugging on the development server, but not under IIS.
A late entry...
To test whether or not the IIS Application gets started before the debugger has had enough time to attach just add this to the top or bottom of your GLOBAL.ASAX's Application_Start.
throw new ApplicationException("Yup, it fired");
I faced this problem when using a static page (e.g. index.html) as the start up page - Application-Start does not get called. I discovered that serving a static page does not actually start the application. Requesting an .aspx page does.
Make sure the namespaces in Global.asax and Global.asax.cs are same. If they are different it will not throw any error but will not hit the breakpoint also because it is not executing application_start at all.
When you say "debug", do you mean actually launching the application from Visual Studio's built-in webserver for debugging, or do you mean attaching to the process in IIS? If it's the former, you should hit Application_Start, but if it's the latter, it can be difficult to be on the process early enough to catch it.
Close Visual Studio and delete the bin and obj folders in your web project (or all projects in the solution).
Here are commands to delete these folders from all of your projects:
rm *\bin -r
rm *\obj -r
I had made some changes based on "Code Analysis on Build" from Visual Studio. Code Analysis suggested "CA1822 Mark members as static" for Application_Start() in Global.asax. I did that and ended up with this problem.
I suggest suppressing this Code Analysis message, and not alter the signature of methods/classes automatically created by platform used for bootstrapping the Application. The signature of the method Application_Start probably was non-static for a reason.
I reverted to this method-signature and Application_Start() was firing again:
protected void Application_Start()
{ ... }
I think the application start event only gets fired when the first request is made, are you hitting your website (i.e. making a request)?
I had this issue in a .net 4 web forms vs2010 project and tried everything mentioned on this page. Ended up removing and adding global.asax actually resolved the issue for me.
I hade the same problem, couldn't catch Application_Start.
And the reason was that it was not firing do to a missmatch in the markup file.
The markup file Global.asax was inheriting another class...
Did you check the Project settings?
I had this problem and I had the Start URL going to a different port than my server specific port.
It took me too long to figure out...
After trying as many of the other answers as were applicable in my situation and having no luck with any of them, I went into the properties for the Web project (the server-side project for a Silverlight app using RIA Services), clicked on the "Web" tab and changed the selected Server from "Local IIS" to "IIS Express". (Note I'm using VS2013.) This solved the problem. Application_Start executes under "IIS Express" but not under "Local IIS". Interesting...
I was trying to step through code in RegisterRoutes() called from Application start and not hitting my breakpoint. I determined Application_Start was not getting called. I had to make a change to make a superficial change to App_start/RouteConfig.cs and save it before Application_Start would get called. I guess these files get cached somewhere and are not called unless a change is made.
My same issue has been resolved by Adding reference of System.Web.Routing assembly in project
If you are using the System.Diagnostics.Debugger.Break(); workaround (which I think is just fine for temporary use) and it's "just not working" on your Windows 8 Machine. The reason is a bug in Visual Studio's "Just in time debugging".
The fix is as follows is to fix the key for the "Visual Studio Just-In-Time Debugger"
Open regedit and go to HKEY_CLASSES_ROOT\AppID{E62A7A31-6025-408E-87F6-81AEB0DC9347}
for the ‘AppIDFlags’ registry value, set the flag to 0x8
More info here:
http://connect.microsoft.com/VisualStudio/feedback/details/770786/just-in-time-debugging-operation-attempted-is-not-supported
In my case, killing the built-in ASP.NET Development Server instance via the system tray resolved the issue.
Weird and crazy stuff... but debugging on a server machine and another user left IIS Express running on their session. I had to logoff that user to kill his running IIS Express processes. That seems to have fixed the problem!
Update
After spending more than 1 hour chasing what was causing the problem... here's the deal: I somewhat managed to type an s inside the <appSettings> section in Web.config. Visual Studio tried to warn me in the Error List window with a warning. I confess I rarely check warnings... should start checking it from now on. :D As soon as I removed the offending s the breakpoint got hit in Application_Start.
I had this problem when trying to initialize log4net. I decided to just make a static constructor for the Global.asax
static Global(){
//Do your initialization here statically
}
Problem mainly occurs when you try to relocate the Global.asax file to another solution directory. Relocate the Global.asax file again into the default location. It will work as expected.
None of the solutions described above worked for me.
However reinstalling the package
Microsoft.CodeDom.Providers.DotNetCompilerPlatform
using nuget gui is a (not too nice) walkaround
I've added a label control to a webform. It appears when I run the page but when I try to reference it using the codebehind, I get no intellisense and the code I write somehow doesn't work. I've verified the project is running in debug, that debug compilation is set in the web.config. In fact, I can debug all pages. However, when i go to this page, debugging runs over it as if there is no breakpoint set. Also, on the breakpoint, it says 'The breakpoint will currently not be hit. The source code is different from the current code' which has the be the main issue. Not sure why that's happening as I recompiled the whole project.
I have this at the top of the page:
print("<%# Page Language="C#" AutoEventWireup="true" CodeBehind="MemberSearch.aspx.cs" Inherits="Portal.EmployerPortal.MemberSearch" Debug="true" %>
");
Any ideas?
In the past I've had problems with this because the auto-generated designer files were bad. Try deleting them and then allow VS to recreate them, this may fix the problem.
Try doing a Build -> Clean Solution
Something similar happens to me from time to time...I add a control and I get no intellisense...VS basically has no idea the control is on the page/designer. If I close the file (codebehind and HTML) and come back...everything is honky dory. Clunky, but it works. Worth a try. I'm using 2008 BTW.
This is a common problem with VS.
Usually the cause is the .designer files are not re-generated due some sort of layout problems.
After deleting the .designer file right-click on the project name in the Solution Explorer and select Convert To Web Application.
If this is not helping either read the following article for more information.
In Visual Studio menu Tools|Option and found that on the Text Editor|All Languages that the three checkboxes for Statement Completion where showing neither empty or checked but a fully coloured box - which usually means an unknown settings. So a set these all to checked (a tick) and my Intellisense started working
for more details use following link
http://forums.asp.net/t/1520617.aspx?Intellisense+not+displaying+controls+in+the+code+behind
In windows 8 for some reason I have to run visual studio as administrator explicitly to get intellisense in my views.