Application signing issue with long paths

[Franky_31]

Hello,

I am having some issues when trying to sign my applications within Labwindows/CVI ("Build/Target settings/Signing info" dialog box).

If my project is in a folder with a "too long" path (definitely less than 255), compilation ends with a "Signing errors" message. 

The same project copied/pasted to a shorter path will compile without problems.

Is there a specific max path length linked to the signing process ?

Thank you for helping

Franck

[L.Zakarian]

Hello Franky_31,

As far as I know, there is no specific max path length linked to the signing process.

However, the standard length limitation for the path length (260 characters) must be respected and there is no workaround for this.

In order for me to help you, can you give me :

-An example of a path which works for the signing process,

-An example of a path which doesn't work for the signing process,

-The informations written on the signing error message that is prompted at the end when it doesn't work.

[rolfk]

---

@L.Zakarian wrote:

Hello Franky_31,

As far as I know, there is no specific max path length linked to the signing process.

However, the standard length limitation for the path length (260 characters) must be respected and there is no workaround for this.

In order for me to help you, can you give me :

-An example of a path which works for the signing process,

-An example of a path which doesn't work for the signing process,

-The informations written on the signing error message that is prompted at the end when it doesn't work.

---

As far as Windows goes, there is nowadays by enabling a feature somewhere that allows for long path names even in the ANSI variant of Win32 APIs (it supported that for the WideChar API variants for a long time already, since about Windows 2000 at least) if the underlying file system allowed for that. With NTSF being the pretty much only file system under Windows since many years, this was a given for a long time.

That of course doesn't mean that it will work in LabWindows/CVI. The CVI routines accessing the Win32 API also all have to support long path names for this to work and that requires to change all such routines from using fixed sized temporary stack variables for paths to using dynamically allocated temporary variables. A major redesign effort!