Changing assemblies or files in a 'moved' project

glenharvy · Post by **glenharvy** » Mon Mar 09, 2009 3:47 am

Hi,

Recently I upgraded my PC and re-installed IA, I think successfully.

I copied the old IA Project folder from the old HD to the new PC's HD. I now wish to change the files and the locations of various files and assemblies in my IA Project. IA however no longer includes the new files/assemblies in the new compilation.

For example, changing the location of the assembles from one directory (eg D:\\xyz) to another (eg C:\\abc) means that they are not included in the compilation. The compilation window indicates the 'new' files are 'copied' but they are not being included in the compression. Change the directory back to the 'old' one and they are copied and compressed!

Has anyone any suggestions as where to look for a solution.

Thanks.

bokkie · Post by **bokkie** » Mon Mar 09, 2009 6:34 am

Does the File Paths on the Project tab help? I've never used it before but it hints at refactoring which is what you want to do?

MichaelNesmith · Post by **MichaelNesmith** » Mon Mar 09, 2009 10:23 am

Glen, do not cross post the same question in multiple places.

glenharvy · Post by **glenharvy** » Mon Mar 09, 2009 4:09 pm

bokkie wrote:Does the File Paths on the Project tab help? I've never used it before but it hints at refactoring which is what you want to do?

Yes, the File Paths refactors the paths BUT the problem remains.

To be more succinct:

It seems that the files in the new path are being 'copied' but they are not being 'compressed' into the new build. The resultant build size is notably smaller than it should be and when trying to use it, an error message comes up saying the installer can't locate the file.

Got me stumped!

glenharvy · Post by **glenharvy** » Mon Mar 09, 2009 4:12 pm

MichaelNesmith wrote:Glen, do not cross post the same question in multiple places.

Sorry, my email to support as well as lodging a ticket were meant to be direct requests to InstallAware for help. As neither of those are publicly available sources of information, I didn't think that asking my peers for help would be an issue.

I know I'm grasping at straws but I am desperate for pointers from anybody.

MichaelNesmith · Post by **MichaelNesmith** » Mon Mar 09, 2009 7:43 pm

Re-visit our support policy page at http://www.installaware.com/support-service-options.htm. Your options are to narrow the issue down and tell us exactly where the bug in InstallAware is so we can fix it for you or provide a workaround, or to order a support incident if you would like us to do the investigation for you.

Of course, it is possible that this is a problem in your script, your project, or other kind of user-error too. This is why our support guidelines require you to narrow the issue down and find the exact problem. We really cannot help you with generic reports like these.

glenharvy · Post by **glenharvy** » Wed Mar 11, 2009 12:43 am

MichaelNesmith wrote:Re-visit our support policy page at http://www.installaware.com/support-service-options.htm. Your options are to narrow the issue down and tell us exactly where the bug in InstallAware is so we can fix it for you or provide a workaround, or to order a support incident if you would like us to do the investigation for you.

Done that.

After changing the paths to the files/assemblies listed in the project, the files are copied during compilation but are not compressed nor included in the final build.

Using the refactoring tool to change the paths doesn't make any difference.

The easiest workaround is to not change the paths - in my case reconstruct the original hard drive partition's drive letters. I presume I could reconstruct the whole project but that is just to daunting as it took me virtually years to get it to the stage it's at

.

I can't imagine you issuing a patch for a now obsolete version and I'm not going to pay for a bug fix - not even Microsoft charge you for that