CANNOT run MSBuild 3.5 Projects

Hello, sorry for shouting but this is my third attempt at having an answer
to my problem.

To recap, if I save a working configuration that needs the 3.5 framework
to compile, TeamCity no longer compiles said configuration. I've found
what the problem is, in the project-config.xml that's being saved, TC is
not adding a to the ]]> element.

Is this a known problem? Maybe it is a problem with my configuration...any
ideas?

Many thanks,
Pablo

--


Of all thirty-six alternatives, ignoring it is best.

Pablo Montilla
www.odyssey.com.uy

6 comments
Comment actions Permalink

Pablo,
Could you please describe you case in more detail.
What version of TC is it?
What build runner is used?
Do you run build agent as windows service? What user account is used than?
Do you have .NET 2.0, .NET 3.5, VS 2005 or VS 2008 installed on build agent machine?
Please attach build log of the failure.

Thanks!

0
Comment actions Permalink

On Fri, 27 Mar 2009 06:04:54 -0300, Eugene Petrenko
<no_reply@jetbrains.com> wrote:

Pablo,
Could you please describe you case in more detail.
What version of TC is it?
What build runner is used?
Do you run build agent as windows service? What user account is used
than?
Do you have .NET 2.0, .NET 3.5, VS 2005 or VS 2008 installed on build
agent machine?
Please attach build log of the failure.

>

Thanks!

>

---
Original message URL:
http://www.jetbrains.net/devnet/message/5234425#5234425


Thank you for your answer!

- I'm using TC Professional 4.1 EAP (build 8804).
- The build runner is sln2008.
- Build Agent is running as a service on the SYSTEM account.
- I have .NET 3.5SP1 and VS 2008 installed in the build agent machine.
- Build log is attached.

If I force a save of a perfectly running configuration, I get a
non-working configuration. The only way to make it work again is by
editing it's project-config.xml file, and adding inside a ]]>.

Many thanks,
Pablo

--


I'd be willing to admit the possibility of a tornado, but it's not really
tornado season. I'd even be willing to entertain the notion of a black hole
passing over the area or some cosmic anomaly, but it's not really black
hole season either.
-- Fox Mulder, "Fearful Symmetry," The X-Files

Pablo Montilla
www.odyssey.com.uy

0
Comment actions Permalink

What do you change in project-config.xml?
Thanks!

0
Comment actions Permalink

On Mon, 30 Mar 2009 12:10:14 -0300, Eugene Petrenko
<no_reply@jetbrains.com> wrote:

What do you change in project-config.xml?
Thanks!

>

---
Original message URL:
http://www.jetbrains.net/devnet/message/5234701#5234701


I've attached two project configs, the one that's been saved by TC, and
the way I leave it to make it work.

Thanks for your time,
Pablo


--


Viva La Ramen Noodles!

Pablo Montilla
www.odyssey.com.uy

0
Comment actions Permalink

Hello,

I think i had the same problem than Pablo.

I'm using TeamCity Version 4.1 EAP (build 8804).

When configuring from scratch a build with sln2008 buildrunner, the project-config.xml seems to miss adding the <param name="msbuild_version" value="3.5" /> element... So, if the project is .NET 3.5, the build fails with:
"Solution file error MSB5014: File format version is not recognized. MSBuild can only read solution files between versions 7.0 and 9.0, inclusive." As it uses msbuild 2.0 (as seen in the build full log:)

...........  c:\TeamCity\buildAgent\bin\..\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MsBuildBootstrap.exe @xml C:\k3x\CI\v4_dev\Framework\K3.Framework.sln.teamcity.bootstrap.properties
TeamCity MSBuild bootstrap v4.1 Copyright (C) JetBrains s.r.o.
Start MSBuild...
'C:\Windows\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe' ......

Manually adding the element <param name="msbuild_version" value="3.5" /> to the run-parameters element of the build-type in project-config.xml fixes the problem.

Attached is the full log for the error when the msbuild_version param is missing.

Hope it helps



Attachment(s):
K3_Tools_DEV_Framework_6.log
0
Comment actions Permalink

I've created the issue for it at
http://www.jetbrains.net/tracker/issue2/TW-7722

Please watch/vote for it.
Thanks!

0

Please sign in to leave a comment.