Can't build project with reportviewer

Question

0.00/5 (No votes)

See more:

LOL

I can no longer build my project due to microsofts reportviewer names being too long.

The error I get is:

The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

while copying to:
C:\Users\myusernamexx\AppData\Local\Temp\WebSitePublish\WebPortalNet4-872599845\obj\Debug\AspnetCompileMerge\Source\packages\Corrected.Microsoft.ReportingServices.ReportViewerControl.Winforms.150.1358.0\Corrected.Microsoft.ReportingServices.ReportViewerControl.Winforms.150.1358.0.nupkg

D'oh… now what?

Any ideas how I can around this? Can I override the temp publishing target to make the folder-name smaller?

Thanks

What I have tried:

Building it over and over until it goes away; but it never does :(

Posted 31-Jul-20 0:04am

dnibbo

Updated 2-Aug-20 1:13am

v2

Add a Solution

Comments

Richard MacCutchan 31-Jul-20 8:28am

The message is quite clear, the path is too long. So move the files to some location with shorter directory names.

dnibbo 2-Aug-20 6:36am

It is Visual Studio that generated the directory name not me :(

Richard MacCutchan 2-Aug-20 7:51am

Then perhaps you should open a question with Microsoft, it's their software.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sandeep Mewara · Answer 1 · 2020-07-31T00:37:00

Solution 1

Try this, as mentioned here: Website publish failing due to file path being too long | The ASP.NET Forums[^]
Add the following line in default PropertyGroup of web project file.

HTML

<IntermediateOutputPath>..\Temp</IntermediateOutputPath>

You can likely make the above path C:\temp to get it as close to root of the drive as possible.

Posted 31-Jul-20 0:37am

Sandeep Mewara

Comments

dnibbo 2-Aug-20 6:53am

Hi Sandeep

Thanks for the reply, it did look hopeful but alas it does not fix the problem.
That path specifies where VS will compile to.
Once compiled, I have no idea why, it copies it to another temp publish folder called C:\Users\myusernamexx\AppData\Local\Temp\WebSitePublish\WebPortalNet4-872599845

I need to somehow get it to use a different path for that bit.
I have looked in that .pubxml to see if there are any other paths that can be overridden but cant see anything.

One site suggested <PublishTempFoldername>C:\Pub\ but that didn't seem to work.

Thanks

dnibbo · Answer 2 · 2020-08-02T01:13:00

Solution 3

Thanks to Sandeep for his suggestion, it did lead to a solution in the end.

There is another node you can add which overrides the publish folder.

<_PackageTempDir>c:\pub\</_PackageTempDir>

It now works.

Posted 2-Aug-20 1:13am

dnibbo

Updated 2-Aug-20 1:25am

v2

Comments

dnibbo 14-Aug-20 3:48am

Please note that the above does not work properly either.
Files seem to get to the c:\pub folder but not the deployment folder and manually copying does not work.
I am now getting: Parser Error Message: Could not load the assembly 'App_Web_uznma5bb'. Make sure that it is compiled before accessing the page.
The search goes on :(