From: Tomasz P. <tom...@gm...> - 2013-04-16 20:31:19
|
Hi Rob, Kal I have been able to force TeamCity to build dotNetRDF with relatively minimal changes. Please refer to my fork [1]. I have switched from MSTest to NUnit and done some minor changes to csproj files. There is also a proposal to change the integration tests to come out inconclusive instead of failed when test config is missing... Most noteworthy is the latest commit in the 'WP7 Hack' branch. Unfortunately I found out the hard way that Windows Phone SDK 7.1 is not only unsuppported on Windows Server 2008 R2, it is completely uninstallable! The only working solution I found was to stuff 14 MB of WP7 SDK files and build targets and have the WindowsPhone project use them instead of the defaults. This way the whole solution builds fine from sln file using msbuild. You can have a look at the project here: http://ci.t-code.pl (guest login enabled) Regarding your eariler emails, I think that version numbering should be moved from solution to TeamCity completely. This way we can flexibly control that number and pass it between build steps/configurations. Next step will be to build and publish nuget packages. Satisfying dependencies between packages will have to be done in some kind of nuspec patching step to modify the <dependency> tags. Hence why we need to control the version withing the CI server. I will write more when the TC configuration is more complete Tom [1]: https://bitbucket.org/tpluscode/dotnetrdf-teamcity |