It's pretty unlikely that "the registry could disappear" very soon.
However, for some kinds of apps, there is a desire to support "xcopy
deployment" - deployment by just copying files. For those apps, having
application configuration stored in the registry would conflict with xcopy
deployment.
In addition, XML serialization of classes provides a very interesting
mechanism for doing application config. Just define a class with all of
your application settings in it, and use XML serialization to load / save
the settings. You can put off writing an editor for all of the settings,
because you can just use notepad (for a while, until your app needs to be
really polished) to change settings.
Finally, some personal speculation: The registry was invented before XML
existed. If the registry was being invented today, fresh, from nothing, XML
would probably have a huge impact on that the "registry" would look like.
--Don
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Rohit Santhanam" <mr*******@hotm ail.com> wrote in message
news:a8******** *************** *****@phx.gbl.. .
As I am reading the .NET documentation, I get the feeling
that Microsoft is trying to get rid of the registry. My
understanding is that an application built using .NET
does not use the registry at all. So, conceivably as
applications are migrated to .NET, the registry could
disappear in a future version of Windows. Does anybody
out there agree with me?
Of course, they might keep the registry for backward
compatibility purposes.
Thanks,
-Rohit
