StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POContinuous Integration with 64-bit Sharepoint and TFS 2008?
text
Body
copied!<p>I've set up a 64-bit TFS 2008 build server with Sharepoint, continuous integration and out-of-the-box MSTest. Unit tests for plain business logic classes run just fine and test results are published into TFS. However, any test that uses Sharepoint's API fails horribly, <code>SPFarm.Local</code> returning null and so on. Is there a way to fix this?</p> <p>The tests run fine in an otherwise identical 32-bit development environment (Windows Server 2008 under Hyper-V, Sharepoint patched up to June 2009 cumulative update) from both Visual Studio and command line, so the problem is not about improper use of <code>SPContext.Current</code> or any other part of the API that needs to be run in a web server context. I've ruled out <a href="http://brandonpotter.wordpress.com/2009/02/10/spfarmlocal-is-null-what/" rel="nofollow noreferrer">permissions issues</a>, because the build agent account can deploy the solution and create site collections just fine with stsadm. The next culprit could be that the unit tests were being run with a <a href="http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/1f8d82af-7895-4f51-bd17-f53b443123eb" rel="nofollow noreferrer">32-bit process</a>, which couldn't access the 64-bit Sharepoint API properly. I tried <a href="http://blogs.msdn.com/danielvl/archive/2009/03/28/run-mstest-exe-as-native-64-bit-process.aspx" rel="nofollow noreferrer">a workaround</a>, but it has the side effect of disabling TFS support in MSTest.</p> <p>Do I have to wait for 2010 versions of MS tools (and hope for the best) or is there a third-party test framework available that runs natively in 64 bit and can publish test results into TFS 2008?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload