Any tips on building? about core HOT 9 CLOSED

Hi Mattias,

Thanks for your interest in WebSharper. I have just attempted to make the build simpler by coding MSBuild tasks to automatically download and reference Cecil dependencies, removing the need to use NuGet. Right now the fresh checkout of the repository builds for me by running MSBuild in the root directory (with F# and MSBuild extension pack installed).

Can you try to update and see if it works for you?

Thanks,

Anton

Original comment by: Anton Tayanovskyy

from core.

Hi Anton,

I've cloned the latest version, when running msbuild in the checkout directory as indicated I get the following error.

{{{

Microsoft (R) Build Engine Version 4.0.30319.1
[Microsoft .NET Framework, Version 4.0.30319.239]
Copyright (C) Microsoft Corporation 2007. All rights reserved.

Build started 01/02/2012 00:36:20.
Project "C:\Users\Andrew\dev\websharper\WebSharper.proj" on node 1 (default targets).
Project "C:\Users\Andrew\dev\websharper\WebSharper.proj" (1) is building "C:\Users\Andrew\dev\websharper\IntelliFactory.Formlet\IntelliFactory.Formlet.fsproj" (2) on node 1 (default targets).
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets(483,9): error : The OutputPath property is not set for project 'IntelliFactory.Formlet.fsproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='X64'. You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project. [C:\Users\Andrew\dev\websharper\IntelliFactory.Formlet\IntelliFactory.Formlet.fsproj]
Done Building Project "C:\Users\Andrew\dev\websharper\IntelliFactory.Formlet\IntelliFactory.Formlet.fsproj" (default targets) -- FAILED.
}}}

I'm wondering if this indicates that the MSBuild Extensions pack is not installed properly? I installed the latest ( Nov 2011 ) version from codeplex, using the x64 .NET 4.0 installer.

Thanks,
Andrew.

Original comment by: Andrew Marshall

from core.

Have resolved the above by specifying the platform property as 'AnyCPU'. Do you also have a dependency on the 'AjaxMin' task? I don't believe this is part of the extension pack.

Thanks,
Andrew.

Original comment by: Andrew Marshall

from core.

I'm getting as far as the missing AjaxMin task, too. :(

Original comment by: Anonymous

from core.

I found the MS Ajax Minifier 4, installed it and got a lot further before the build stopped.

AjaxMin: http://aspnet.codeplex.com/releases/view/40584

jquery-1.7.1.min.js was still missing in the IntelliFactory.WebSharper.JQuery project. I'm not sure if the MS AjaxMin was supposed to produce this file, but I just downloaded it from jquery.com and put it in the project.

JQuery-1.7.1.min.js: http://code.jquery.com/jquery-1.7.1.min.js

IT BUILT!

Original comment by: Anonymous

from core.

Indeed, MS Ajax Minifier is a build-time dependency. I added this to README.txt, together with a short instruction how to compile with Plaform=AnyCPU.

Anonymous, yes, the AJAX Minifier is intended to produce the .min.js files for jquery and other embedded resources. It seems to work for me on a clean build right now. Please open a new issue in the tracker if the problem persists. Thanks!

Original comment by: Anton Tayanovskyy

from core.

I had the opportunity to try building on a fresh clean machine with only VS2010 and VS11Preview installed.

I installed the wrong MSBuild Extensions first. I wasn't sure which of the 4 (4.0 vs 3.5 and x86 vs x64 (on a new x64 machine)). I was pretty sure it was the x86 ones since VS is 32-bit, but I also knew that the WS projects target the 3.5 framework, yet seem to be invoking the fsc.exe from 4.0. I should have installed all 4, but I wanted to know which it was really using. I did one, then tried to build from the command line. That created the build.tmp file in Lib, then the WebClient tasks failed. After that, since build.tmp existed, it didn't try to fetch the mono.cecil stuff ever again.

After I read the build files to understnad what went wrong, cleaned up my Lib folder, and installed the v4.0/x86 MSBuild Extensions things worked fine under VS2010 and VS11 both command line and in the IDEs.

I've updated the readme.markdown in my fork with a little more guidance on the MSBuild Ext stuff and I fixed the pathing and PowerShell command line syntax.

Original comment by: Michael Garnett

from core.

Thank you for the feedback, Michael. You convince me that the build needs more work, so I am reopening the ticket. It is tempting to give up and just commit the binaries instead of trying to work around having them, although BB and hg are not very good at handling those.

Original comment by: Anton Tayanovskyy

from core.

I have just simplified the build further by removing the requirement to install MSBuild Extensions and Ajax Minifier. I moved the dependency download logic to an F# script ./Build/Build.fsx and am invoking that from ./WebSharper.proj; since F# does the downloading MSBuild Extensions are no longer necessary, and Microsoft Ajax Minifier is downloaded and locally referenced from BB. Please re-open if there are any further problems with building. Thanks!

Original comment by: Anton Tayanovskyy

from core.