M
mwieder
We migrated our ASP.NET 1.1 application to 2.0. We want to deploy
using the fully compiled mode and have made the appropriate selection
in teh IDE to publish a non-updatable site. However, what gets
published are more files then it would appear we need. I understand
that empty copies of the aspx and ascx files must be published to avoid
naming conflicts. However, all the resource files (resx) are published
as well. Aren't they compiled into the dlls? Also, there are some
other files (.vsdisco for example) coming along as well. How do I stop
all these extra files from being published so we can distibute the app
with xcopy?
thanks!
using the fully compiled mode and have made the appropriate selection
in teh IDE to publish a non-updatable site. However, what gets
published are more files then it would appear we need. I understand
that empty copies of the aspx and ascx files must be published to avoid
naming conflicts. However, all the resource files (resx) are published
as well. Aren't they compiled into the dlls? Also, there are some
other files (.vsdisco for example) coming along as well. How do I stop
all these extra files from being published so we can distibute the app
with xcopy?
thanks!