Compatibility with Windows XP
I have a private installation of all the dependencies in a private folder within my App.path and they are also registered from there.
The test of the pooding is in the eating, so may be I'll discover what there is to it when I actually port. But for now I know that my app is not tied down to any specific software vendor or any legacy software, nor is it OS specific (except for the alpha blending and layered windows and a few aspects on which NT based systems vary from the 9x systems such as it uses psapi.dll which has entry points that are not found in 9x in psapi but are found in kernel32 because 9x does not have psapi etc.) and since XP is an evolution of 2000, I think it should work. However, if some of you have burnt a finger at it, please caution me.
LOL - pooding
I pitty the fool, who has to live on mars
Sorry for the typo - pudding it was.
I **pitty** the fool...
I'm not calling you a fool Sathyaish, I'm making fun of George Bush's political stunt. Sorry if you took it the wrong way.
Yes pity is spelled wrong on purpose.
Really just thought that spelling of pudding was funny. Never saw it spelled that way before heh.
>I'm not calling you a fool Sathyaish, I'm making fun of George Bush's political stunt. Sorry if you took it the wrong way.
Well, I'm offended - take it back!!!
Just as soon as you take your troops back, George.
Dear Mr. President:
My favorite Dubya Joke:
Some things we ran into for a VB6 app originally built for NT was:
The registry entries is more of a network issue, and I've had to deal with that in the recent past for the same client. Now they have given all their users Power User rights so they will be able to use applications that shall be allowed to modify their registry.
You should be using late-binding for Office Automation. That way it will use whatever version of Office is installed.
Yes, I agree that late binding is the way to go. Makes things a lot easier. Still, I would test fullt and make sure all Office Automation constants work correctly.
Sathyaish, better security than giving all users power user rights is to install the compatibility template, which was designed precisely to allow users to run applications that needed to write to the registry.
"Somewhere in Texas, there is a village missing an idiot."
I have always wondered how a nation that produced edison, bill gates and all those nobel laureates can also produce george bush.
In the same way that the nation that produced Ghandi also produced idiots that are often at the brink of war with their neighbours.
... genetic and environmental diversity I guess. A friend of mine supports the idea that the proportion of idiots is constant across cultures.
Actually it was South Africa that produced Ghandi...
Or maybe England... It is hard to isolate a single element or experience that "makes" or "produces" a person. Anyway, the real question is: Is Gandhi compatible with Windows XP?
Regarding Office 2000 compatibility, just make sure that your project references the type library for the oldest version of Office that your application supports. (In your case, the Office 9.0 library for Office 2000 compatibility.) The later versions of the Office type library are backwards compatible to earlier versions, so an application developed for Office 2000 should work fine on Office XP and Office 2003.
yes, you do need to retest. office is mostly but not 100% backwards compabible. i'll also recomend late binding if you don't do version detection. there are some obscure cases where office will not work quite right even though the API hasn't changed. plus the version-dependent progids aren't always version-dependent (e.g. word.application.10 might actually start word 11)
I developed a MS Word interface for my company’s product 2-3 years ago using late biding. At the time my specs required the module to support Office97 and up. It still works without any problem with Office XP. You have to be careful though with the evolutionary behavior of certain methods (i.e. Open()). Since Office2000, this method opens a new document in what it looks like a new Word instance but in the fact is the same WinNT process. In the previous versions Word had a pure MDI look. Depending on your GUI, your user might be confused by this kind of differences.
Fog Creek Home