e.g.

http://blog.michaelkc.dk/sourcegear-vault-35-nant-tasks-converted-to-msbuild/

The download link no longer works (404 error), but is seems that a lot of time has passed since then and perhaps it was a failed experiment?

If you had some reasonable success but lost interest I’d love to pick up where you left off.

Regards,

Jason
Auckland
New Zealand

The only problem is that when doing a very long get I get this error message inside the debugger.

Managed Debugging Assistant ‘ContextSwitchDeadlock’ has detected a problem in ‘C:\Development\{Tools}\{Builder} 1.0\Source\{WinForms}\bin\Debug\Builder.vshost.exe’.
Additional Information: The CLR has been unable to transition from COM context 0×1a26c0 to COM context 0×1a2830 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

However I think I could probably turn that message off if I cared and it only appears when run from inside the debugger.

thanks again – saved our bacon for the build scripts.

- Greg

If you do SharePoint development you tend to run IISRESET a great deal each time you deploy new webpart…