Error while installing assembly into Global Assembly Cache

[gweihs]

I have a setup that installs 1 .NET assembly into the GAC. It fails with a message saying there was an error reading from the temp file (see attached image).

I have no other files to install, just that one. So there are no file copies happening during the install.

Any ideas?

[gweihs]

Heres the image

File Attached:

GACBug1.gif

[MichaelNesmith]

I think your setup output path may be too long, please try something shorter, try for example placing built setups in c:\\builds and see if that helps your situation.

[Gizm0]

Also verify that the assembly is strong name signed, otherwise you can't install it on the GAC!

[gweihs]

I have moved it to a different (shorter) path and it works fine from there. I dont see this being a long term solutions, however. Can you give me some details on this restriction, is it a bug? What is the max length of the filepath? We have a rigid build process that will take a lot of effort to change.

[MichaelNesmith]

You may shorten your source paths. Essentially, the MAX_PATH limit is being exceeded and this is the root cause of the problems we're experiencing here. The only workaround is to use shorter source paths or build output paths.

[gweihs]

It appears to be 100 character limit on the path... can you confirm?

[CandiceJones]

The limit is 255. Keep in mind that this limit may be exceeded when setup is running from the temp folder on the end user system. Therefore, best to use short paths.

You don't need to change your existing folder structure either. Just use subst drives to replace a very long source path with a single drive letter!

[gweihs]

Does this problem relate to GAC registration only, to everything or something in between.

[MichaelNesmith]

It effects all files that are built with InstallAware.