I am creating a module on Dotnetnuke project template, and i want to make the release of that module. But when I select "release" from dropdownlist and after that click on debug button. I got an error below on iis7 and windows7.
Unable to start debugging on the web server. The web server is not configured correctly. See
help for common configuration errors. Running the web page outside of the debugger may provide further information.
I don't understand why it comes.
If you are trying to DEBUG, you shouldn't choose RELEASE from the dropdown list, that will build the module in RELEASE mode, not DEBUG mode.
You should also check to see if you have enabled Debugging in the web.config of your DNN Development site.
Update:
If you want to package the module, after choosing RELEASE from the dropdown list, choose BUILD not the DEBUG option in visual studio.
One other consideration is to ensure that your web.config compilation node is set to debug="true". This is of particular interest if you configSource this setting into a separate file.
Related
Here is my situation...
I have to maintain a website with multiple applications. We no longer have any of the solution files and the code is deployment code (so it uses DLL's instead of the original classes).
I basically grab the code from the website and stick it in a Visual Studio projects folder (This is generally C# code with Javascript that was originally developed on VS). I then open Visual Studios's 2010 Professional (VS) and open website, using the path in the project folder. I then add references to all the DLL files and if all the includes, images , and css files paths are referenced correctly, I can hit F5 and get the webpage to appear with some functionality. This creates a Project file in the Projects folder which I can then open instead of opening a website.
The problem is that I am unable to debug. If I set a breakpoint, it goes from solid red to outline red upon start of debugging. The standard message is "The breakpoint will not be currently hit. No symbols have been loaded for this document".
I have cleared out the symbols and reloaded.
I have debug = true in all my Web.config files.
I have gone into project properties and set the startup project action to "Start".
Any ideas why I can't debug ? My other projects that I develop from scratch work fine, but it is these projects that I am trying to get working from website files that won't debug.
My goal is to get every one of the Website apps under VS control were I can fix bugs and make improvements. Not very easy when the original source code is no longer available.
Please Help !
Thank You,
Eric
I fought this issue for a half of a day. I'm currently maintaining a website application. What worked for me is going into the project's Property Pages >> Start Options and changing the server to "Use Custom Server". I believe this setting will use IIS and not IIS Express. I started the project and was immediately able to debug.
In VS2013 why does the Configuration Manager only show debug as an option for websites?
Attaching image to show what I'm talking about.
Website projects are not based on MSBuild (there's no .csproj or .vbproj). Configuration is an MSBuild concept, so it doesn't apply to these projects; but since they show up, they appear as Debug by default.
I have an Azure Cloud Service Project that has a web role with multiple websites associated with it.
When I click the "run" button, it fails to load the debug symbols for all the websites in the web role. In order to debug the other websites, I have to explicitly build the web project in question before I can run the debugger.
How can I configure the Azure Cloud Service Project to compile all the associated webs within a single web role?
As of this posting, Visual Studio 2012 support for multiple websites within a single web role is fairly poor (Exibit A, Exibit B).
When you click the "Run" button in a solution, it doesn't mean that all projects will be compiled. Only those directly related with the project that is being run at the moment will be compiled (and debug symbols updated).
Consider the following work-around:
Identify the main web role web project in the solution (it should the one that
matches the name of the web role in the Azure Cloud Service Project).
Right click on the web project
Go to "Add Reference"
Go to "Solution"->"Projects"
Check the checkbox next to each of the web role's associated websites.
Click OK
By adding a reference to the other web projects, it causes the compiler to compile the other webs when the Azure Cloud Service Project is run with the debugger.
This will allow you once again hit the "run" button with great abandon.
I've posted some details on using multiple web sites within a web role on my blog at http://michaelcollier.wordpress.com/2013/01/14/multiple-sites-in-a-web-role/.
As for the debugger, are you using host headers for the different sites? If so, try switching to use different ports instead. I've had better luck going that route for debugging purposes. Then switch back to host headers when ready to deploy.
I have a solution consisting of a number of class library project, and a windows service project. When I open the project settings for the windows service project and (accidentally) click on the "Services" tab, Visual Studio insists on automatically ticking the "Enable client application services" checkbox.
The effect of this is that it will add a reference to System.Web.Extensions, and also insert some parts in the app.config. Disabling the checkbox again will not remove the reference. It will however remove the generated configuration, though it will also remove some unrelated configuration that were there before.
Why does it insist on ticking this checkbox, and can I make it not do it? The HELP documentation for the "Settings" tab does not mention any "auto-select" behaviour.
This is Visual Studio 2010, targeting .Net 3.5.
At least one other person have the same issue, unfortunately without any resolution provided:
http://go4answers.webhost4life.com/Example/visual-studio-2010-keeps-enabling-7689.aspx
That in turn links to a Microsoft Connect issue, but for some reason they don't allow access to older reports it seems: https://connect.microsoft.com/VisualStudio/feedback/details/570166
When there is AppSettings item in app.config, the setting “Enable client application services” will be always automatically checked on when to open the project property page.
Reproduce steps:
Using VSTS 2012
Create an empty console application
Add AppSettings section to app.config
Open the project property page and click the "Services" tab
You will see “Enable client application services” is checked on and app.config is updated.
One workaround from our team member:
just to rename the app.config to the its finally deployed file name, such as ConsoleApplication.exe.config and change its file property - "Copy to OutputDirectory" as "Copy if newer".
It works for our project.
Is it possible to change some setting so that Visual Studio always use the "release" configuration when publishing?
I use debug mode when i develop to clear some caches and stuff like that and i also have different web.configs for release and debug. Sometimes when i publish i forget to change the configuration to release and i end up with a broken website ;)
I understand i can do this with MS Build or something but publish working fine except for this. Any tips?
In Solution Explorer, select the project.
On the View menu, click Property Pages.
Click the Build or Debug tab, in a Visual C# or a Visual F# project, the Compile or Debug tab, in a Visual Basic project, or Configuration Properties, in a Visual C++ project.
In the Configuration drop-down list, click Debug or Release."
Steps provided by:
http://msdn.microsoft.com/en-us/library/wx0123s5.aspx
As of at least VS 2017, the web publish settings now include a setting for which configuration to publish, which defaults to Release, so you can publish the release build even when VS is still in Debug configuration.
I just wish that they had also done this for regular Click-Once applications as well...