Using IntermediateOutputPath Not copying to Target Path

Question

I have a Website Application that I use the Publish option to write the output to a local folder which I then zip up and move to our deployment server. We upgraded out packages and started to get an error that it can't find the path which ended up being the path was too long. I resolved this issue by using the IntermediateOutputPath in the website.publishproj file. The site now compiles but it leaves all the files in the IntermediateOutputPath folder. The output pane says it publish successfully to the Target location in the publish profile but the target location is empty. I'm sure I'm missing another setting somewhere but I cannot figure out what I'm missing. Does anyone have any idea what I may be missing here?

Jim · Accepted Answer · 2025-07-24 13:27:11Z

0

For anyone else stumbling upon this you can add the below parameter to your publish profile and it will fix the issue:

<AspnetCompileMergeIntermediateOutputPath><short path></AspnetCompileMergeIntermediateOutputPath>

ex: 
<AspnetCompileMergeIntermediateOutputPath>c:\compile\</AspnetCompileMergeIntermediateOutputPath>

answered Jul 24 at 13:27

Jim

112 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Using IntermediateOutputPath Not copying to Target Path

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related