This is a great and easy-to-use tool. I assume that Cablib.dll creates a cab file (wsp file). I added the command to call wspbuilder in the post-build event, and Cablib.dll for x64 systems works
fine in development. However, I have a deployment / build issue, I am developing on a 64 bit server, but the code is built on a 32 bit server. And our SharePoint target servers will be both 32 and 64 bit systems.
I am wondering if wspbuilder could just use one version of cablib.dll that will work for both system types instead of keeping renaming / copying the dll depending on the operating system. Since
VS makecab.exe generates a standard cab file, could cablib.dll do the same thing?
Any suggestions how I can deal with this?