.Net 3.0 runtime File Bag fails to build - is path too long?
Posted: Tue Feb 16, 2010 2:46 pm
Hi. I am evaluating installer builders for my company's new .Net applications. So far we have been able to do everything we need with InstallAware, which has not been possible with any other product we've tested yet.
But we encountered a troubling problem - most troubling because it was entirely unclear why the failure occurred.
We created an installer using all defaults for the .Net Setup template. At this point the installer would build.
We then simply selected the .Net Framework v3.5 SP1 Runtime (its dependencies all automatically checked themselves), and built the setup.
The setup would fail with only "Error during build: Failed to compile plug-in action: File Bag", which occurred immediately after "Built plug-in action MSXML".
Through trial and error we found if we unchecked the .Net 3.0 runtime the installer would build.
After much frantic experimenting, we realized that if we moved the whole setup project folder to a less recursed directory (i.e., shorter path) it would build correctly with the .Net 3.0 runtime re-checked.
We concluded that there was probably a file copy error due to too long of a path, but there was absolutely no information we could find to indicate anything more specific than "Error during build: Failed to compile plug-in action: File Bag".
Did we miss it in the documentation somewhere? Maybe its specific to Windows XP?
I suppose it's easily avoided once known, but for a moment we were pulling our hair out trying to figure out what went wrong.
But we encountered a troubling problem - most troubling because it was entirely unclear why the failure occurred.
We created an installer using all defaults for the .Net Setup template. At this point the installer would build.
We then simply selected the .Net Framework v3.5 SP1 Runtime (its dependencies all automatically checked themselves), and built the setup.
The setup would fail with only "Error during build: Failed to compile plug-in action: File Bag", which occurred immediately after "Built plug-in action MSXML".
Through trial and error we found if we unchecked the .Net 3.0 runtime the installer would build.
After much frantic experimenting, we realized that if we moved the whole setup project folder to a less recursed directory (i.e., shorter path) it would build correctly with the .Net 3.0 runtime re-checked.
We concluded that there was probably a file copy error due to too long of a path, but there was absolutely no information we could find to indicate anything more specific than "Error during build: Failed to compile plug-in action: File Bag".
Did we miss it in the documentation somewhere? Maybe its specific to Windows XP?
I suppose it's easily avoided once known, but for a moment we were pulling our hair out trying to figure out what went wrong.