The obvious answer is Quicken, time tested, mother approved. Just spend the money, you know it'll be around for years.

DP

What is it about WPF that gives it a "Wow" advantage over using standard controls? I've heard comments like this, but I don't understand the difference. I'm sure that's because I know little about WPF at this point, but I'd love it if you could elaborate.

DP

WPF sounds like a good idea, but I'm wondering if it's worth the learning curve. Has anyone here actually used it successfully? Any positive or negative comments?

DP

I want to ask what the general opinion is in regards to the best way to install components (controls and dlls). I'm fairly new to .NET, and am begining the process of converting some of my companies COM components to .NET. Here's what I think I understand my options to be so far: - Install as private assemblies to some common directory: This is easy, but if we ever modify a component (which we do often), and send to customers, they will need to update all references in their client apps, which would be a pain. - Install to the GAC: This would prevent client apps from needing to update references but seems to add many other complexities. First off, my .NET components will be importing many COM components, so I have a bunch of Interop DLLs. All of these will need to be assigned strong names and also installed into the GAC. Some of these COM components may change along the way as well, which means the Interops will need to be regenerated, strong names reassigned, blah blah. Sounds like a royal pain as well. I'm guessing some of you have been through this. What's the best path to take? Is there another option I'm not aware of?

DP