I am using a Web Application Project to develop some web user controls (c#).

In the WAP the user control directive contains the codefile and inherits attributes.

When I publish the WAP to the target website. The dll from bin is copied correctly to the bin of the website, the user controls (.ascx files) are copied correctly.

When I perform a build on the website, I get errors as the ascx files still contain the codefile attribute in the directive. To resolve this I simply remove the codefile attribute and the ascx still works as the code is picked up through the inherits (which is now in the dll).

My question is - can the publish automatically remove the codefile attribute for me. or.. am I using WAP / Build / Publish incorrectly?

Many Thanks, Adam

Have you added those directive manually at the time of designing user controls ?

No, when I add a new user control it is automatically created with codebehind and inherits attributes.

I have read that codebehind should read as codefile so I have manually changed this.

What happen when if you don't change it manually?

If I leave it as CodeBehind, the attribute is still present in the published user control on the target website, howerver in this instance the user control builds on the target site successfully, and only contains a warning instead of an error.

Is this correct, or should the attribute have been removed? 

Can you post that warning here. or google / bing about it  and see how harmful it is to your application.

 Hi,

After we use Publish feature to publish ASP.NET web application, we can remove the "CodeFile" from Page directive, instead, ASP.NET uses Inherits to load assembly.

In ASP.NET Website project, the compiler will remove CodeFile attribute and change the Inherits attribute to include the assembly name.

You also can try to disable “allow this precompiled site to be updatable” while precompiling website. By doing this, the .aspx page just is the placeholder.

Thanks.