Can Specify If Aspnet_compiler.exe Creates A Debug Or Release Build
Apr 16, 2010
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?
this is used when loading certain assets (swf files) by being appended as a querystring parameter and ensures that when debugging a cached version isn't received but is manageable once released.
However, after what I believed should be compiling a relase build, the version is still being set as a Guid indicating I'm not achieving a release build yet. I've checked the web.config and the value of debug is changed to false so I'm assuming I'm missing some setting in the aspnet_compiler.exe arguments, but I cant find anything which indicates such in the documentation.
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'm opening some project off of the codeplex website. When I do, it lists two types of files: *.cs and *.debug.cs me what the *.designer.cs" are?Also, when I build the application, it creates a "dll" in the "debug" directory. How do I make a dll get built in the "release" directory?
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'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>............
We have an ASP.Net MVC solution built in VS2008 and TFS2008. We use TFS Build and use Continuous Integration.We have a deployment pipeline that enables us to progress a build, eventually, to our live site...
Internal Dev (immediate deployment following a build) External Dev (used by internal testers to make sure it works on the production server) External Test (used by our client to test themselves) Live (self explanatory).
I have 2 questions relating to thisWhich ones of these should be built in Debug and which in Release?How should I write my TFSBuild.proj files to cope with this strategy?
I'm working on resource files in windows application. After i'm adding the resource file in the project if i built the project it creates a separate folder for each language with language code(Spanish->es-ES, French->fr-FR..) and also it has one dll file for corresponding langage inside the folder. Why it is creating like this? Can't we avoid this?
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?
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 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.
I am working on an ASP.NET web app using Visual Studio 2008 and a third-party library.
Things are fine in my development environment. Things are also good if the web app is deployed in Debug configuration. However, when it is deployed in Release mode, SerializationExceptions appear intermittently, breaking other functionality.
In the Windows event log, the following error can be seen:
"An unhandled exception occurred and the process was terminated.
Message: Unable to find assembly 'MyThirdPartyLibrary, Version=1.234.5.67, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89'.
StackTrace: at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name) at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
[code]....
Using FUSLOGVW.exe (i.e., Assembly Binding Log Viewer), I can see the problem is that IIS attempts to find MyThirdPartyLibrary in directory C:windowssystem32inetsrv. It seemingly refuses to look in the bin folder of the web app, where the DLL is actually located.
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 have a VS2010 Web Application that uses the AjaxControlToolkit. I am able to build the Debug configuration. When I build the release configuration I get the following error message: Error 89 Could not load file or assembly 'file:///S:My CodeLibrariesACTMay 2010AjaxControlToolkit.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) S:My CodeEZFishingEZFishingEZFishingSGEN EZFishing
The location of the file is correct, and I just downloaded and unzipped there the Ajax CT. I have always built this app correctly before upgrading to VS2010 and ACT May 2010.
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 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.
I have a Nant build script which referrences 30 other build scripts.
Each build script referrences a visual studio solution using MSBuild.
Each solution has 3 to 5 projects in.
Some projects are Class Librarys and some are Web Apllications.
The projects reference other projects both in their solution and out of their solution, so the projects do not use project references, they reference the the Release DLLs in the Bin folders of the other projects.
To use the software, I need to publish all the solutions together.
Which means I cannot do a deployment which is in debug mode.
Which means I cannot the step into and debug the code.
I would like to run the build script to get a deployment of the software which I can debug.
I 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.
