Hi Bob,

I think we might be talking at cross purposes. What I'm saying is that I shouldn't have to recompile. Version 1.1 should install over 1.0 and everything should still work. When our clients upgraded, for instance, to Win2k from Win98, I didn't have to recompile our VFP app for them, it simply worked as is. Nor did they have to go out and get new versions of all of the rest of the software on their system.

My contention is that Win2k seems to be a heck of a lot more massive and complex an upgrade from Win98 than Framework 1.1 is from 1.0, so why should I need a whole new VS.NET to use it, and why should my apps need to be recompiled to use it?

As you say though, it's moot now for me since I've got the newer versions of both on my machine. At least it is until MS comes out with Framework 1.2, and we all need a new VS.Net to use that one.

Alan

>Alan,
>
>I am not saying your 1.0 built ap won't run against 1.1 once you rebuild/compile it. I am saying that I would rather have two [or more] versions of the framework on my PC, than deal with the .dll hell we used to go through.
>
>Feel free to delete the 1.0 version of the framework, if you don't have any aps that need it. I am glad that 1.1 installs next to, instead of on top of 1.0, so I can decide when to delete it.
>
>BOb
>
>
>>>>I'm fairly sure that if you go to 1.1 with VS.net 2002, you'll end up having both 1.0 and 1.1 on your system (clutter as far as I'm concerned).
>>>
>>>Actually, that is part of the versioning. Your app will use the version of the framework it was targeted to. Nice that a new version of the framework won't break your legacy apps.
>>>
>>>BOb
>>
>>Usually backward compatibility hangs around for a version or two - even with Java, you get deprecation, but it's still usable. Upgrading to Framework 1.1 should not only not break apps targeted to 1.0, but it should just slide into place. Obviously not the other way around, but heck, this is only a .1 upgrade. It's not even a whole version. Imagine if every time you upgraded your os, nothing worked anymore with the new version of Windows. Normally, the latest update of something will handle what the previous one did, and more, certainly not less.
>>
>>On the other hand, as Bonnie pointed out, it may simply be a question of the order in which things are installed, and maybe it does work 'properly' after all. I don't really feel like uninstalling and reinstalling to find out.
>>
>>Alan