Two new versions of AlphaVSS released!

It has been a long time since AlphaVSS 1.0 Beta was first released. A little over two years to be precise. The original plan was of course to go from beta to final in a month or two, but for reasons I’ve rambled way too much about already that didn’t happen.

So it is now with great pleasure I release two new beta versions of AlphaVSS!

"Wait? What? Two new versions? Beta… again!?", I hear you ask. Well, the fact that they are still beta versions and no final version is simply due to the fact that quite a few things have changed in the source code and projects with the move to Visual Studio 2010, and I have not yet had the time to test everything thoroughly. After all, that is kind of what a beta version is there for. So I ask you to help me in this task and report any errors/bugs that you may find. Also, I want a better sample application for the final, and I have not had time to write that yet. And some of you have asked me to put up a release of the latest version because of all the hassles of building this library, so therefore I wanted to get it published as soon as possible.

So why two versions? Well, as it turns out using a mixed mode assembly (which the AlphaVss.Platform.* assemblies are) built for .NET 2.0 framework in a .NET 4.0 application is not as straightforward as one might have thought. It requires some special configuration in the App.config to work, but this have other implications as well which may not be desired. So the best way to solve that was simply to build AlphaVSS against .NET 4.0 instead. But I didn’t want to abandon anyone still using older .NET versions either, and managing to target both frameworks within the same solution just isn’t feasible, so therefore there are now two versions. 1.1 and 1.2.

They are built from more or less exactly the same source  code, so there should be no difference functionality-wise, the only difference is the target framework for which they are built.

The 1.1 version will be the last version made for the .NET 2.0 framework. All future development (except for bug-fixes) will be done for .NET 4.0, i.e. on the 1.2 code base.

Anyway, I hope you find use for this and that you help out by reporting any bugs you find. 

I promise that I will do my best to make these versions go final within a couple of months at the latest.

What’s new?

  • AlphaVSS is now built using Visual Studio 2010 (together with Visual Studio 2008 for version 1.1). This doesn’t affect anyone using the library very much, but it feels really good to have gotten that conversion done and tidying up quite a few things in the project management area.
  • Some bug-fixes of course. Not that many since not very many bugs have been found that could be reproduced and traced back to AlphaVSS. (The VSS API’s are not straightforward to use so it’s quite easy to get things wrong and mess up when trying to code against these API’s).
  • Most classes in AlphaVSS are now marked as Serializable.
  • The DLL-files have a new naming scheme, see the documentation for more details.
  • Several new interfaces and methods introduced in Windows 7 and Windows Server 2008 R2 have been added.
  • AlphaVSS version 1.2 is built targeting the .NET 4.0 framework, simplifying and enhancing the use of AlphaVSS in a .NET 4.0 application.

And as always the latest releases and source code of AlphaVSS are available at http://alphavss.codeplex.com/

5 Comments

  1. @Alessandro: Thanks for letting me know. Looks like a good piece of work. It is always nice to get to hear when your projects get used! :)

    1. Windows Live Mail does indeed use the .eml frmaot. Even though Emailchemy doesn’t have Windows Live Mail listed as a supported frmaot (yet), it can convert this to Thunderbird folders. Try this: using the conversion wizard, select RFC-2822 Message Folders in step 1, then select the Local Folders folder found inside the Windows Mail data folder. Convert this to Thunderbird mail folder and then copy the resulting files to the Thunderbird Mail/Local Folders folder. Email me if you need more help.

  2. Would it be possible to use this library to quiesce a SQL Server database in order to do a storage level snapshot of a volume?

  3. Hey, I just wanted to thank you for authoring/sharing such awesome libraries! I was just about to start writing a .NET wrapper for TxF, but I fortunately found your project (way, way down at the bottom of google, unfortunately). I hope to give a spin here in a little while!

    Congrats on the new releases – keep’em comin’!

    Cheers!
    -Charles

Comments are closed.