.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

deployment problum

Posted By:      Posted Date: October 05, 2010    Points: 0   Category :ASP.Net

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect&

View Complete Post

More Related Resource Links

Debugging ASHX after deployment



I'm finished with a part of my ASHX handler and need to test it against the software that'll be calling it using HTTP POST. The software required an https url so I created an internally hosted site in IIS and published the project there. 

Question now is how do I do any debugging on the script to see what data is coming out of it before the data goes back into the software that's calling it? Do I set something on the project itself to be able to step into the published DLL? 

Multiple MSIs from one deployment project


We have several .NET based products for which we need to generate multiple MSI files to allow for multiple instances of the same app to be installed on the same machine.  For instance, we might have a single server running version of the app that are pointed at either test or QA databases, or may use the same server box to deploy the product for multuple clients.  (So, for instance, our web server might have separate installs of the same code in different locations for product names "Client A test", "Client A QA", "Client B Test", etc., where the only real differences are in the web.cionfig files that are not overwritten by the install of a new version.)

Right now we simply have a deployment project for each named variation of the app.  This works, but is likely to become a maintenance mess as the number of instances grows.  We'd like to be able to maintain only a single deployment project and script the creation of multiple MSIs, one for each product variation, after the build of a baseline MSI.

As I understand it, this should be acheivable by building the MSI, then for each possible instance, making a copy of the MSI and giving it a unique ProductCode and PackageCode; this way Windows should recognize each instance as a unique application.  I've done this (as well as changing the produc

web deployment project (WS_deploy) on VS2008


I am building a asp.net webservice in VS2008 and the web service compiles and debug fine. The project should be using : Net 3,5

 I have

  1. VS2005 and VS208 installed
  2. .Net 1.1 - 3.5
  3. WebDeploymentSetup for VS2008 (and most likely a version for VS2005 as well)

But when I add a web deployment project the fun stops. The .WS_deploy project will not compile and I cannot find any precompiled output.

--------------debug output-------------------

------ Build started: Project: **************.DAL, Configuration: Debug Any CPU ------
Build started 13-08-2010 08:17:14.
Target EntityDeploy:
    Processing 0 EDMX files.
    Finished processing 0 EDMX files.
Target CoreResGen:
    No resources are out of date with respect to their source files. Skipping resource generation.
Target CopyFilesToOutputDirectory:
    **************.DAL -> C:\Development\VS2008\**************\**************.DAL\bin\Debug\**************.DAL.dll

Build succeeded.

Time Elapsed 00:00:00.14
------ Build started: Project: **************.BLL, Configuration: Debug Any CPU ------
Build started 13-08-2010 08:17:14.
Target EntityDeploy:
    Processing 0 EDMX files.
    Finished processing 0 EDMX files.
Target ResolveProjectReferences:
Target CoreResGen:
    No resources are out of

vs2010 web deployment project restarts w3svc even when restartwwwservice = false


We've updated some of our projects from VS2008 to VS2010.  When these projects are deployed the w3svc is restarted on the target machine, even when restartwwwservice = false in the vdproj file.


This was a problem in 2008 until SP1 (http://forums.asp.net/p/1300097/2534736.aspx).  Does this same problem exist in VS2010?


This is a major problem for us -  we need to be able to deploy projects without restarting IIS.


I've tried creating a new web deployment package and setting the restartWWWService field to false, but this still does a restart when it's installed.


Has anyone come across this problem in VS2010?

Web deployment project - web.config section replacement does not add remove tag


I have a web application that is actually installed as a component of a third party site.  In some configurations, I need to remove certain connection strings and re-add them.  I'm replacing this web.config section with a xml file that includes the following:

      <remove name="MyOverridenConnection"/>
      <add connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyDb;Data Source=MyServer" name="MyOverridenConnection"

For some reason the remove tag is left out during the substitution and I end up with the following in the installed config:

      <add connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyDb;Data Source=MyServer" name="MyOverridenConnection"

Is there any way to issue removes in replaced sec

Web Deployment - Setup failing - aspnetca.exe


I have created websetup in windows 7 environment, asp.net 3.5, IIS 7.

Client System is windows 7 and IIS 7

Our client configuration is Windows 7, IIS7 dotNet Framework 3.5.
Following error raising below...
Faulting application name: aspnetca.exe, version: 7.5.7600.16385, time stamp: 0x4a5bcd3c
Faulting module name: aspnetca.exe, version: 7.5.7600.16385, time stamp: 0x4a5bcd3c
Exception code: 0xc0000005
Fault offset: 0x0001d912
Faulting process id: 0xe80
Faulting application start time: 0x01cb3604624975cd
Faulting application path: C:\Windows\system32\inetsrv\aspnetca.exe
Faulting module path: C:\Windows\system32\inetsrv\aspnetca.exe
Report Id: a05d368d-a1f7-11df-8336-4487fc612414
PFA Here I"m attaching custom action script. 

Web Deployment with IIS settings of remote server


Im trying to deploy a web application project (VS 2010) via team build (TFS 2010), i got to use IIS settings of development server for deployment. So from the project properties I configured the web projects to use Custom web server, (enabled radio button), once i do this the Option in the tab Package/Publish Web "Include all IIS Settings as configured in IIS manager" gets disabled and as a result the deployed web project does not have this IIS settings.

What am I missing here, Im not using the option "Use local IIS Web Server" because the build happens in a build server and would try to take local IIS settings for packaging which is not present.

If this is not possible, suggest me any workaround. Any help on this is greatly appreciated.

Could not load file or assembly - Web Deployment Project



I have the following projects in a solution :

- A Web Application

- A Class Library

- A Web Deployment project

The Web Application compiles and run fine when I don't go through the Web Deployment Project. However when I try to use that, I get the following error:

Error 1 An error occurred creating the configuration section handler for hibernate-configuration: Could not load file or assembly 'NHibernate' or one of its dependencies. The system cannot find the file specified. (F:\Folke\Folke.csproj_deploy\Release\web.config line 4) 1 1 Folke.csproj_deploy

"An error occurred creating the configuration section handler for hibernate-configuration: Could not load file or assembly 'NHibernate' or one of its dependencies. The system cannot find the file specified. (F:\Folke\Folke.csproj_deploy\Release\web.config line 4)"

This is the beginning of my Web.config:


SMTP not working if I use web deployment package to deploy my app.


Hi all

I use msdeploy to install my web app. deployment package. everything about web app works, but find out email was not working.

I checked telnet smtp is running.

I debug the project, and it was sending out email too.

So my solution was upload the whole project (not complied) to wwwroot, and email works too. Thats why I assume the deployment cause the problem.

at last, I also tried to copy the web deployment web.config to replace the project's web.config, and the email also work, so it wasn't the web.config problem.

Could anyone tell me whats going on?

My environment:

window 2003

iis 6

.net framework 4.0

Web Deployment Projects (WDP) arabic character



I built web project using asp.net & c# in VS2005 and i use arabic label in my project and every think working good when i run my application. but when i use WDP to make msi file All arabic letter come like ?????. 


Visual Studio Web Deployment Project for VS 2008


What is the latest version of Visual Studio web deployment project which I can use with  VS 2008 ?

Can I use VS 2010 Web Deployment Project with  VS 2008 ?


MOSS 2007: Automate Web App Deployment with the SharePoint API


Learn how to automate custom SharePoint application deployments, use the SharePoint API, and avoid the hassle of custom site definitions.

E. Wilansky, P. Olszewski, and R. Sneddon

MSDN Magazine May 2008

Office Space: Solution Deployment with SharePoint 2007


WSS 3.0 introduces a new deployment mechanism that lets you move your development efforts into a staging or production environment.

Ted Pattison

MSDN Magazine August 2007

Extreme ASP.NET: Web Deployment Projects


ASP.NET 2.0 development is the easiest ASP development yet. Fritz Onion reveals why.

Fritz Onion

MSDN Magazine April 2007

Escape DLL Hell: Simplify App Deployment with ClickOnce and Registration-Free COM


DLL Hell that results from versioning conflicts is generally not a problem in .NET because components do not require registration, and are either totally isolated to an application or are managed in a well-defined side-by-side way with the help of the Global Assembly Cache. But if you're still using COM, wouldn't it be great if you could deploy your existing COM components using a model similar to the .NET Framework? In Windows XP, you can, and this article explains how.

Dave Templin

MSDN Magazine April 2005

Data Deployment: Streamline Your Database Setup Process with a Custom Installer


Database setup can be a tough and time-consuming process and sometimes fall victim to human error. Microsoft Installer or InstallShield can help, as can your own custom installer. In this article, the author tackles one approach to writing database installers and demonstrates the process with a working code sample.

Alek Davis

MSDN Magazine September 2004

.NET Zero Deployment: Security and Versioning Models in the Windows Forms Engine Help You Create and


Windows Forms applications solve many of the problems inherent in building Web applications the old fashioned way?with HTML. To demonstrate the use of Windows Forms over the Web, the author takes his existing app, Wahoo!, and ports it to Windows Forms. In doing so, he discusses versioning, linked files, security, storage isolation, the deployment model, and everything else you need to get started building your own Windows Forms apps for the Web.

Chris Sells

MSDN Magazine July 2002

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend