Version 1.5.2 Final Release???

Ok, I have found 1 final bug. The Environment.UserName returns an extra character. So I've had to update the release and it is available at Source Forge.

No new functionality has been added, simply a minor fix.

Kelly

Version 1.5.1 A Small Release

Version 1.5.1 has been posted on Source Forge. This release fixes 3 minor problems that most likely won't cause any problems if you are just using version 1.5. But, I like to post updates.

Kelly

Version 1.5 Finally!

Ok, I have finally release version 1.5, that is all.


Ok ok, this is another massive release. There are lots of new classes, especially in the resources department. There are a few other classes aswell. Some classes have been upgraded and fixed.

I've even included example projects that demonstrate various aspects of the library! Check 'em out!

-Kelly

All About the Resources

Ok, I've got .RES files being read and written. The default support is for String, Icon, IconGroup, Cursor, CursorGroup, Bitmap and Byte arrays. The readers and writers accept custom decoders and encoders to easily extend the RES data supported.

Also, reading from EXE, DLL, and OCX's resources has been updated to work like reading a .RES file.

I've been investigating writing resources back into executable files and it seems that it could be quite easy to screw things up, so I'm not convinced I should include the ability to write to those types of files.

-Kelly

Just When I Though It Was Over

Ok, I haven't released anything yet. I have figured out how to create the .RES files now, so I have been rebuilding the Resource area from the ground up. It now supports the ability to be extended to allow for new resource types to be decoded from the .RES file without the need for updating VBCorLib. On the same token, encoding will work the same way.

Classes can implement the IResourceDecoder or IResourceEncoder to read and write to a .RES file. Right now there are decoders for bitmap, icons, cursors, group icons, group cursors and string tables. I will write encoders for those types and that should be enough to cover 99% of everything. For resources that aren't supported, they are still read and written as byte arrays.

The enumeration is robust in that each resource now has a unique key, and each string in a string table is returned individually.

I'll implement the same functionality when dealing with resources in executable files also. Reading is supported on all systems, but writing seems to be supported on only NT machines.

Off I go..

Kelly

Close To Release

Ok, version 1.5 is basically ready. I'm just checking things over. There are about 10 examples demonstrating various functionalities within VBCorLib. The examples are far from exhaustive in showing all the capabilities of the library, but it will help get an idea on how to utilize VBCorLib.

- Kelly