.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Path too long packaging or deploying SP2010 solutions in VS2010

Posted By:      Posted Date: August 31, 2010    Points: 0   Category :SharePoint
I'm regularly getting "Error 2 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" building projects with VS2010 for SP2010. I've done what I can to reduce the length of the path but unfortunately I have rules for the namespaces I must use. This is really frustrating and causing issues for our team trying to meet our business requirements. Is there any way to improve this situation apart from shortening the paths? (Similar to this post for the RC build: http://social.technet.microsoft.com/forums/en-us/sharepoint2010programming/thread/36D35235-6736-410F-ACC6-03C0BDCC4FE2) Thanks, Alex.Alex Angas - http://www.alexangas.com/blog

View Complete Post

More Related Resource Links

Path too long when deploying


Hi all,

i have problem with deploy on my sharepoint project. Unfortunatelly we have company naming convention, which i have to use.

I found some information about \\?\ unicode support for paths, but is possible to change deploy path in visual studio 2010 (for redirecting to higher folder or adding \\?\).


Thx for help.

SharePoint's Sandbox: Developing, Deploying and Monitoring Sandboxed Solutions in SharePoint 2010


The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.

Paul Stubbs

MSDN Magazine November 2009

.NET Framework: Building, Packaging, Deploying, and Administering Applications and Types-Part 2


Part 1 of this series discussed how types built for the common language runtime can be shared among applications in the Microsoft .NET Framework regardless of the .NET languages used to build them. This second part continues with building assemblies by first covering security, sharing assemblies, versioning, localization, and side-by-side execution. Because in .NET two DLLs with the same name can be loaded as long as another attribute-which can include the localization language-differs, versioning is much easier than it used to be, so DLL Hell may become a thing of the past.

Jeffrey Richter

MSDN Magazine March 2001

.NET Framework: Building, Packaging, Deploying, and Administering Applications and Types


Types that are built for the Common Language Runtime can be shared among applications in the Microsoft .NET Framework no matter which of the .NET languages they were built in, an obvious benefit to developers. This article describes the building, packaging, and deploying of applications and types for the .NET Framework, including the role and significance of assemblies, private and otherwise. The way metadata and assemblies help to solve some historical problems like versioning conflicts and DLL Hell, and how they improve system stability are also discussed.

Jeffrey Richter

MSDN Magazine February 2001

Fresh VS2010/SP2010 install. Cannot Deploy default BCS template.

Error ocurred in deployment step 'Add Solution': Failed to load receiver assembly 'Microsoft.Office.SharePoint.ClientExtensions, Version is everyone else getting a BCS template to work  ?If you do SharePoint dev and have MSN add me!! punkouter@hotmail.com We can help each other out. My SharePoint Blog ---> http://punkouter.spaces.live.com/

Path too long (Exception from HRESULT: 0x80010135)

Hi I have recieve this error any idea how to solve it Path too long (Exception from HRESULT: 0x80010135) ThanksMomo

VS2010 Deploying Database Project - Error: Cannot create file [...]MSSQL10.MSSQLSERVER\MSSQL\DATA\m

I had SQL Express from a previous installation of VS2010. I uninstalled All SQL and VS2010 and re-installed VS2010 (without Express) and then re-installed SQL Server 2008 Developer Edition. Now when I try to deploy a database project I am receiving the following error:     Creating EDDY.Cheetah.Database.Server... ...\sql\debug\Server.sql(38,0): Error SQL01268: .Net SqlClient Data Provider: Msg 5170, Level 16, State 1, Line 1 Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf' because it already exists. Change the file path or the file name, and retry the operation. ...\sql\debug\Server.sql(38,0): Error SQL01268: .Net SqlClient Data Provider: Msg 1802, Level 16, State 4, Line 1 CREATE

JS script file path screwed up after deploying MVC application

Hi,  I am relatively new to MVC, after deploying my MVC application as per Haack http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx i seem to have got a new problem. My Jquery doesnt seem to get recognized. I get "object doesnt support this property or method " at this line "jQuery(document).ready(function() {" i have tried all sort of things including changing the js script file path to relative and absolute, setting base tag etc. Kindly advice if the above method of deploying is right and if that is what is causing the issue and if there is some other way to handle the .mvc requests.   Thanks and Regards, Muzammil Ahmed

Need help deploying SP2010 Document Converter using Visual Studio 2010


I have created an SP 2010 Document Converter app, which seems to work fine in all respects except it doesn't seem to be converting documents in SharePoint. I think there is a problem with the way that I'm deploying the converter executable to the server, but I am having trouble finding the specific issue.

Some notes:
* SP 2010 sees the document converters in my Elements.xml file and is making them available in Sharepoint.
* When I tell SP2010 to convert a document using one of my Converters, I can tell that the service is trying to do *something* in the Central Administration console (job shows up with progress bar and sits there for a while). I have no idea what it's actually doing during that time though.
* All of my executable and executable DLLs have been defined in VS2010 as having "Application Resource" Deployment Types - not sure if this is right because the MS SP2010 SDK info doesn't seem to give much guidance on this subject. VS 2010 is deploying all of the appropriate executable files to C:\inetpub\wwwroot\wss\VirtualDirectories\80\resources\PDFDocumentService\DocumentConverter\". I have no idea if this is a sensible location for document converter executable files. When I try to run my executable in this location from the command line, it works fine.

My guess is that there's a disconn

Path Too Long Problem. Accessing filenames longer than 260 chars using unicode and kernel32.dll.

I found this article a few weeks ago that provided a way to access files and folders past the 260 char length:


I put the code from "Finding Files and Folders" in a dll and wrote an app in vb accessing these functions.  However, the code randomly breaks on a specific kernel32 function call. 

I noticed that if the search finds a file (not folder) longer than 12 to 14 characters then it breaks on occasion.  This is strange because I would think it would either never break or always break.

Here's the line where it breaks:

// find next

found = FindNextFile(findHandle, out findData);

Any ideas?


Custom Webpart doesn't show up in Sharepoint 2010 after deploying from VS2010

I have created a visual webpart in VisualStudio 2010 as Farm Solution and after deploying the webpart doesnt show under Categories(Custom) when i click insert webpart

Help - uanble to Debug Feature Receiver with VS2010 on SP2010 Farm



I am unable to debug the feature receiver using VS2010. I Changed the Active Deployment Configuration from Default to No Activation. Set the breakpoint and press F5, I get the below error

 "Unable to start debugging on the web server. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. "

 We are running VS2010 on x64 bit Windows2008 server and the farm has 1 App server, 1 WFE server and 1 sql server.

I would really appreciate any help regarding this.



260 Characters in File Path - Too long


I have a Windows Service that is getting cought up on file paths that are longer than 260 characters.  I have googled just about every combination of this problem I can think of as well as various other forums.  From what I have read, Windows System.IO has a limitation on file paths of 260 characters or less.  However Microsoft's latest release of Robocopy has support for 260+ characters.  I have also read that a couple people mentioned unicode file paths which support up to 32,000.  The limitation is set with the MAX_PATH and internet explorer and Robocopy use unicode filepaths to save long files.

My workaround right now is to trap and skip the folders while I would like in the future to be able to have paths longer than 260 characters.  This right now is the ONLY work around, so the obvious "why dont you just move the folders?" response is out of the question.

My question is: Is there a way to use unicode file paths with the FileInfo class?  Perhaps using PInvoke?  Can you give an example for me?

Event Type: Error
Event Source: File Mirroring Service
Event Category: None
Event ID: 0
Date:  8/9/2005
Time:  8:42:28 AM
User:  N/A
An error occured:
The path is too long after being

Deploying Branding Solutions for SharePoint 2010 Sites Using Sandboxed Solutions

Learn to create sandbox-compatible branding solutions using custom master pages, CSS files, and images that can be deployed to SharePoint 2010 farms.

Sample: Deploying Branding Solutions for SharePoint 2010 Sites Using Sandboxed Solutions

Explore the code as you learn to create sandbox-compatible branding solutions using custom master pages, CSS files, and images that can be deployed to SharePoint 2010 farms.

Sharepoint/SSRS: The full path must be less than 260 characters long

Question: I setup a dual server Sharepoint deployment with SSRS and now I keep getting the error like the one below when I try to save a report or a datasource on the server:

The path of the item 'http://intranet/sharepoint/CompanyReports/MyReports' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.

I'm looking into permissions but this happens regardless of authentication I select on the client end.

Deploying SQL CE dll's for VS2010 Unit Test


I'm trying to uint test the methods of a class which derives from a base class in another assembly. The base class uses Entity with SQL CE.

Normally the System.Data.SqlServerCe.dll and System.Data.SqlServerCe.Entity.dll are in the common build target directory, along with the base class assembly's dll. They don't get copied to the TestResults/<test>/Out directory. (The test assemblies do NOT target the comon build target directory; they use "bin/Release" or "bin/Debug".)

The base class assembly dll DOES get copied to the Out directory, along with other project dll's it depends on. These also have been copied to the bin/Debug (bin/Release) for the unit test project, but the SqlServerCe dll's are not there, either.

I tried using [DeploymentItem("System.Data.SqlServerCe.dll")] to copy them to the Out directory, but with no luck.

Adding the files to the Deployment list in the Test Settings, DOES copy them to Out. However, the unit test still fails in the same way... An exception is being thrown when the main entity class (derived from ObjectContext) is constructed with the connectionString.  The exception message is:

The specified store provider cannot be found in the configuration, or is not vali

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend