It virtualizes c:\Program Files for "compatibility" so that you can see bizarre situations like writing to a file and then having it not exist where you thought it was.
To avoid these virtual store problems, you have to embed XML in your application's executable to get the infamous ALLOW or DENY window to bother the user. If you use Visual Studio 2005 to do it, watch out! There's a bug in a certain class of unpatched XP that blue screens the computer because of the way the XML is structured that Visual Studio's manifest tool spits out when it merges manifest fragments. It's all overly complicated.
I would never develop Windows software if there wasn't a market for it--it's exciting to see the underdogs picking up marketshare.
It virtualizes c:\Program Files for "compatibility" so that you can see bizarre situations like writing to a file and then having it not exist where you thought it was.
To avoid these virtual store problems, you have to embed XML in your application's executable to get the infamous ALLOW or DENY window to bother the user. If you use Visual Studio 2005 to do it, watch out! There's a bug in a certain class of unpatched XP that blue screens the computer because of the way the XML is structured that Visual Studio's manifest tool spits out when it merges manifest fragments. It's all overly complicated.
I would never develop Windows software if there wasn't a market for it--it's exciting to see the underdogs picking up marketshare.