0

When deploying from a development to an acceptance IIS environment via FileSystem, the web.config file does not get output to root and as a result, accessing the website produces an Runtime error.

(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.)

When I check the deployment directory, the web.config isn't there, but instead, its located at the bin/ directory.

I tried changing the file type to Content/ None / Resource and nothing happens.

Also tried to follow this link and disable transformation by adding a TransformWebConfigEnabled tag in my configuration, to no avail.

Publishing straight from Visual Studio works, however, due to restrictions in the company, I can only publish directly to development environments.

Cece Dong - MSFT
  • 29,631
  • 1
  • 24
  • 39
bruno_cw
  • 994
  • 1
  • 8
  • 22
  • 1
    Check this case which may be helpful: http://stackoverflow.com/questions/16246562/using-msbuild-to-execute-a-file-system-publish-profile – Cece Dong - MSFT Feb 24 '16 at 02:24
  • How do you deploy via FileSystem? Why not use WebDeploy? – chief7 Feb 24 '16 at 02:25
  • @Cece-MSFT it didnt work but i guess it's a step in the right direction. Maybe I can add a task which will copy the web.config to the root folder, or remove the task which is deleting the web.config – bruno_cw Feb 24 '16 at 13:25
  • @chief7 It's made through a robocopy script. But it's automated via TFS-Build. I could copy the files manually, however I don't have write access to the prod server. – bruno_cw Feb 24 '16 at 13:26
  • Why not use WebDeploy? It seems like this would simplify the deployment and be more stable. – chief7 Feb 24 '16 at 14:45

0 Answers0