Issue 102937 - Extensions and long path names
Summary: Extensions and long path names
Status: CLOSED DUPLICATE of issue 50885
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m49
Hardware: All Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: mikhail.voytenko
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 09:44 UTC by thomas.lange
Modified: 2013-08-07 15:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description thomas.lange 2009-06-19 09:44:17 UTC 
Extensions can not be installed if the overall path to the installed extension
gets too long. There are two versions to reproduce the problem
1) give the extension a rather large name (e.g. 50+ characters)
2) the installation path of the Office is already quite long

It might be possible that similar problems apply to 'normal' document handling
as well.
Comment 1 thomas.lange 2009-06-19 09:45:41 UTC 
.
Comment 2 thomas.lange 2009-06-19 09:45:56 UTC 
.
Comment 3 thomas.lange 2009-06-19 09:48:46 UTC 
This problem seems to be Windows-only specific.

A possible solution might be to use the GetShortPathNameW from the Windows API.
By doing that one can (once again) obtain file handles that can be used with
fopen and the like, even if the path name is long.
Comment 4 bmarcelly 2009-06-20 09:44:20 UTC 
I think this is a duplicate of Issue 50885
Comment 5 mikhail.voytenko 2009-06-23 08:04:01 UTC 
Indeed, it is a duplicate. Closing.

*** This issue has been marked as a duplicate of 50885 ***
Comment 6 mikhail.voytenko 2009-06-23 08:04:34 UTC 
.