some of my clients have installed the .Net Framework 3.5 SP1. Since doing so, my application (which runs on framework 2.0) has stopped working with the usual ("[program name] has encountered a problem") message. Clearly the 3.5 update has knocked out the framework 2.0.
I have fixed this by removing the frameworks (including 2.0) and reinstalling 2.0. this seems to fix the problem, but...
Is there a cleaner/easier way to deal with this
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thank you for the post.
I know it is THEORETICALLY incremental and updates previous frameworks, but on many of my clients systems .Net 2.0 applications fail to run after this SP is applied. After the 3.5 update their systems are behaving as if the framework 2.0 has been corrupted in some way. Thankfully, my clients see this for what it is: my software ran before the Microsoft update but not after the update = Microsoft's doing.
That's OK, but I think that your only real solution is to find why the software is not working after the SP is applied, in order t osort out or workaround any incopatibilities, because you can't trust that all your clients are going to stop the Framework to update (it's being pushed trough Windows Update).
problem is that the error message is that general "encountered a problem and needs to close" - it sends a load of garbage back to MS, but means nothing to me.
I suppose rather than waste 2 weeks troubleshooting this, I could roll everyone up to framework 3.5 but we're talking hundreds of firms - thousands of users. Not sure I want to embark upon this project this side of my holiday! :D
Thanks for the input so far.
The issue is caused by the fact that we use Remotesoft Protector to protect our IP. At this stage, Remotesoft do not seem interested in solving this issue, so we are considering alternative measures such as straight obfuscation. So...
Do you know of any free (or cheap) but good obfuscation tools?
Here is a good one, it's basic version comes with Visual Studio:
http://msdn.microso
Business Accounts
Answer for Membership
by: Juan_BarreraPosted on 2009-02-02 at 16:02:51ID: 23532889
The .NET Framework releases are supposed to be incremental, that is, each version installs on top of the other and patches previous versions. It doesn't delete them.
Installing .NET 3.5 SP1 updates .NET 2.0 to SP2, so you'll have to find out what's the difference between .NET 20 RTM and .NET SP2 that is causing the error.