By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,717 Members | 2,052 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,717 IT Pros & Developers. It's quick & easy.

Visual Studio 2005 reporting Error 13 : Unknown Build Error

P: n/a
Hello, I have a problem when working with a program that uses XAML in
one of the modules.

I copied some XAML code from another working project into an existing
project, then when trying to compile the project I get the following:
Error 13 Unknown build error, '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.'

The XAML code that was entered was the following:

<Window x:Class="WPFPhotoGalleryDemo.Window1"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="clr-
namespace:Leadtools.Windows.Controls;assembly=Lead tools.Windows.Controls"
Title="LEADTOOLS WPF Photo Gallery Example" Width="800"
Height="650" Background ="Black" Icon="lv.ico"
ResizeMode="CanMinimize"
>
<Grid>
</Grid>
</Window>

I am using VS 2005 SP1 with .NET 3.0 extensions installed. The OS is
Windows XP Home SP2.

How do I resolve this error?

Thanks.
Mike
Jun 27 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Fri, 11 Apr 2008 15:06:10 -0700, eljainc <el*****@sbcglobal.netwrote:
Hello, I have a problem when working with a program that uses XAML in
one of the modules.

I copied some XAML code from another working project into an existing
project, then when trying to compile the project I get the following:

Error 13 Unknown build error, '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.'
That's the sort of error that can be hard to diagnose without access to
the entire project and the computer on which you're trying to compile it.

However, as a suggestion: given the error, and given that the same code
worked in a different context, you probably should be looking at how the
new context compares to the old one. Specifically, your new project in
which you've added the code, does the project live deeper in your
directory structure and/or have longer directory names?

The example you posted doesn't even have relative references to local
files, except possibly the icon. So it's hard to see from here what might
be different and causing the error. But maybe the local project into
which you copied the code text itself is too far into the directory
structure, or maybe there's some implicitly generated local file reference
that's not obvious.

Finally, it's possible that at some point the example is causing an
illegal path to be generated, in that the path is simply garbage for some
reason. Why that would be I can't say. But obviously if it's not a valid
path in the first place, the length easily could be too long too.
Unfortunately, an invalid path that's too long will hit the length-check
first, generating the error you're seeing rather than a more specific one
telling you that the path itself just isn't right.

I think it's more likely to do with where the project is and the depth of
the directory structure. But without being right there looking at the
computer, it's difficult to say for sure.

Pete
Jun 27 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.