Alex Rivera | Logout

How can you control the file names for .NET Service References?

Asked 2011-09-01T14:50:39.170
16

Windows has a limitation of 259 characters in paths. Unfortunately, this is starting to cause problems for us due to some of our Service Reference names.

For example, we have our TFS branch with an already-long path, and then .NET service references nearly double this because they always use the fully-qualified namespace as the file name:

Some.Really.Long.Fully.Qualified.Namespace.Service.Reference.Name.datasource

AFAIK, you can't change the name of the service reference -- but Ihoping I'm wrong. Can this be done?

If not, are there any other possible workarounds to this annoying issue?

EDIT: Also, I know one obvious solution would be to shorten our namespaces and/or paths, but assume we can't do that in this case. :) I'm mainly trying to figure out how to control the file names for the service references.

UPDATE: The root issue I'm having is where TFS is not letting me get latest on a particular branch. Here is the exact error:

TF205022: The following path contains more than the allowed 259 characters: [C:\Some-really-long-259-character-path-here]

Edit
Report

1 Answer

14

Turns out, these .datasource files can be deleted, as they are not needed to build the project. So we just did a sweep of all .datasource files in TFS, and deleted them.

This article talks more about this.

answered 2011-10-03T20:52:19.277

Your Answer