Visual Studio :: References In Debug Versus Release Mode
Nov 1, 2010
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 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 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 got a problem regarding CSS in my pages. I managed to apply styles to my page using css and everything looks fine in the Design view. I ran it on IE8 and everything is working fine. Now after I returned to Visual Studio, added some rules to my CSS, and noticing that everything is working fine in the Design view, I ran it again in IE8 and nothing has changed. The rules I added was ignored and it looks the same. I ran it on Firefox and Google Chrome and it's working fine.
But if I ran my project in IE8 through IIS7.5, everything is working fine so it means, the problem is within visual studio 2010.
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 using vs2008 sp1. I am building web site with aspx. I am also using an ajax control. My Site was working normally. I could run it from f5 and it would stop at a debug point. I added an additional aspx page. Then I got a strange error. When I pressed f5 a message box appeared saying that I had not made this version with the debug option. Then from reading an internect post I disabled only my code. That got rid of the message box error but now the debugger does not stop at any break point? Of course this happen when I need to go live with this project in a day.
We all know that we should only be publishing our ASP.NET Web Applications with release build type, so why do I not get a warning when I trigger the "Publish" command in Visual Studio 2008, for a project configured to build in debug mode? Sure, there might be cases where I need to publish a debug build to a development or test environment, but answering yes in a confirmation dialog would be acceptable in these cases. Is there an option that I have overlooked, forcing Visual Studio to warn me every time I try to publish a debug build? Yes, we could just ban using the "Publish" command and use a more solid build management tool, but this involves a change of process and right not be an option in this particular case.
There are plenty other similar static methods defined within the class.
When does it fail: ONLY when the solution is compiled in 'DEBUG' mode. Everything works fine in 'RELEASE' mode.
What have I already tried:
1. Including a static constructor inside 'Utility' class - FAILED
2. Marking 'Utility' class with 'static' keyword: FAILED
3. Changing platform target from 'Any CPU' to 'x64': FAILED
As highlighted above, the issue is really not with VerifyPassword() method per se. Rather it is with the instantiation of 'Utility' type. That's why an exception is thrown from the constructor. Since 'VerifyPassword' is it is the first static method called, it appears in the stack. Just for the sake of proving that, I removed the call to VerifyPassword and returned 'true' instead. That way I was able to login to the application (no password verification), but failed at a later stage where I had called the Utility class on another method, namely Utility.ValidateSKUAdjustment(txtCurentMonthM1.Text).
I am using Visual Studio 2010 and ASP.NET 4.0 to build a WebForms project that uses the new routing features in System.Web.Routing. When I build my solution and run it from within VS.NET's debugging environment only routes with RouteUrl's that include a ".aspx" extension are being properly routed to the PhysicalFile. It appears requests made to other URLs are not being "detected" by the routing engine for processing. In the case below, "Scenario1" shows a 404 and "Scenario2" works properly.
I'm running ASP.NET on Visual Studio 2005, and I am not able to step through my break points when I run my application in "Debug" mode. I set the break points, run the application, and Visual Studio simply ignores them.I have gone through all of the configuration settings and project properties to see if their is something obvious that needs to be turned "on" - but I don't see anything.What would be the most logical settings or references to look at?
I am using Reporting Services to render a report directly to PDF. It requires that I use two web references: ReportExecution2005.asmx and ReportService2005.asmx. The performance on web references seems really poor. Since my web server (IIS7) and my SQL Server (2008) are on the same box, is there a way I can reference them directly? If not is there any way I can explicitly cache them or something. First load is really really slow, second load is perfectly acceptable.
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 noticed when creating a reference that two of the columns in the dialog box under the .Net tab have Version and Runtime.
I'm assuming that Version is the version of the .Net Framework that a given namespace was introduced with.
I'm not sure I understand what the runtime is though. I originally thought it was for the version of ASP.net but now I question that. If look at two namespaces that were introduced with two different Versions they can have the same run time. This contradicts my original conclusion.
how these relate to each other and correct any misunderstandings I my have with this?
I have a Visual Studio solution containing two web applications. I would like the first to depend on the second (pages in the first may contain links to, or possibly post to pages in the second). Furthermore, I would like to be able to launch the first project on a development server (standard debugging procedure for web apps in VS) and have the references to the second project be fully functional.Does anyone know the best way to achieve this?
Is there anyway to localise an external assembly reference? Here's my situation:I am working on Project A and it contains assembly references from Project B. Now when I release this Project to my client I don't want to have to include the whole of Project B with it. Is there anyway to force it to copy the dll's from Project B onto Project A and use those references? I can do this manually by copying all dll's to local project and re-referencing but just wanted to know if there is an easier way.
I use SmtpClient to send email. I want to ensure that the SMTP connection gets closed after each message is sent. I found an explanation of how to do this in the SmtpClient documentation on MSDN:
[URL]
One thing it says is: Call Dispose when you are finished using the SmtpClient. The Dispose method leaves the SmtpClient in an unusable state. After calling Dispose, you must release all references to the SmtpClient so the garbage collector can reclaim the memory that the SmtpClient was occupying.
I have a question about the last part. What exactly does "release all references" mean. How do I do that?
I am currently making the switch over from Visual Studio 2005 to 2010. In 2005, you were able to right click on the 'web references' folder and update all web reference within that folder. However, in 2010 I cannot see an option to do this - I have to update each one individually.Anyone know of a way of updating web references in Visual Studio 2010 en masse?
