Softpedia >Windows >Programming >Components & Libraries >AlphaVSS >  Changelog

AlphaVSS Changelog

What's new in AlphaVSS 1.0 Beta

Apr 22, 2009
  • Most significantly the nasty assembly version bug is finally gone, and loading
  • of the platform specific assemblies should now work without a problem.
  • The other major difference is an update of the documentation which now also
  • include conceptual content (such as these release notes) and some basic usage guidelines to make getting started using AlphaVSS easier.
  • A couple of simple samples have also been included to demonstrate the basic usage of AlphaVSS.
  • An installer is provided for help integration with the Visual Studio 2008 help
  • system.

New in AlphaVSS 1.0 Alpha (Mar 21, 2009)

  • With version 1.0 Alpha the public interface of AlphaVSS should have stabilized somewhat, and no major changes will be made to the interface before 1.0 final is released unless required by a serious bug or flaw. Please report any usages, both successful and unsuccessful by posting a message at the discussion board or filing a work item in the Issue Tracker. This is vital if I should be able to release a Beta and Final releases in the near future.
  • Listed below are the most important new features in AlphaVSS version 1.0 alpha. For a full list, see ChangeLog.txt included in both the binary and source releases.
  • All VSS API classes that are platform specific are now exposed as interfaces instead of classes. The code common to all platforms have been extracted into a separate assembly called AlphaVSS.Common, which is written in C#, greatly reducing the maintenance workload.
  • Only one executable need to be produced for all platforms now. VssUtils and IVssImplementation provide the entry point to the VSS API, providing automatic detection of the operating system and loading of the correct dll and creating an instance of IVssImplementation which provide further methods to aquire the relevant VSS interfaces. See the API documentation for VssUtils for more information about this.
  • All of the VSS API (as of Windows SDK version 6.1) relevant to requesters should now be available for use in AlphaVSS.
  • Documentation has been updated and many erroneous links have been corrected.
  • All assemblies now have a strong name. This is used by the dynamic loading facility, but may cause problems when you build AlphaVSS from source. See Building AlphaVSS from Source for more information.
  • Target framework for AlphaVSS was changed to .NET 2.0 since it doesn't use any of the features introduced in the later framework versions.