Size limit on web based builds?

[stampy]

Hello!

I'm evaluating (and still a little new to this ) and so my apologies if this has come up before -- I looked but didn’t see it mentioned. I'm guessing that I’m hitting a file size limit, probably MAX_PATH (260) when trying to create web-based setups. E.g.:

"Error during build: Unable to copy file to <c:\\my InstallAware setup folder>\\Release\\Web\\data\\<the name of my feature>\\d_\\<path to the file I want to install>\\myfile.dll"

It builds fine when building a Single Self-Installing EXE. Apparently, when building web-based setups InstallAware creates temp folders concatenating the source file path with the project path, along with other stuff, it hits some max path limit (rather quickly) in my case. If I change the location of my project to something short like “c:\\temp” it builds OK.

We tend to use deep directory structures here and apparently my workaround would be to simply relocate my InstallAware project. While this is not a big deal, it makes it a bit annoying because it would be nice if I could keep the same folder hierarchy that is saved in our version control (without having to remap the build root). Is there any other workarounds for this? Thanks!

[MichaelNesmith]

Hi Stampy!

You are right, you are hitting the MAXPATH size limit here. You have already found the correct workaround, and I apologize for the inconvenience this is causing. A partial remedy would be to keep your project in the same folder but to redirect your output to a shorter folder using the Project Options dialog, Build->Output node, "Output filename" field. This will at least allow you to store your main project files in your proper source control folder structures.