Hey, we were about to buy the NetAdvantage for WPF at our company, and I wanted to try it before buying it.
But I am getting error while I am trying to install it.
I have tried the installation with and without the administrator account, and it is still given the same errors.
Log files:
IGPlatformInstall.log
Infragistics_VSExtension_20131.msi.txt
NetAdvantage_VersionUtility_20131.msi.txt
NetAdvantage_WPF_20131.msi.txt
NetAdvantage_WPF_20131_Help.msi.txt
Hi Nawed,
I believe it's an OS specific issue since the installer is unable to find the registry value under "HKLM\Software\Microsoft\Windows\CurrentVersion\explorer\Shell Folders\Common Documents". I believe this setting is corrupt on your system. Could you give us more information about the OS you are trying to install NetAdvantage for WPF? This is an example of similar issue with Microsoft Office installation:
http://support.microsoft.com/kb/886549/en-us
And this is how these registry keys should look like at the different operating systems:
http://social.technet.microsoft.com/wiki/contents/articles/6083.windows-xp-folders-and-locations-vs-windows-7-and-vista.aspx
It could be a matter of installing a SP or a Microsoft KB to fix this issue. It might be even a virus that has corrupted / modified these values.
Best regards,
Alexander Vezenkov
DevOps Architect
Infragistics
Hey Alexander,
Thanks for the quick reply.
I am on Windows 7 machine, with service pack 1.
Its windows 7 Professional 64bit OS.
And I checked the windows registry all the values are the same as the mentioned site above.
This is the first and only installer I had problems with.
This is really strange because we are using a standard MSI Registry Search Custom Action and it's returning an empty string for the registry that I mentioned.
I will ask Developer Support to have a case for you and try to reproduce the issue so we can resolve it? We're performing lots of tests on Windows 7 SP1 x64 machines before we ship the installers so I don't think the problem is the OS. We will be very glad to resolve the issue for you. We need to reproduce it and locate the problem.
Thanks,
Alex
Hey Alex,
Thanks again.
Another user of yours fixed this.
And he told me to slap the network guy, so probably the problem was within the network.
Thanks again