I'm working with larger solution that has several website projects and recently it was decided to switch from Cassini to IIS Express. There are about 10 or so developers who all share the same solution/project and thus web.configs and they are all working happily with IIS Express except for me. The problem is that for no pattern I can figure out, IIS Express constantly resets itself and performs a new build thus resetting the session.
Here are some of the reasons it will rebuild itself:
Editing an ASPX file
Doing nothing for a few minutes
Editing code behind file
Using the web site as normal
Note: the above actions do not always cause a rebuild. Also many of these actions were perfectly fine using Cassini.
My system is pretty standard compared to the other developers who are not having issues.
Here is some more information:
I'm using VS2010 SP1 and Windows 7 Professional.
I started using IIS Express 7.0 but have since tried upgrading to 8 with the same results.
I've uninstalled/reinstalled IIS Express several times w/o any luck.
Using ReSharper 7.x
I've turned off edit and continue
I'm now in full debug mode and this constant rebuild/reset is becoming prohibitive.
EDIT: it is in fact rebuilding as verified using health monitoring per John Saunders' suggestion.
EDIT: one important thing I did not mention is this mainly happens during a debug session. Not only during debug session, but usually. In fact adding a break point, or even hitting a break point can cause a rebuilt.
I would look at Resharper as being the cause of the problem. Try completely disabling or uninstalling Resharper and see if the problem persists.
I've been much happier with coderush from dev express myself... I don't work for them just tried both and Resharper really bogged down my system and I didn't like it...
Related
I'm having a hard time fixing an error that I currently have and I hope you can help me with it.
I am developing a little ERP-WebSite that is going to be used within an intranet. Naturally I want to use Windows authentication to make it as comfortable as possible for the user. I developed the Website using Visual Studio 2008 and its integrated development server. Recently I migrated to VS2013 and .NET 4.5. Code wise everything went good and I am able to build everything but here comes the problem. Because I am using VS2013 now I also have to use IIS Express. When I try to debug the Website i receive a 401.2 Error. Error Code 0x80070005. On VS2008 everything worked perfectly and I am 99% sure I have the IIS config set up currectly. Here are the relevent parts:
applicationhost.config:
I also set the according values in the Project Settings in VS2013.
I'm kind of lost right now. Any help will be much appreciated!
EDIT--------------------------------------------------------------------------------------------------------------------------
After playing around with IISExpress for way to long now, I finally got it to work again. Something must have been wrong with my previous eddits of the applicationhost.config file of the IIS Express. I just deletet it and let VS13 recreate it. Afterwards I was able to run my site using IISExpress. I hope this might help someone who has the same problem as I do. Sadly i realized that it is painfully slow. It takes almost 2 minutes for some pictures to get loaded etc.. What could be the cause of that ? I also tried using the full IIS Version (with Win-authentication installed) but when I run my site using the local IIS I receive an XML-parsing error: No element found. Using the local IIS would be a lot faster than using IISExpress, so I'd very much like to fix this Error.
Thanks for any help in advance.
I have searched all the usual but come up empty. I must be doing something silly!
Simply I created a new project, ASP.NET Web App, and wish to use and debug it with the local install of IIS 7.5 on my Windows 7 x64 box.
According to what I have read it should be a simple process; my issue is that Visual Studio will not stop at breakpoints nor at errors etc.
I just don't get it:
Visual Studio is attaching to the w3p process for me automatically.
If I hover over the breakpoints it shows a message saying the same, that it is in the same w3p process.
I am in Administrator context. I manually ran it like so to be sure but in any case if you are an admin it runs like that anyway.
Some notes:
I do not wish to use IIS Express as I require native IIS 7.5 for my tasks, however it does debug in express - no surprise there.
As mentioned above, all this is being done locally.
The path of the virtual directory is pointed towards the project files, as set by Visual Studio 2010. It even set the Network Service as read on the folder structure.
When debugging from VS the web site runs fine, just debugging is the issue.
Maybe it is permissions? The Default App Pool is using the ApplicationPoolIdentity not Network Service... Should it be? I had assumed they we.re one and the same essentially. Although I changed this and no luck unless I didn't do something I should of
Keep in mind here that my issue is semi-unique in that I am not receiving error messages, not even in the event logs... For all intents and purposes it should be working fine, just it isn't.
VS and IIS, and all updates, are applied to date.
Note: I'm familiar with IIS7.5, I run my own public web hosting server. I just never tried to debug
Note: It is Visual Studio 2010 Ultimate
Thanks for your time.
Sigh!
I went back to basics... Uninstalled IISExpress and tested; It worked! Re-installed IISExpress; It worked!.
I guess installing IIS7 native after IISExpress did something screwy? I had ran the register ISS command on IIS7 when I installed it.
Right, so now I have both installed in tandem and they work fine. Thanks for all your help guys, appreciated.
you can try right-click on project in VS go to properties select web from left menu tab. Check if ASP.NET debugger is checked and also you can select Use Local IIS Server and give localhost url there (in project Url textbox) and then Say start debugging from VS and put breakpoints.
I had a similar issue the other day, I attached the debugger to the wrong w3p process, make sure you attach it to the one the app pool identity is running under.
I wanted to write it as comment by I don't think I can add pictures..
Are you sure you are running the same version of dll?
Is your breakpoint filled like this?
or hollow like this?
1st go to ,Program and Feature in control panel and then in that turn on or off windows features. and now check all check boxes(activate features) related to Internet Information server & windows service managers. once this is done run your visual studio as administrator and then attach to right w3p process.
We have an ASP.NET application running on a webfarm. When we release a new version and copy it to the production servers, occasionally it happens that after a few hours the application reverts to a an earlier code base.
Have anyone else experienced something like this? Would sharing an application pool between two applications running different versions of the code make this happen?
Additional information:
3 x web servers running w2k3/iis6
ASP.NET 3.5
I've had this happen rarely on non-precompiled sites and the solution was to stop IIS and clear out the temporary cache at:
%WINDIR%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
Is not a long-term solution, but will address the immediate problem. If not already, it is worth considering deploying the site pre-compiled.
Does anybody know if there are any major changes in IIS7.5 that is coming with Windows 7 that will require rewriting all or a portion of a major website (CMS). Obviously not knowing my code, it is hard to judge this, but I haven't found any announcements of what is expected in IIS7.5 and would like to get a heads up.
Don't expect any breaking changes. This document shows the changes.
IIS7 introduced a lot of new features, and was a somewhat dramatic change. IIS 7.5 just builds on on that. Some features that one can now download via the Web Platform Installer (like FTP 7.5) will be included in IIS 7.5 from the get go.
I've imported a few of my projects over to Win7's IIS and if you're coming from an IIS7 environment then everything hums (so far). If you're coming from a lower version of IIS then there are a few things that need to be taken into consideration (ex. system.webServer node in your web.config).
You're right however, I have no idea what your code is other than a CMS. From personal experience, I've encountered no problems.
I have an ASP.Net 2.0 web site, using the DotNetNuke framework (4.09), and it will not compile, but when I hit the site in a browser, it works. Even the parts that don't compile will work. How is IIS able to compile and run this site, when Visual Studio can't? Everything is the same in both places... I copied the entire web site from the remote server on to my local machine, then I set it up in IIS the same way. On my local machine, Visual Studio can't compile the site, but it still runs. How can this be possible?
The specific errors are not important, as there are 189 of them, from every possible part of the site. I'm not trying to fix the errors... what I want to know is how it's possible for the web server to run the site, regardless of the errors. Please pay attention to what I have written - everything is exactly the same in both places. There are no missing DLLs, no different configurations, nothing on the machine itself... remember, the site runs fine on my local machine.
Is this a web site or a web application? If it's a web application, you're probably still running off the last successfully built bits in the bin.
The site is using old dlls, or possibly you have references missing in your local version that the server has just fine.
As Mitchel said, we need to see the error before we can really answer your question.
To give you an answer on this we would need to know what the errors are.
Your local machine cached the 'working' copy and is using that maybe?
The site was compiled successfully at one point as it works on the remote server. Thus, copying it to your local machine and hitting the local site will also work. However, there can be several reason why you can't re-compile it on your local machine including; missing references, web.config entries, third party control licensing, etc..
I realize you are not trying to correct the 189 errors, but there are clues, if not answers, in the error listing that will get you moving in the right direction.