Help and Support
 

powered byLive Search

You may receive an "unable to build project output 'content files from WebApplicationName'" error message when you build a deployment package in Visual Studio .NET

View products that this article applies to.
Article ID:835458
Last Review:May 17, 2007
Revision:1.7
On This Page

SYMPTOMS

When you try to build a deployment package in Visual Studio .NET, you may receive the following error message:
Unable to build project output group 'Content Files from WebApplicationName'
Note In this error message, WebApplicationName is a placeholder for the name of the Web application that is part of the project.

Back to the top

CAUSE

This behavior occurs if dependency files for the Web application are missing from project.

Back to the top

RESOLUTION

To resolve this behavior, you can replace any missing dependency files, or you can remove the file that requires them if the project does not require that file.

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

Steps to reproduce the behavior

1.Create a Web Setup project:
a. Start Visual Studio .NET.
b. On the File menu, point to New, and then click Project. The New Project dialog box appears.
c. Under Project Types, click Setup and Deployment Projects.
d. Under Templates, click Web Setup Project.
e. In the Name box, type WebSetup, and then click OK.
2.Add a Web Application project to the solution:
a. In Solution Explorer, click the solution.
b. On the File menu, point to Add Project, and then click New Project. The Add New Project dialog box appears.
c. Under Project Types, click Visual Basic Projects.
d. Under Templates, click ASP.NET Web Application.
e. Click OK. A Web Application project that is named WebApplication1 is added to the solution.
3.On the File menu, click Save All.
4.Remove a file that is part of the Web Application project:
a. In Microsoft Windows Explorer, locate the folder that contains the WebApplication1 project that you created in step 2. By default, this project is located in the C:\Inetpub\Wwwroot\WebApplication1 folder.
b. Delete the Global.asax file.
5.In Solution Explorer, click the WebApplication1 project.
6.On the View menu, click Refresh.

Notice that a yellow triangle icon appears next to the Global.asax file. This icon indicates that the Global.asax file is missing.
7.Add the project output to the solution:
a. In Solution Explorer, click the WebSetup project.
b. On the Project menu, point to Add, and then click Project Output. The Add Project Output Group dialog box appears.
c. In the Project box, click the WebApplication1 project.
d. In the box under the Project box, click Content Files.
e. In the Configuration box, click (Active).
f. Click OK. In Solution Explorer, Content Files from WebApplication1 (Active) appears under WebSetup.
8.Build the solution:
a. In Solution Explorer, click the solution.
b. On the Build menu, click Build Solution.

Back to the top

REFERENCES

For more information about project deployment and file dependency, visit the following Microsoft Developer Network (MSDN) Web sites:
http://msdn2.microsoft.com/en-us/library/k8kzx145(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/k8kzx145(vs.71).aspx)

http://msdn2.microsoft.com/en-us/library/wx3b589t(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/wx3b589t(vs.71).aspx)

http://msdn2.microsoft.com/en-us/library/2x78bwsf(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/2x78bwsf(vs.71).aspx)

Back to the top

APPLIES TO
•Microsoft Visual Studio .NET 2003 Enterprise Architect
•Microsoft Visual Studio .NET 2003 Enterprise Developer
•Microsoft Visual Studio .NET 2003 Academic Edition
•Microsoft Visual Studio .NET 2002 Professional Edition
•Microsoft Visual Studio .NET 2002 Enterprise Architect
•Microsoft Visual Studio .NET 2002 Enterprise Developer
•Microsoft Visual Studio .NET 2002 Academic Edition

Back to the top

Keywords: 
kbdeployment kbsetup kbprb KB835458

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.