CroMagnon Posted July 22, 2011 Share Posted July 22, 2011 I notice when I install Paint.Net 3.5.8 on an XP 32 bit system that it installs some amd64 elements in the winsxs folder. I am trying to track down the redistributable that it installs that does this. I know that it installs VC++ 2008 SP1 and .net 3.5 SP1, but when I install these seperately I do not get the amd items. Are there other redists that it installs? Thanks, Cro Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted July 22, 2011 Share Posted July 22, 2011 Why are you asking? Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
CroMagnon Posted July 22, 2011 Author Share Posted July 22, 2011 Why are you asking? We have an app that migrates apps and settings to a new computer. We are having issues migrating these amd64 sxs entries and after the migration Paint.Net doesn't run correctly. Because of security rights you can't actually copy anything into the sxs folder, only TrustedInstallers can do that. Basically we identify all redists an app uses and then install those after the migration. With Paint.net the app sees these amd64 entries and tries to run a 64 bit version of the redist installer, which of course fails. Any help would be greatly appreciated. Cro Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted July 22, 2011 Share Posted July 22, 2011 Ok so don't migrate them. Paint.NET obviously doesn't need the 64-bit binaries. They're installed because that's just how Visual Studio automatically added the dependencies, there wasn't a good way to remove it only for 32-bit machines, and it didn't cause any trouble anyway so why mess with it. I really don't understand why you need to do all this back-breaking work to migrate things. Just recognize that Paint.NET was installed, and run the Paint.NET installer from scratch on the new system. There's no good reason to try and reverse engineer the installer and figure out all the weird little things it does and then determine how to migrate each one, especially since those things can and do change over time. You'll save a whole lot of pain and headache if you just let Paint.NET install itself the way it was designed to. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.