What is the difference in a P/Invoke signature between “byref byte” and “byte[]”?http://blogs.msdn.com/joshwil/archive/2005/08/10/450200.aspxLately we’ve seen a spate of issues coming up on 64-bit platforms within the Developer Division around usages of P/Invoke signatures which declare a parameter as type “byref byte” where the developer really means “byte[]” (the corresponding native parameteren-USCommunityServer 2.1 SP1 (Build: 61025.2)re: What is the difference in a P/Invoke signature between “byref byte” and “byte[]”?http://blogs.msdn.com/joshwil/archive/2005/08/10/450200.aspx#450421Thu, 11 Aug 2005 18:19:53 GMT91d46819-8472-40ad-a661-2c78acb4018c:450421Frank HilemanYour recent posts are very useful! Would it not be so much work for someone at Microsoft to create an VS add-in that performed the following: the user selects from a list of win32 methods, the add-in pulls a Correct PInvoke decl from some safe online database (not the frequently vandalized wiki) and sticks it in a file dedicated to PInvoke decls. PInvoke is quite common and errors are just as common.Marshal opaque structs as IntPtr instead of Byte[]http://blogs.msdn.com/joshwil/archive/2005/08/10/450200.aspx#1169716Wed, 29 Nov 2006 08:26:04 GMT91d46819-8472-40ad-a661-2c78acb4018c:1169716Mike Stall's .NET Debugging Blog<p>If you have an opaque native structure that you want to pass through managed code, consider using IntPtr,</p> GetPrinter Call in x64 caused a FatalExecutionEngineError expectio | keyongtechhttp://blogs.msdn.com/joshwil/archive/2005/08/10/450200.aspx#9364485Thu, 22 Jan 2009 10:56:13 GMT91d46819-8472-40ad-a661-2c78acb4018c:9364485GetPrinter Call in x64 caused a FatalExecutionEngineError expectio | keyongtech<p>PingBack from <a rel="nofollow" target="_new" href="http://www.keyongtech.com/452072-getprinter-call-in-x64-caused">http://www.keyongtech.com/452072-getprinter-call-in-x64-caused</a></p>