I cannot for the life of me figure out how to force Visual Web Developer 2010 Express to use my Web.Release.config when I'm publishing my web application. I'm using FTP to publish my webapp to a remote server. Each time I publish, the build uses my Web.Debug.config.
I know I'm overlooking something simple and would really appreciate a clue.
Respectfully,
Ray
In Visual Web Developer Express (2010), selecting the build is simply a matter of clicking on the drop down to the right of the green "Start Debugging" button. Debug will use your debug web.config and release will use your release web.config.
When publishing, click the drop down and select Release. Then publish as normal.
Go to Build -> Configuration Manager
Under Active Solution Configuration select Release
Hopefully this is what you're after.
Related
All of a sudden after I installed Microsoft Edge on Windows 10 gd, Visual Studio is using IIS Express when debugging a web application and it is messing up everything.
How do I get back to normal, so that stupid IISExpress is not used anymore?
Go to the project settings and on the web tab is a drop down that allows you to choose which engine to use.
I went to Project > Properties > Startup Project and then set my start up projects to start the services I need and my project. This reverted my button back to just "Start".
As per the question, how do I configure an ASP.NET MVC project when running from Visual Studio 2013 under IIS Express (x64) to be seen as a "Managed" type in the debugger "Attach to Process" screen?
My solution always used to allow me to debug the web projects when running, and now I can no longer do so as the projects all seem to run as x64 non-managed.
I'm guessing it's something I have changed under the csproj or MSBuild targets / properties.
Regards,
Rob.
In the end, it appeared this was a combination of bloated csproj files, coupled with instability in Visual Studio 2013.
If you are using Visual Studio 2013, I highly recommend installing Update 2. It appears to make tasks a lot more reliable.
I never figured out what governs the Managed setting, however I have found the following option:
Click Attach to Process
Underneath Transport/Qualifier/Transport Information, there is a box marked Attach To:
By default, it is set to perform Automatic selection.
Click the Select button.
Toggle from Automatic to "Debug these code types"
Tick one or the other (not both) of the entries for "Managed ([.NET version])"
Click OK
I have had some success in getting the Debugger to attach properly to the IIS Express processes that are running Managed debuggable code that it "automatically" doesn't let me (for seemingly random reasons).
I have a website (target framework 2.0) , I install VS 2010 Ultimate on Windows 7 Professional, The problem is When I open the website, I'm trying to change the Build configuration from Debug->Release, There no "Release" item option in Solution Configuration drop-down list, which is on the Standard toolbar. even when i right click of solution and select properties, then Configuration Properties, I can see Active(Debug) only.
I need to publish a released copy. (in other word, no html code in aspx files)
Release configuration is not available for Web Sites. You have two options:
Right click the project and "Publish Site", or
Get the web deployment add-on at http://www.microsoft.com/en-us/download/details.aspx?id=24509. This will allow you to package your site and get it ready for deployment.
I prefer the second option, it has many benefits, provides more options, and if you do it right, it can help with the deployment process.
I'm getting this error, vb / .net4, although the website is working fine, at the bottom of the page:
YAF Compiled in DEBUG MODE.
Recompile in RELEASE MODE to remove this information:
I opened up Visual Studio 2010 right-clicked my solution, looked under the "build" tab, but I cannot find anything about release mode. Could somebody please tell me where I can find this and build my site in release mode? Thanks!
I'm experiencing the same issue with VS 2010 and VS 2011 beta. I suspect a third party tool or plugin may be the culprit and am in the process of looking into this.
For now, just change the compilation switch in the Web.Config to false:
<system.web>
<compilation debug="false">
</system.web>
UPDATE 1:
I have fixed my VS 2010 issue by uninstalling Telerik JustTrace. I was still experiencing the same issue with VS 2011 beta (on a separate VM to VS 2010) though. So, I tried using a Web Application Project instead of a Website Project and the problem went away.
UPDATE 2:
This is normal for website projects as each page is compiled dynamically:
Why can't you build a website in release mode?
Make sure you have the "Standard" toolbar visible and you should see something like this:
Change the "Debug" to "Release" and rebuild your solution.
I have it right in my toolbar.
But you can also change it by using the menu Build => Configuration Manager. Select Release from the Configuration drop down next to your project.
Is there a "debug" and "release" build in VS 2005? If so, how do I switch between the two?
Saif:
Are you working on an ASP.NET web site project?
If so, Visual Studio delegates the build step to the ASP.NET runtime, and the ASP.NET runtime picks up debug versus release in the web.config .
I have a post on the topic that will help: Debug and Release Builds in ASP.NET 2.0
Note that a couple things have changed since that time. Namely, MSFT released two add-ins for VS 2005 - one to add real web application projects that have debug and release settings (for the code-behind and loose c# files), and they also released web deployment projects, which can use the asp.net command line compiler. Web App projects became a part of VS2005 in SP1, too.
Use the Configuration Manager. Right-click on your solution in the Solution Explorer, select "Configuration Manager...", and change the active solution configuration.
You can change your project's behavior when in debug or release mode. Bring up your project properties pane, select the appropriate configuration from the dropdowns at top, and change the settings as appropriate. Notice that some changes are made by default for you. For instance, release builds by default are set to optimize code, and debug builds are not.
In the ASP.NET web.config file there is a debug="true" attribute. The first time you run the web application Visual Studio will ask you if you want to turn on debugging, selecting yes will cause Visual Studio to edit the config file for you.
Just remember to make sure you change that back to false for your release builds. For more info click here.
The quick way is to right click on the toolbars and turn on the standard toobar. Then you can quickly change between build targets by choosing the one you want from the solutions configuration drop down.
If you want to change what those configurations do, then follow what Michael Petrotta said in his answer.