Link to home
Start Free TrialLog in
Avatar of steverguy
steverguy

asked on

Publishing with ASP.NET and Visual Stuido 2008

I'm publishing my first ASP.NET website to a shared hosting environment. (GoDaddy) I have been testing it using my local machine, and everything works fine.

When i published the site using the "Publish Web Site" tool, the site returns an error for any pages that are in the root directory.  Files that are located in folders work fine.  The error isn't specific, but when i removed the check for "Allow this precompiled site to be updateable" the site works fine.

This is good, but if anyone wants to make changes to a file on the server, they can not.  All the files show up with a text message: "This is a marker file generated by the precompilation tool, and should not be deleted"

Is there some web.config setting i need to change to enable the site to be published to a root directory?  I can't seem to find anything on this.

Thanks for your help!
ASKER CERTIFIED SOLUTION
Avatar of Juan_Barrera
Juan_Barrera
Flag of New Zealand image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of steverguy
steverguy

ASKER

This is the error I get:
BC30456: 'CreateResourceBasedLiteralControl' is not a member of 'ASP.masterpage_master'.

you can see it here: http://edtweb26dev188.edthosting.com/

What I don't understand is that the issue doesn't exist when i publish the website with "Allow this precompiled site to be updateable" unchecked.

I agree with you, it actually makes a lot of sense not to have people make changes to the files on the production server.  But since my partner works from a different location, sometimes he has to change things i've posted.

Thank you for your help with this!
Check the "inherits" declarations in your pages and make sure that there are no duplicates.
Sorry this is so long in being accepted.  While i can't get past the error, we can live with it, and like you said, it's probably better this way.  Thanks!
Thanks Juan for pointing me in the right direction.