article

How to make sure your project is compliant with all windows operating systems

Email
Submitted on: 2/9/2015 12:23:00 PM
By: Thomas Swift (from psc cd)  
Level: Beginner
User Rating: By 3 Users
Compatibility: VB 3.0, VB 4.0 (16-bit), VB 4.0 (32-bit), VB 5.0, VB 6.0
Views: 414
 
     How to make sure your project is compliant with all windows operating systems.

 
				

The most important factor of knowing that your project is compliant is API. Before publishing you particular project be sure to go to MSDN at Microsoft & cross reference all your API calls. At the bottom of each API description page at MSDN is a list that shows what operating systems that particular API call is valid on. It is OK to implement both if you use a operating system detection API to fire or not to fire the correct API for the detected operating system.

The second factor is null filtering on NT operating systems. Be sure to debug your application on either windows 2000 or XP to find out if any of your code generates any null characters when returning data. Null characters are indicated by a empty square box or boxes in your string data. If null characters do exist be sure to use a null filter in those areas of your code. Windows NT operating systems are famous for generating null characters. This is why most programmers now days either work in windows 2000 or XP.

Their you have it, its as simple as that !!!


Other 27 submission(s) by this author

 


Report Bad Submission
Use this form to tell us if this entry should be deleted (i.e contains no code, is a virus, etc.).
This submission should be removed because:

Your Vote

What do you think of this article (in the Beginner category)?
(The article with your highest vote will win this month's coding contest!)
Excellent  Good  Average  Below Average  Poor (See voting log ...)
 

Other User Comments


 There are no comments on this submission.
 

Add Your Feedback
Your feedback will be posted below and an email sent to the author. Please remember that the author was kind enough to share this with you, so any criticisms must be stated politely, or they will be deleted. (For feedback not related to this particular article, please click here instead.)
 

To post feedback, first please login.