Need to move Framework assemblies to program files
Recently after MS updates on W7 we have had a problem were an application that ran fine prior to the update no long runs. The application uses a combination of legacy code and 3.5 framework assemblies. We have found that moving the assemblies to a program
files(x86) folder, re-registering them and then deleting them from the application folder fixes the issue. We cannot pin this to a particular update and have talked to other companies that have had a similiar problem. This is not isolated to just
7 but see on XP and Vista. Any ideas? Thanks.
August 19th, 2010 6:16pm
You should no do such things. Install a new Windows and check update is causing the issues."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2010 6:18pm
Haven't tried reinstalling W7 although have removed and resintalled framework and its primary service packs (3.5 sp1). Sometimes that fixes it, other times it doesn't. Sometime a regasm on the primary assembly fixes it, but then it may break
next day. Reinstalling O/S is not a viable option, we support the software not the hardware. Although not 100% sure, if I have software that works correctly at close of business one day, 12 updates are installed overnight and the software doesn't
work in the morning I am inclined to think the updates are related to the issue.
August 19th, 2010 9:21pm
That's why you should test all updates first, before deploying them."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2010 3:00am
Hi,
Thanks for posting in Technet.
I agree with Andre. This is a design bug of the application. I suggest you notice the application publisher to resolve this issue. To find the root cause, you may need to test in a Windows 7 system that does not have any updates on it. Then install updates
one by one then check the result. By doing so we can find which update conflicts with the application.
I suggest you focus on the .Net Framework 3.5 related updates.
Arthur Xie
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
August 20th, 2010 6:30am