http://msmvps.com/blogs/windrvr/archive/2007/05/27/crossing-the-undocumented-line.aspxAs a consultant who has more than once taken on projects Microsoft has said are impossible, many people assume I often use undocumented calls in Windows in my work. In fact, I try to avoid them if at all possible, and am extremely careful in crossingenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/windrvr/archive/2007/05/27/crossing-the-undocumented-line.aspx#932413Tue, 29 May 2007 16:27:04 GMTd67277c4-116b-43f1-b688-e9ef184ea916:932413Harry Tasker<p>&quot;As a consultant who has more than once taken on projects Microsoft has said are impossible, &quot;</p> <p>This is interesting - a few questions though:</p> <p>Did Microsoft say the entire project was impossible or part of the technique it&#39;s based on? e.g. Did they say you just cannot have a product like this work reliably on Windows OR You cannot make this product work reliably using this-technique-you-mention because it&#39;s undocumented (and the using the documented way won&#39;t give you the required benefit - e.g. performance - etc.? </p> <p>In other words, was it because Microsoft didn&#39;t want to bless the usage of undocumented calls or was it because Microsoft guys didn&#39;t think of the technique you used as a viable approach for that project? </p> <p>Can you also blog about how you perform the test in such cases? Do you consider all the combinations with various service packs and updates? I&#39;ve seen that some updates combinations can break something especially if the administrators don&#39;t issue &#39;recommended&#39; updates, but only install &#39;security&#39; / &#39;vulnerability&#39; updates. </p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=932413" width="1" height="1">