visual-studio-debugging

Connecting to Visual Studio debugging IIS Express server over the lan

强颜欢笑 提交于 2019-11-26 23:41:24
I have a test ASP.NET MVC3 application developed in VS2012. When I start debugging the app is accessed from the host machine via the request to http://localhost:<portnumber> . But if I try to access the same application from the remote machine in the intranet via the http://<ip>:<portnumber> I get HTTP error 400: Bad request. Invalid Host Name. As far as it runs on IIS Express any server configuration is inaccessible. Are there any ways of solving this? Garrett Fogerlie Update I made a video that better describes the process, https://youtu.be/5ZqDuvTqQVs If you are using Visual Studio 2013 or

Attaching to a child process automatically in Visual Studio during Debugging

扶醉桌前 提交于 2019-11-26 22:41:28
问题 When writing plugins for media center your plugin is hosted in ehexthost.exe this exe gets launched from ehshell.exe and you have no way of launching it directly, instead you pass a special param to ehshell.exe which will launch the plugin in a separate process. When we are debugging media browser I find the process of attaching to a second process kind of clunky, I know about Debugger.Attach and also of some special registry entries I can use. Both these methods don't exactly fit my bill.

Enable the javascript debugger in the Page Inspector

南笙酒味 提交于 2019-11-26 22:36:35
问题 Visual Studio 2012 comes with the very nice Page Inspector. I like it! Problem though, I haven't found how (if?) I can turn on JavaScript debugging. Could someone point me in the right direction? 回答1: In IE9 (only one time): Tools > Internet Options > Advanced tab > In Browsing category > Clear "Disable script debugging" check boxes (both) > restart IE. In VS 2012: Run the Page Inspector ( when javascript error box opens, click No ! ) Choose from VS menu: DEBUG > Attach to process... Select

Does IIS Express support Debugging Classic ASP?

只谈情不闲聊 提交于 2019-11-26 21:35:55
问题 I recently installed Visual Studio 2010 SP1 BETA , ASP.NET MVC 3 RC2 and IIS Express . I successfully got an MVC 3 project running along with classic ASP pages in the project with IIS Express . I was wondering if there is a way to set up Classic ASP debugging with breakpoints in Visual Studio while using IIS Express? If so, are there any tutorials / posts on how to do this? 回答1: Enable ASP debugging in IIS Express: First, you need to locate the appropriate applicationhost.config file to

Visual Studio 2017 Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run

人走茶凉 提交于 2019-11-26 21:32:22
问题 I updated Visual Studio 2017 to version 15.8.2. After this update, I started to encounter these errors while debugging: Here are the error messages: Visual Studio Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run. This may have changed the state of the process and any breakpoints encountered have been skipped. This error shows up quite often, and after a while Visual Studio crashes. I tried to uninstall and install Visual Studio

Page uses an invalid or unsupported form of compression when debugging ASP.NET MVC app with Visual Studio 2013 Preview

爱⌒轻易说出口 提交于 2019-11-26 21:18:37
问题 While trying to debug an ASP.NET MVC project using the recently released VS 2013 Preview I get this message: Content Encoding Error The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. Please contact the website owners to inform them of this problem. In Firebug I see this error message: SecurityError: The operation is insecure Tried with Google Chrome and IE 11 and the same problem happens. What is causing this? Note: I'm on Windows 8

Lazy<T>: “The function evaluation requires all threads to run”

别等时光非礼了梦想. 提交于 2019-11-26 20:24:49
问题 I have a static class with some static properties. I initialized all of them in a static constructor, but then realized that it is wasteful and I should lazy-load each property when needed. So I switched to using the System.Lazy<T> type to do all the dirty work, and told it to not to use any of its thread safety features since in my case execution was always single threaded. I ended up with the following class: public static class Queues { private static readonly Lazy<Queue> g_Parser = new

Debugging MVC application in VS2012 attempts to start IIS Express twice

点点圈 提交于 2019-11-26 20:22:34
问题 UPDATE I'm certain this is a Visual Studio bug with no obvious solution. I've encountered a number of people who have the same exact issue. I have submitted a bug ticket with Microsoft here: http://connect.microsoft.com/VisualStudio/feedback/details/778864/vs2012-is-spawning-two-iisexpress-processes-when-attempting-to-debug If you are having the same issue as described below, please go vote up the bug ticket so that it gets more attention. Whenever I attempt to debug an MVC3 (or MVC4)

The Following Module was built either with optimizations enabled or without debug information

本秂侑毒 提交于 2019-11-26 18:50:42
问题 I cannot get rid of this in my VS 2008 web project when debugging. I've checked that it's in debug mode on the non-web project in question and it's in Active(Debug). Deleted all items in my .NET 2.0 temp folder in Windows. Not sure what else to do here. 回答1: Try disabling "Enable Just My Code" in Tools/Options/Debugging/Options. 回答2: I had the same problem and discovered that I wasn't outputting my debug info on my build. If you right click on the project and go to 'properties', then select

Unable to start debugging on the web server. Could not start ASP.NET debugging VS 2010, II7, Win 7 x64

自古美人都是妖i 提交于 2019-11-26 17:12:16
I am running Visual Studio 2010 (as Admin), IIS 7 on Windows 7 x64. I am able to run the ASP.NET web site in IIS 7 without debugging just fine, but when I press F5 to debug it, I get: Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging. Unfortunately the help link is not helping me much and leads down a heck of a large tree of things. I checked the following: Security requirements — I don't recall having to do anything special before. The worker process in IIS7 is w3wp.exe. It says that if