Do NOT use pointers in managed code (unsafe code). There is no reason to use this, though there are acceptable reasons for performance like when manipulating pixels. out ulong is already serving the role of a pointer, too. out ulong* with an unsafe context would actually be more like unsigned long** in native code. You should read Marshaling Data with Platform Invoke[^] in the .NET Framework SDK to gain a better understanding of how native types translate to managed types. You can also visit http://pinvoke.net[^] for signatures to many common APIs. You should also refrain from using undocumented APIs because they can be changed without warning, not to mention that they are not officially documented by Microsoft. There are better ways to gain compression in .NET, including class libraries that implement compression without resorting to P/Invoke, which means your applications that use such libraries are more likely to be portable to other platforms. One popular compression library is SharpZipLib[^] but you can search for many more. This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles] [My Blog]

See the SDK documentation for IMAGE_FILE_HEADER. This reveals that the field is a 32-bit integer representing the number of seconds since 1 January 1970 00:00:00. Probably the easiest way to handle it is to construct a DateTime representing that date, then use AddSeconds. Stability. What an interesting concept. -- Chris Maunder

No, timestamps are not in hex. Hexadecimal is only a numeric representation. They're a number and that's all. To actually be stored in hex would require storing a string, which I know is now the case. To convert numbers to a filetime, you can pass the number (a long, or Int64) to either of the static DateTime.FromFileTime or DateTime.FromFileTimeUtc methods. In your case, you'll want to use DateTime.FromFileTimeUtc since timestamps are specified in UTC (+0 GMT). This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles] [My Blog]

Hi, what you want to do is called serialization. Serialization is saving an object's state to a stream so its state can be transported or saved and later restored. You suggested a tab separated text file, which is nice since the file is easily read and understood by other applications, however binary files are faster. If format don't mattter to you, I would suggest binary format. BinaryFormatter.Serialize Method is the method you use for binary serialization. The problem will be for you that a listview control or ListViewItemCollection object do not support serialization. To be able to serialize an object, the object's class needs to be either marked with the Serializable attribute or implement the ISerializable interface. The class ArrayList however is marked Serializable attribute and it's pretty easy to construct an arraylist from a listview control. Good luck and feel free to check my C# blog, Patric

leppie wrote: just click search Be careful, someone it apt to claim they didn't get the results they wanted by simply clicking 'search'. :rolleyes: - Nick Parker My Blog | My Articles

I've answered your questions because this is for educational purposes, and also because knowing these things does not in fact allow the "attack" of the signed assembly. To verify the assembly's digital signature, the CLR uses the assembly's public key to decrypt the assembly's digital signature, resulting in the original, calculated hash. In addition, the CLR uses the information in the assembly's manifest to dynamically generate a hash. This hash value is then compared with the original hash value. These values must match, or we must assume that someone has tampered with the assembly. - from .NET Framework Essentials, By Hoang Lam, Thuan L. Thai. my blog

yep, i'd read an article to work out re-signing, but the public key changes, and what i need, is not changing the public key

from ShlObj.h #define CSIDL_RESOURCES 0x0038 // Resource Direcotry "No matter where you go, there your are." - Buckaroo Banzai -pete

well, i think some of the functions are native, and that's the prob

[sarcasm]Want to borrow my claws ?[/sarcasm] :laugh: The tigress is here :-D

Hi, From VB you can use ZOrder, MyForm.ZOrder 0 will send the form to the top of the z order MyForm.ZOrder 1 will send it to the bottom of the z order If you are looking for more control, check SetWindowPos API function, BOOL SetWindowPos( HWND hWnd, // handle to window HWND hWndInsertAfter, // placement-order handle int X, // horizontal position int Y, // vertical position int cx, // width int cy, // height UINT uFlags // window-positioning options ); where hWndInsertAfter is a handle to the window to precede the positioned window in the Z order or one of the following values. HWND_BOTTOM HWND_NOTOPMOST HWND_TOP HWND_TOPMOST Check the MSDN for a detailed explanation. Fabian