David Gardiner wrote:
> Although in my case, our solution doesn't have any C++ projects - just C#
>
Yep, the targets go through the same code path.
--
sig://boB
http://joyofsetup.com/
--
Register Now for Creativity
Although in my case, our solution doesn't have any C++ projects - just C#
2009/5/19 Bob Arnson
> David Gardiner wrote:
> > Adding the ToolsVersion attribute fixed the problem for me.
> >
>
> And it's definitely required if you want to use VC9 .vcproj files. But
> I'll fix it so you at least get
David Gardiner wrote:
> Adding the ToolsVersion attribute fixed the problem for me.
>
And it's definitely required if you want to use VC9 .vcproj files. But
I'll fix it so you at least get a better error message. Mostly, it boils
down to changes in MSBuild between releases of the .NET Framewo
Adding the ToolsVersion attribute fixed the problem for me.
thanks,
-dave
2009/5/18
> If you want to build the project, manually go in and set the ToolsVersion
> attribute to 3.5 of the Project tag in the votive project (.wixproj) file.
> This task is in MSBuild 3.5, not 2.0.
>
> I had the same
If you want to build the project, manually go in and set the ToolsVersion
attribute to 3.5 of the Project tag in the votive project (.wixproj) file.
This task is in MSBuild 3.5, not 2.0.
I had the same problem.
I tried to send the same message earlier, but Cox munched my email. I hope
this
David Gardiner wrote:
> At a guess, I'd say it might be related to the changes made for bug 2786736
>
Agreed. I reopened the bug. Can you attach a /v:diag log of a
command-line MSBuild run? I suspect MSBuildToolsVersion is a value I
didn't expect.
--
sig://boB
http://joyofsetup.com/
6 matches
Mail list logo