One thing that has started to bother me since going to a VS 2010/IIS7 setup is that by default the time-out on the debugger is incredible short. You start looking into a problem and be on the point of realisation when a Message Box pops up saying that the thread is aborting.
Helpful, that is not.
After a little digging about I found that it has something to do with the application pool settings in IIS. To increase the time the thread is available open IIS Manager, open the application pool your site is running on and click "Advanced Settings". In the property dialog that comes up there is an item labelled "Ping Maximum Response Time (seconds)". Set this value to your desired value and click OK.
I have mine now set to 6000 which should be enough for now.
9 August 2011
8 August 2011
Arch KDE SC 4.7 Missing KDM Background
If after upgrading KDE to 4.7 on Arch you notice that your KDM theme is missing you need to run the following:
pacman -S kde-wallpapers
It turns out the KDM default theme use's an image from the KDE Wallpapers package which has been split out on it's own from 4.7.
pacman -S kde-wallpapers
It turns out the KDM default theme use's an image from the KDE Wallpapers package which has been split out on it's own from 4.7.
3 August 2011
Arch Linux Zope Interface Update Issue
The issue is old now, I have ignored it for about a month of pacman -Syu but in updating to KDE 4.7 tonight I hit it again.
If you pacman -Syu and get
error: failed to commit transaction (conflicting files)
python2-zope-interface: /usr/lib/python2.7/site-packages/zope.interface-3.6.3-py2.7.egg-info/ exists in filesystem
The you need to go to this page and follow the two simple commands.
It would appear to be a simple bug in pacmans conflict resolution handling. It had to happen sometime I guess!!
If you pacman -Syu and get
error: failed to commit transaction (conflicting files)
python2-zope-interface: /usr/lib/python2.7/site-packages/zope.interface-3.6.3-py2.7.egg-info/ exists in filesystem
The you need to go to this page and follow the two simple commands.
It would appear to be a simple bug in pacmans conflict resolution handling. It had to happen sometime I guess!!
Disable Visual Studio 2010 w3wp Warning
So I have finally got to switch to my new laptop (windows 7, i5 lots of RAM!) and reinstalled all my tools.
This first thing that started to really annoy me was that every time I attempted to attach to the w3wp.exe process to debug Visual Studio showed a message telling me it might be a bit dangerous to do so. Clicking OK allows you to attach and debug as usual. I had to find a way to disable that message.
Apparently you can and I have! Thanks to a great little post over at thethoughtfulcoder.com it appears this can be turned off in the registry.
This is great and saved me some keystrokes however, it is the kind of thing you should be able to disable in Visual Studio itself rather than have to dig about in the registry for.
This first thing that started to really annoy me was that every time I attempted to attach to the w3wp.exe process to debug Visual Studio showed a message telling me it might be a bit dangerous to do so. Clicking OK allows you to attach and debug as usual. I had to find a way to disable that message.
Apparently you can and I have! Thanks to a great little post over at thethoughtfulcoder.com it appears this can be turned off in the registry.
This is great and saved me some keystrokes however, it is the kind of thing you should be able to disable in Visual Studio itself rather than have to dig about in the registry for.
Subscribe to:
Posts (Atom)