Avoid Publishing ASP Applications In Debug Mode From Visual Studio?
Feb 17, 2010
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.
When I am actively developing it is extremely cumbersome to write some code, fire up the debugger to test said code, wait a minute for the debugger to start, look at the page in the browser, stop the debugger, edit the code, rinse, lather, repeat. I can get around that by using CTRL-F5 and CTRL-SHIFT-B during development but I lose all the benefits of the debugger. Is there a better way to use the debugger, or something else I can do to get quick rebuilds and use of the debugger? I/we do write unit tests, but you also need to test your app in the browser so please no "you shouldn't have this problem if your unit tests were written properly"
Error: When I hit F5: "A project with an output type of class library cannot be started directly. In order to debug this project, add an executable project to this solution which references the library project. Set the executable project as the startup project."Trying to debug the code in windows applications. It throws the above error.Googled, most of them say to download the exe file. But when I've right click the Project ->add reference-> browse -> bin-> debug -> .dll downloaded, still throws the same error. Unable to locate the executable file.
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.
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.
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?
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?
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 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.
Using VWD 2010 Express.We are using SVN for versioning control and so there are folder .svn in each of the project source code folder(eg. App_Data, Views, ...). These .svn folders also get published into the deployed location. Anyway can I set up a filter to exclude these .svn folders when do a Publish?
We are using Windows 7 with Visual Studio 2008. We wanted to know if there is a way to automatically configure new Projects to use the publish to IIS and create a virtual directory options, instead of defaulting to using the built-in web server, since we then need to manually go and publish/create the virtual directory.
In the "olden days" when creating a new project it automatically created the virtual directories in IIS, but not anymore .
I have created a Vista Side Bar Gadget in Visual Web Developer. When I run it from Web Developer, It installs to my sidebar, and works great. How do it package it so I can send it to my buddies to install on thier machines to test it for me?
I am struggling to publish a site built (and working locally) using VWD 2010 Express to a production server.I realise that this is because I don't understand enough about the relationship between the website and SQL server and I certainly don't know enough about the way SQL server works in general. Can anybody recommend some learning resources - books, tutorials, vids etc, that explain the background and in particular address the issue of how to publish to a production server.
This is just a small problem with some form of workaround im sure.I'm ready to publish my ASP.NET website, however, there is no 'Publish' option when I right click the project in solution explorer or even a Build Tab on the menu. I'm using Visual Web Developer 2010 and having done some research they all refer to this option in the Tab menu when I don't even have the Build tab myself.I did also see something to Download but I accidently closed the tab in a hurry - WebPI is it? Will this work?
The reason I want to 'Publish' ideally via MS VWD 2010 Express is that in previous versions (VS 08) when it 'Publishes' is combines the .cs/vb files with their respective pages rather than upload them as seperate files through FTP.I know some changes need to be done with the web.config file so If there is any info on that and other essential info I need to know please help me out (links references wud do! :P)
I'm trying to publish a site which uses an ajax uploader control which has an extra licence file that must be in the bin folder. Now if i publish my site this file is not published to the server and so i have to manually copy the file every thime to the server. My publishing setting is set to 'Only files needed to run this application'. If I change this to 'All files in the project folder' then it works but what is the point in that? I'm using Visual Studio 2010 Ultimate. (Note that i am a little new to publishing websites etc).
I have a couple files that are missing after a I publish a web application project in VS 2008. I know that the files need to be included in the solution and they are. I have tried excluding them and including them to hopefully reset whatever is missing these files in the first plac but that had no effect.
Ultimately, I need this to work on the command line with msbuild.exe, but I get the same results when I publish through VS.
Knowing that the files are already included in the project, what else do I need to do to get these to files to be copied over in the publish/build?
I'm relativly new to developing in .net so I probably publish to web to check my code more often than most developers but everytime I do it kills my login session... so I have to log in, navigate to the page I'm working on and then test it... is there a setting to stop killing the active sessions.... it would make development MUCH quicker for me.
there is probably a really simple answer to this, but I have the flu and can't think straight. I am taking advantage of being out sick by downloading VS2010RC and playing around with it. I created a simple WCF service (my first in this foundation, but not my first service). Its a redo of an existing asmx service I created a while ago. I commented out all the processes, and am simply trying to publish the service to my local IIS7 to see the discovery working. I have setup a new site to host the service ( I tried using Default as well, with the same results). I right click the project in VS and select publish. It is prompting me for a login even though the site is setup for anonymous access. If I try to use WebDeploy, it can't find my site, and if I use FileSystem, it give me a simple "Publish failed" with no details. Can someone point me to a tutorial or something that describes the publish process in VS2010 or give me some leads as to what setup needs to happen either in VS or ISS to let me publish?
