I'm a fan of the new VS 2010 Web.config transformations. I use this feature for deployment purposes and wondered if it is possible to use them for debugging too.I think of using them in the IDE: I want to create different built configuration (with linked transformation configurations); choose one of them; start the web site in the IDE and debug the different configurations this way.
View 3 RepliesWe have a couple transformations available for our web.config. How can I enable one of our staging or release configurations in my development environment? I'm trying to duplicate an issue from our staging environment in my development environment. Is this possible?
View 3 RepliesIf application is started without debugging - it runs smoothly, when I press F5 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. Click Help for more information"I noticed that problems are caused by URL Rewrite section in web.config:
<rewrite>
<rules>
<clear />
<rule name="LowerCaseRule" stopProcessing="true">
<match url="[A-Z]" ignoreCase="false" />
when I comment it out - I can start debugging. Also debugging works on VS's built-in web server.I'm running Win7 64 bit, VS 2010, application's framework is 4.0, in IIS application has ASP.NET 4.0 Intergrated pool set
I've been searching around on a way to use the new features of web deployment in VS2010, namely the transformations for config files, but everything I reference just says "right-click on web.config and add config transforms".Is it possible to do config transforms (and get all of the other publish goodness) in a 3.5 ASP.Net MVC project in VS2010? Is it just an msbuild file?
View 7 RepliesWhen you run an application in the debugger, it appears to not apply the transformations to the web.config based on your build selection. Is this the case or am I missing something? It appears to be working just fine if I publish to local IIS, just does not seem to work in the debugger.
View 1 RepliesI found an article which explains how to perform a Web.config transformation on an ASP.Net 4.0 Web Site, but all of my web sites are still running ASP.Net 3.5.[URL]
View 1 RepliesI really like the new transformation feature for the web.config. It seems to work when I do "Build deployment package" but not when I just want to locally start the debugging using the green arrow. It just uses the web.config without processing theWeb.Debug.config. I can prove that because in web.config I have debug="false" with a transformation in Web.Debug.config so that it gets true but everytime VS asks if it should modify the web.config to enable debugging which it should've done automatically with the following transformation:
[Code]....
Am I missing something here? I used to work with NAnt to modify/create the web.config as a pre-build event but I thought that I wouldn't need it anymore. Am I wrong? The project is a freshly created asp.net mvc 2 web application.
I'm trying to develop my first web application using Web.Config transformations.Trying to run the app (building with the "Dev" build configuration)in the Asp.Net Debugging web server built into VS the site doesn't seem to work - the "Web.Dev.config" configuration doesn't appear to be seen by the application.
View 1 RepliesI've just enabled config transformations on a .NET 3.5 project in VS2010 RC after watching Scott Hanselman's video on web deployment. Unfortunately every time I go to publish I now get the following error:
The "TransformXml" task failed
unexpectedly.
System.UriFormatException: Invalid
[code]...
If I take a brand new VS2010 web application which already has the configtransformations by default I don't have a problem so I suspect my issue is project related.
I'm trying to debug my web application on my localhost machine in Visual Studio 2010 and I keep getting this error: "unable to start debugging on web server. The Microsoft Visual Studio remote debugging monitor(MSVSMON.exe) does not appear to be running on the remote computer."
Is there a way I can turn this off as I'm not trying to make any attempts debugging remotely.
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 it's running as ASPNET or NETWORK SERVICE I must have Administrator privileges to debug it. How do I find out if I need to change something here? Web site Property Pages > Start Options > Debuggers > ASP.NET is checked. Use custom server is set to the URL of the site (which works fine without debugging). Debugging is enabled in web.config. Application is using ASP.NET 3.5 (I want to move to 4.0 eventually but I have some migration to deal with). Application pool: Classing .NET AppPool (also tried DefaultAppPool). Surely it shouldn't be that hard to install IIS, VS, create a web site, and start testing it?
I just installed VS2010 and opened the root machine.config and web.config files for review and I found some errors. In machine.config, the following line has errors in both entries for <Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior>. When I hover the cursor over them I get a tooltip text which displays: "The element 'endpointBehaviors' has invalid child element 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior'. List of possible elements expected: '...(list of options here)...'. The same problem happens for the second appereance in tag <serviceBehaviors>.
[Code]....
In web.config, there is a tag called <protocols> that has an error with a tooltip text that says "The element 'system.web' has invalid child element 'protocols'. List of possible elements expected: '...(list of options here)...'.
I want to use the web.config transformation that works fine for publish also for debugging.When i publish a web app, visual studio automatically transforms the web.config based on my currenc build configuration.How can i tell visual studio to do the same when i start debugging.On debug start it simply uses the default web.config without transformation.
View 5 RepliesI am trying to debug an ASP.NET website in VS 2010. The website is running in classic pipeline mode in IIS 7 on a Windows 7 64 bit machine. For some reason my breakpoints are never hit. I use the attach to process method to attach to the w3wp.exe process. I do not have enable 32 bit application enabled on the app pool. If i use the integrated mode it does work. i would rather use the classic mode since my production server runs IIS 6.
View 1 RepliesI have a problem with Visual Studio 2010. When I start debugging it works slowly.
Internet Explorer opens, but the website loads extremely slowly.
My workmate and me work on the same project and he doesn't have any problem like that.
My hardware is 4G memory + Intel Core i5 CPU 3.20 GHz.
I stopped my anti-virus program but it couldn't be resolved.
All of a sudden my debugging is taking forever to start on localhost (several minutes). It also takes a long time to return to the vwd after I stop debugging.
I haven't done anything that I can think of that would change anything (it has worked in the past, although the slow stop may have been there for some time.
The only thing I did was to add another user to the membership db.
I think it's a problem with starting the localhost development server.
Overall debugging works, but each step through code takes dosens of seconds.
I've already closed all additional windows like stack trace,watches,autos; deleted all breakpoints.
server and dev machine are located in different domains, so i set up local user on both, with matching password. remote debugger is running as service.
looking at security log, I found quite a lot of entries about remote debugging account logging in (record about every minute).
how i can speed up remote debugging?
dev computer: quad core, 8 Gb mem, win 7 x64 , visual studio 2010 ultimate target server: asp.net website , 2xdual core xeon, 2Gb mem, remote debugger 2010communication channel: vpn , 5 mbit , latency about 20ms. (seems that debbugging never uses more than 20 kb/s)
is this something basic or am I missing something?My ASP.NET (4.0) site has a web.config with URL rewrite rules. When I run it in debug mode (local webserver) all the URLs fail because the local web server does not recognize the rules (e.g. I have /register which maps to register.aspx etc.)Is there someway I can get the debug system to recognize my URL rewrite rules? Should I be doing something else?
View 2 Repliesi have problem with Visual Studio 2010 on Windows 7 x64. When i started asp.net site debugging, it stoped working. Only solution is restarting IIS.
Have anyone experiences with this?
All of examples on web assume the remote server which we are going to debug remotely is on the same network. I have only a static IP address and using RDP I connect to server.
I've installed Remote Debugger on remote machine but cannot set the static IP address as Qualifier in visual studio -> debug -> attach to process
I'm creating a website in Visual Studio 2010. I would like to use Visual Studio for C# debugging, but it also uses Visual Studio as JavaScript debugger. Is there a way to disable script debugging for Asp.Net website projects? I run my projects by hitting F5 in my Visual Studio. (I've noticed that when I attach the debugger manually, I can specify the type of stuff I would like to debug.) Note: I would like to debug, but not with Visual Studio. The developer toolbar is enough.
View 3 RepliesI am debugging an ASP.Net C# application in Visual Studio 2010, the application is running and execution is currently stopped at a breakpoint. How can I stop the page execution without "Terminate All" or killing the debugging process altogether, similar to what would happen if an unhandled exception was thrown? The "Break All Cntl+Alt+Break" option is grayed out in the Debug menu.
I want to stop the app from running but not have to go through a compile/start again. EDIT: I want execution to stop, not break, so that the page finishes loading and I don't continue running the application from the breakpoint forward. I've looked through the Breakpoints panel, the Debug menu and have right clicked all over but still haven't found the right option.
I get this error when I hit F5 in VS 2008. I have checked that Windows authentication is enabled on the site and it is. I can mannully attach the debugger to the IIS process and it works. What could be wrong? I have tried alot of things without success.
View 2 Repliesi am working on ajax slideshow extender.
1) implement transformations between slide to slide.
2) and the direction means orientation in changing of slides.
I'm struggling to get web.config transformations working with automated builds. We have a reasonably large solution, containing one ASP.NET web application and eight class libraries. We have three developers working on the project and, up to now, each has "published" the solution to a local folder then used file copy to deploy to a test server. I'm trying to put an automated build/deploy solution in place using TFS 2010. I created a build definition and added a call to msdeploy.exe in the build process template, to get the application deployed to the test server. So far, so good!
I then tried to implement web.config transforms and I just can't get them to work. If I build and publish locally on my PC, the "publish" folder has the correct, transformed web.config file. Using team build, the transformation just does not happen, and I just have the base web.config file. I tried adding a post-build step in the web application's project file, as others have suggested, similar to:
<target name="AfterBuild">
<TransformXml Source="Web.generic.config"
Transform="$(ProjectConfigTransformFileName)"
Destination="Web.Config" />
</target>
but this fails beacuse the source web.config file has an "applicationSettings" section. I get the error Could not find schema information for the element 'applicationSettings'.I've seen suggstions around adding arguments to the MSBuild task in the build definition like
/t:TransformWebConfig /p:Configuration=Debug
But this falls over when the class library projects are built, presumably because they don't have a web.config file.