Configuration :: Deploy Code With Both Release And Debug Mode
Jan 19, 2011
any way to deploy code with both release and debug mode together. I know it is logically impossible.
My requirement is to deploy debug based aspx page(for temporary) in release mode build in prod.. the concept is to avoid to put full release build on production again & again.
I am developing a web site in Visual Studio 2008. I have a project for the web application and several class libraries as references. When I add the references I select the file under bin/debug in the class library folder. When changing the project to release mode the references still point to the .dll in the debug folder. Shouldn't this change automatically. How should I add the references so that debug and release are properly referenced?
I'm on Windows Server 2008 with IIS 7.5 I have set up two web applications on the web site; one for the debug-build and one for the release-build for our system. I have not been able to figure out how to setup the two web applications so that they do not share the same native module.
When I access the debug-application (http://dev1/debug) it loads "G:workspaces ewreposdebuginRXWeb.dll" and the site works fine. However, when I access the relase-application (http://dev1/release) it also loads the "G:workspacesewreposdebuginRXWeb.dll" which is not want I want. I want it to load the "G:workspacesewreposeleaseinRXWeb.dll". Apart from that the relase-application works fine, loading for example its own database, javascript-files, images and so on.
I have tried many different configuration but obviously there is something I do not understand.
These are the changes I have made to applicationHost.config:
Under the section <globalModules> the following to rows are added at the end:
<add name="RXDebug" image="g:workspaces ewreposdebuginRXWeb.dll" /> <add name="RXRelease" image="g:workspaces ewrepos eleaseinRXWeb.dll" /> The web.config for the debug-application looks like this: <?xml version="1.0" encoding="UTF-8"?> <configuration>............
I'm trying to find a definite explanation of what effect compiling in release mode has on a .Net 3.5 web application versus debug="false". So far it looks like setting debug="false" has the same effect and compiling in release mode has been depreciated but I can't find any firm evidence this is the case.
This question looked promising but seems to be answering what's the difference between debug and release builds rather than release mode and debug="true":
[URL]
However it does link to this article:
[URL]
"This new compilation model makes the Configuration Manager for a web site obsolete. The only option appearing in a Visual Studio 2005 web site "project" is a Debug configuration. Don't fret - it means nothing. The web.config file now rules the school."
Now that is the closest I've had to an answer and it does seem to imply that release mode has been depreciated in favor of debug="false" but I can't find any confirmation of this on MSDN or any other source.
clarify this is a "Web Application Project" I am referring to.
To rephrase my question slightly, if I have the following setting in web.config:
<compilation defaultLanguage="c#" debug="false">
What effect (if any) does release and debug mode compile have?
I got a project when after opening in visual studio 2005 in build mode drop down, only debug mode is shown but release mode not shown.Project builds successfully in debug mode is there a way to enable release mode.
I have few confusions about build. What is release build and debug build? What are the output files for these builds? I had seen debug and release folders in bin folder. So the respective output goes into the respective folder? elaborate release and debug build. I dont want the difference.
I wish to compile my asp.net MVC application using aspnet_compiler.exe from the comandline to speed up cold startup.
I'm wondering how it determines if it should do a release or debug build. Is it always release? Does it depend on what the web.config file says when you run aspnet_compiler.exe?
What happens to an application that's been compiled w/ aspnet_compiler.exe if someone changed the debug attribute in the web.config file after it has been published?
What is a good approach to managing a debug and release connection string in a .NET / SQLServer application? I have two SQL Servers, a production and a build/debug and I need a method of switching between the two when my ASP.NET application is deployed. Currently I simply store them in the web.config and comment one or the other out, however that is error prone when deploying.
I can't see anything about this in the forum, yet it's a problem I have both on my VPS demo box and on some live boxes too:
When I deploy anything requiring a re-compile (e.g. not just an aspx.cs, but a .cs file) about once in every three times, IIS crashes.
This then requires not just a restart of IIS, but a reboot of the entire server, to bring it back again. If I try to restart just IIS, it won't actually "stop", so it won't then start again.
I therefore try to only deploy updates late at night, but in urgent situations a problem which needs rectifying can be made much worse by an additional 5 minutes of hard downtime while the box reboots. I can't predict when this will happen, but now warn all my clients against any updates during "office hours".
Is this a known bug/fault - can I get around this, preferably not by using RDP and stopping IIS completely before I FTP the files across?
I have an application that uses various script files. These files are not used for any AJAX purposes. However, I am using MS AJAX Libraries. My goal is to use the ScriptManager to manage release and debug versions of my JavaScript. Is this the right approach? Is there a better way to handle this task?
I am having a hardtime script debugging in VS2010 and IE8. I am using .net 4 framework.When i try to make a break point in my client script in VS2010, i get the respond "This is not a valid location for a breakpoint". Then I have tried to use IE8 Developebar, but when i try starting the script debugger it throws an alert, and tell's me that it couldent attatch to the process, because there may be another debugger attatched to the process.
Debug-Start Debugging/Debug-StartWithoutDebugging OR Project ASP.Net Configuration launches Dreamweaver. It started lastnight, I had both Deamweaver and VWD 2008 express open at the same time - (I was looking at JQuery in the Microsoft and Dreamweaver enviroments simultaniously). After the first tie this happened, I closed down Dreamweaver (CS3) and it opened when I tried to run my VWD project. I reinstalled VWD 2008 express, IIS and disabled Dreamweaver (renamed the exe). Dreamweaver still came up.
I just upgraded to VS 2010 and MVC 2.0 and I noticed the web.config has two additional files attached to it? Are these files used to specify debug and release specific settings, so you don't clutter up the main web.config?
Does it even make sense to place a connection string in the root web.config file if I have have a local and remote one in the debug and release web.configs respectively.