That .NET 4.0 stuff kills Sonar.

I accidentally installed it when I recently did a format/fresh install of my OS and my DAW does not run right with it. It never did, but it's been so long since I did a fresh install, I forgot about the .NET 4 crap and installed it.

Oh well, time to format ... again.

Honestly, these are DAW's. They shouldn't be on the net, period. Doing all these updates is a waste of time unless we actually see something from Cakewalk that says, hey, this is broken, do this update and it will fix it. To date, I've never seen that. So ... next time I format, I'm not doing a single update and the DAW is never going to see the internet.

CakeAlexS


> But this worked for **nobody** 

As thousands apparently had the problem that must have been some survey. Guess all of them were developers and IT experts who knew what they were talking about ;). Microsoft continues to transfer it's codebase towards .NET for good reason.

CakeAlexS,


With all due respect, if everyone needs to be a developer and IT expert to run a program, then someone out there missed the point... ;)  You may be right about some points, but I can tell you (after dozens of times trying the steps you suggested) that it does not work. For me, and many others.  I've wasted dozens and dozens of hours searching, trying, writing, removing, repairing, reinstalling - but I did not want to waste more time with reinstalling Windows (with all that it involves).  If I decide to upgrade to Win 8 then probably I'll chosse the clean install route.  You are raising something interesting though, about a folder in the Windows directory : that's one I never seeked for (and I admit: don't know what to search for...) - I had read something about it (might have been the remainings of a previous Office installation too...). That being said, I also admit I never experienced problems with SONAR (though I had weird things such as impossible to update Pro Tools 9, for which hours - again - never solved the issue. After hours of troubleshooting with Avid, they found out there was only one other in North America with that same issue - go figure if that might also be related to that same .NET story ..? Don't know.  Ended out using PT only under Mac OS X since then...)


No offense.
Rob

Nope I'm saying in order to diagnose an issue and blame something you need to come up with something technical rather than point to something and blame it, it could easily be something else and there could easily be another solution.

To say that every-time they install .NET 4 it screws their machine up clearly points to another issue in my experience, far away from .NET

The last poster said he doesn't want to connect to the internet anymore... fair enough. Somebody else however might say I BLAME THE INTERNET! And then attempt to back it up by stating "thousand have used the internet and it crashed their machines". So you see what I mean, you need to be specific before you do the finger pointing. Look in logs, attempt repairs, check your hard drive. Most non-experts should be able to handle it to be honest if they take time to google, so I apologize for sounding a little snobbish.

For instance maybe it could be firewall type software was blocking the .NET application communication with another app. The fact that Sonar does NOT run on .NET here also seems a little strange. Why are you installing in the first place? Well because there's something else running on it that you are not tell us about. That could be something that's interfacing with your drivers... etc etc.


There's a bigger picture at work here.

My experience with issue like these is that every once in a while, Microsoft incorrectly stages its updates. It's an issue with the logic within the Update service within Windows.

Now, 99.999% of the time, if you leave you're computer alone and just let it automatically apply updates, you're never going to have a problem. but selective install or de-install certain services or packages, .Net among then, and there is a small chance you'll encounter an issue. As an personal example, I had issues with a clean install of Windows 7. After the install and the hours long cycle of letting apply group after group of updates, it began to fail to apply certain updates. The solution was to tell the system to ignore/hide those updates, so that it continue on. At a later point, I was able to apply those failing updates. The whole point is, if MS can get get the order of dependencies wrong, it can get the wrong ones too.

Thank you for all the info. I did have a couple of updates fail, and when I was having problems, the first thing I did was go back and reinstall those updates. That just made things more unstable. So far, I haven't encountered any problems with my audio programs. Sound Forge uses the .NET framework, and it runs just fine, so I'm assuming it's using an older version. I surf the internet using my studio comp, and update my progs, but I don't play games or do anything else with it. So, for now, I'm going to leave it alone. If it works, then I'm not going to mess with it.

From what I've read, the client profile is a cut down version of the full framework, and it's main purpose is for tablet devices. I don't use tablets, or even connect my phone to the comp.

I agree with Bub. 

Build your DAW. 

UNPLUG IT FROM THE NET

Install DAW software and live happily ever after. 

Sorry bro, don't agree.

Years of broadband connected to my DAW...never an issue...

V
 
btw - liked your Squirrel Nut Zippers cover...

> and it's main purpose is for tablet devices.

The only purpose is for it be be accessed by any application that has a dependancy on it. Doesn't matter about the hardware :).

Cheers...