wspbuilder on windows 2008 server

Aug 22, 2008 at 1:35 PM
I am trying to use the wspbulder on windows 2008 server 64 bit.  I downloaded the latest version and replaced the cablib with the 64 bit version.  However, the build seems to simply consume memory until the program crashes (about 10 mins).  Is there any known issues with 2008 server.

Any troubleshooting tips will be helpful.


Aug 27, 2008 at 9:01 AM
I'm also using WSPBuilder on a windows 2003 server. With Visual studio 2008 service pack 1. I see the same behaviour as you. I can see by studying the process in taskmanger that WSPBuilder consume all the memory it can. For me it goes from 0 kb to around 620Mb before it finish its job. However it do not crash.
Aug 28, 2008 at 12:16 AM
The version should fix the problem with the memory.
Aug 28, 2008 at 3:07 AM
I downloaded the new version. and here is the behavior I am experiencing.
I have a wspbuilder project that copies all files form the different projects in the solution to the logical locations and then wspbuilder is called as part of the post build event.
When I run wspbuilder from a command prompt it takes about 7 mins to complete the operation, however, when running it as part of the post build the program crashes.  What I got from the event viewer is not that helpful but here is what i got.

Faulting application WSPBuilder.exe, version, time stamp 0x48b5b068, faulting module MSVCR80.dll, version 8.0.50727.1434, time stamp 0x475772d1, exception code 0xc000000d, fault offset 0x000000000002a133, process id 0x11d4, application start time 0x01c908af89ac6c47.

The memory problem does seem to be resolved in the intial stages.