Originally posted by: Mike Hughes
This works great except that tab controls with tabs at the bottom appear as if they are at the top. Also , the background behind the control is painted transparently for some reason. I am using Dundas's version of the TabControl COX3DTabViewContainer which inherits from the windos tab control.
ReplyOriginally posted by: Andy E
When I call SQLManageDataSources to display the ODBC Administrator that dialog is now unusable. This must be a bug in the ODBC installer dll. Any thoughts?
ReplyOriginally posted by: jjsj
Your column is great, and saved me from losts of searching. Even so, I run into a problem (and the solution) worth to mention.
If you include a especial character in the manifest file (a character such as '�', '�', '�', '�', ...) XP will declare that '..the applicacion configuration is incorrect.'.
The only workaround I found is to supress those characters whatsoever or replacing them with the unicode rep ('á', 'é', ...). Changing the encoding of the manifest won't do. Microsoft, Microsoft, Microsoft.
Reply
Originally posted by: fetboy
my operation system is win2000
but when your application run under my computer,nothing happened.
i have changed "MyApplication" to "XPStyle.exe" in the file XPStyle.manifest
Reply
Originally posted by: Amn
I would like to correct the statement that "manifest is not technically a resource". This might lead people to believe they must carry the XML file along with the their product release distributions, which they dont, since the XML manifest is integrated into the executeable.
Otherwise, neat article. Spares a lot of time not to having to go through MSDN :) Which i did anyway ...
Reply