Solved

Error during build in visual basic project

Posted on 2008-10-15
11
948 Views
Last Modified: 2011-10-19
I am very new to programming and was given this project to try to figure out, While trying to build I get the error message the "ResolveAssemblyReference" task failed unexpectedly.  System.IO.PathTooLongException
0
Comment
Question by:jeremyj54
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
11 Comments
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22724408
The error explanation is quite straight-forward. It is telling you that app Path name exceeds the lenghts allowed by your IDE. I can't remember which is the maximun lenght allowed, but you can check in Help File.

Here you can find more info, http://msdn.microsoft.com/en-us/library/5eyyxc3b.aspx.

In order to build your app, you should move it to a root folder in the disk or to some not so deep folder.

Regards,
0
 

Author Comment

by:jeremyj54
ID: 22724550
I looked at that and put the project in the root directory and it still gets this error.  The path is nowhere near the 360 character cap.
0
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22724596
Have you check the path of every component that you could be using and its location on the disk? Forgive if I sound kind of rude before. I didn't mean it.
0
Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

 

Author Comment

by:jeremyj54
ID: 22724982
I have checked as well as I know how, is there an easy way to check all dependence paths?
0
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22725095
I haven't tried it, but this program seems to do what you are looking for:

http://www.codeproject.com/KB/cs/DependencyTracker.aspx
0
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22725110
Does the error provide more info? In which dependency component, it aborts building? Can you see it in your result/task bar?
0
 

Author Comment

by:jeremyj54
ID: 22725248
I have attached the error
Error.doc
0
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22725399
The error 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.

Check every folder of your solution... (check that you are building the app you moved to the root folder) and check that you are not having a deep folder structure for your app.

What about .NET framework installation directory? Is it possible that your may have installed in other location different from the default? Is your solution folder showing any missing dependency?

If nothing of this work, I don't know what else I can suggest to you...

0
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22726938
I've been researching on the Internet and I found this. Maybe it can be useful for you...

[...] post app.config or project file. This error seems to be with the project file / appconfig file and it [...]

After that the user answered:

Your comments lead me to look in the app.config file and I found a hold over runtime section for issues I was having with runtime binding

Below is the code that the user removed.

The comments continued: After pulling this out, it compiles fine.

You can find the whole post in the following address:
http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/90b81569-0dcd-4c5e-ab9e-32b92ff72b7e/

Please let me know if it helps.

Regards.
<input style="padding: 0pt; font-size: 14px; height: 18px;">
<runtime>
 
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
 
<dependentAssembly>
 
<assemblyIdentity name="Micron.Facilities.Data" publicKeyToken="2D8C82D3A1452EF1" culture="neutral"/>
 
<bindingRedirect oldVersion="1.*" newVersion="2.0.0.0"/>
 
</dependentAssembly>
 
</assemblyBinding>
 
</runtime>

Open in new window

0
 
LVL 3

Expert Comment

by:SpeedFingolf
ID: 22726947
I don't know what happened. My post originally was:

I've been researching on the Internet and I found this. Maybe it can be useful for you...

[...] post app.config or project file. This error seems to be with the project file / appconfig file and it [...]

After that the user answered:

"Your comments lead me to look in the app.config file and I found a hold over runtime section for issues I was having with runtime binding"

Below is the code referenced in the last paragraph

The comments continued: "After pulling this out, it compiles fine."

You can find the whole post in the following address:
http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/90b81569-0dcd-4c5e-ab9e-32b92ff72b7e/

Please let me know if it helps.

Regards.


<runtime>
 
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
 
<dependentAssembly>
 
<assemblyIdentity name="Micron.Facilities.Data" publicKeyToken="2D8C82D3A1452EF1" culture="neutral"/>
 
<bindingRedirect oldVersion="1.*" newVersion="2.0.0.0"/>
 
</dependentAssembly>
 
</assemblyBinding>
 
</runtime>

Open in new window

0
 

Accepted Solution

by:
jeremyj54 earned 0 total points
ID: 22777418
I finnaly found out that the problem was that I had the wrong version of visual studio, I had vs 2005 standard and only the pro version works with crystal reports.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background What I'm presenting in this article is the result of 2 conditions in my work area: We have a SQL Server production environment but no development or test environment; andWe have an MS Access front end using tables in SQL Server but we a…
This article describes some techniques which will make your VBA or Visual Basic Classic code easier to understand and maintain, whether by you, your replacement, or another Experts-Exchange expert.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question