I am using "CreateCSharpAssemblyInfo" function of FAKE for updating AssemblyInfo.cs.
But I am getting error , i.e.
2) CS0579: Properties\AssemblyInfo.cs: Duplicate 'AssemblyProductAttribute' attribute
3) CS0579: Properties\AssemblyInfo.cs: Duplicate 'AssemblyCompanyAttribute' attribute
4) CS0579: Properties\AssemblyInfo.cs: Duplicate 'AssemblyCopyrightAttribute' attribute
5) CS0579: Properties\AssemblyInfo.cs: Duplicate 'AssemblyVersionAttribute' attribute
6) CS0579: Properties\AssemblyInfo.cs: Duplicate 'AssemblyFileVersionAttribute' attribute
here is the code that I am using :
let assemblyInfo = [
Attribute.Title "My Project"
Attribute.Product "My Product"
Attribute.Company "XYZ"
Attribute.Copyright "Copyright XYZ"
Attribute.Version "14.8"
Attribute.FileVersion "13.9"
]
Target "BuildApp" (fun _ ->
CreateCSharpAssemblyInfo "./Source Code/Project/Properties/AssemblyInfo.cs" assemblyInfo
!! "/Source Code/Project.sln"
|> MSBuildReleaseExt buildDir [("SolutionDir", currentPath ## "\BuildTools")] "Build"
|> Log "AppBuild-Output:"
)
I am not getting the reason of this error .
I'm new to FAKE and have not used F# much, so forgive me if this should be obvious.
If anyone can help , that would be really helpful.
Have you tried the CreateCSharpAssemblyInfoWithConfigargument? It allows for an additional parameter:
CreateCSharpAssemblyInfoWithConfig
assemblyInfoFile
attributes
(AssemblyInfoFileConfig(generateClass=false))
Alternatively, the UpdateAttribute would do a similar thing (in my case all developers work in Visual Studio and it is safe to assume default AssemblyInfo.cs files would be auto-generated).
From the doc:
Update a set of attributes in an AssemblyInfo file. Fails if any attribute is not found.
See below example:
Target "UpdateAssemblyInfo" (fun _ ->
let csProjectDirs =
!! "**/**/*.csproj"
|> Seq.map (directory >> directoryInfo)
let attributes =
[
Attribute.Title "My Project"
Attribute.Product "My Product"
Attribute.Company "XYZ"
Attribute.Copyright "Copyright XYZ"
]
let applyAssemblyInfo (projDir:DirectoryInfo) =
let assemblyInfoFile = projDir.FullName ## "Properties/AssemblyInfo.cs"
clearReadOnly assemblyInfoFile
UpdateAttributes
assemblyInfoFile
attributes
csProjectDirs |> Seq.iter applyAssemblyInfo
)
Related
I am very new to FAKE. I use the following code (based on the official FAKE example) to build some F# project:
Target.create "BuildApp" (fun _ ->
[ p.buildTarget ]
|> MSBuild.runRelease id buildDir "Build"
|> Trace.logItems "AppBuild-Output: "
)
Everything is great except that it builds a 32-bit application, while I explicitly need a 64-bit one (with <gcAllowVeryLargeObjects enabled="true" />, of course) as otherwise it would not make a dent. This answer: FAKE: How to define MSBuild properties? seems to reference FAKE 4 but it looks that I have FAKE 5.
How can I tell FAKE 5 to build a 64-bit application? Thanks a lot!
You can set properties by supplying a setParams function other than id to MSBuild.runRelease:
Target.create "BuildApp" (fun _ ->
[ p.buildTarget ]
|> MSBuild.runRelease (fun p ->
{ p with Properties = [ "platform", "x64" ] } ) buildDir "Build"
|> Trace.logItems "AppBuild-Output: "
EDITED to show the ignore return as pointed out by Fyodor and the resulting error
I have a .fsx file with several targets that work as expected, but I can't get a target for OpenCover to work. This is what I have for the Target code:
Target "Coverage" (fun _ ->
OpenCover
(fun p -> { p with ExePath = "./packages/OpenCover.4.6.519/tools/OpenCover.Console.exe"
TestRunnerExePath = "./packages/Machine.Specifications.Runner.Console.0.10.0-Unstable0005/tools/mspec-clr4.exe"
Output = reportDir + "MspecOutput.xml"
Register = "-register:user"
}
)
testDir ## "FakeTest2UnitTesting.dll" + "--xml " + reportDir + "MspecOutput.xml" |> ignore
)
But I now get the following build error:
build.fsx(45,3): error FS0039: The value or constructor 'OpenCover' is not defined. Maybe you want one of the following:
OpenCoverHelper
NCover
I don't know what I am doing wrong. Can someone show me how to use the OpenCoverHelper from the FAKE API?
Thanks
After a lot of playing around an googling, I finally came up with the solution. The basic problem was that I didn't open the OpenCoverHelper. I made the assumption that it was included in FAKE as it is in the Api and there was no documentation saying anything else. So, here is the code I use:
// include Fake lib
#r #"packages/FAKE.4.61.2/tools/FakeLib.dll"
open Fake
open Fake.OpenCoverHelper
Target "Coverage" (fun _ ->
OpenCover (fun p -> { p with
ExePath = "./packages/OpenCover.4.6.519/tools/OpenCover.Console.exe"
TestRunnerExePath = "./packages/Machine.Specifications.Runner.Console.0.10.0-Unstable0005/tools/mspec-clr4.exe"
Output = "./report/MspecOutput.xml"
Register = RegisterUser
})
"./test/FakeTest2UnitTesting.dll + --xml ./report/MspecOutput.xml"
)
Hopefully this will help someone in the future.
my question is the following:
When I try to install my Windows Service I get the following error:
snippet:
...
No public installers with the RunInstallerAttribute.Yes attribute could be found in the <path to exe> assembly.
...
I follow this tutorial
I have one Program.fs file containing:
[<RunInstaller(true)>]
type public FSharpServiceInstaller() =
inherit Installer()
do
< some logic, doesn't really matter >
This should be sufficient, as a matter of fact, I don't even think I need to add the public keyword to the type definition. Installing this executable with InstallUtil.exe gives me the same error as installing it using the following code:
[<EntryPoint>]
let main args =
if Environment.UserInteractive then
let parameter = String.Concat(args);
match parameter with
| "-i" -> ManagedInstallerClass.InstallHelper [| Assembly.GetExecutingAssembly().Location |]
| "-u" -> ManagedInstallerClass.InstallHelper [| "/u"; Assembly.GetExecutingAssembly().Location |]
| _ -> printf "Not allowed!\n"
else
ServiceBase.Run [| new CreditToolsService() :> ServiceBase |];
0
I have tried running this script in PowerShell, cmd and Visual Studio CLI as both administrator and my normal account but I keep getting the same error. If anyone knows what I'm doing wrong I would really appreciate some help.
OK, so here goes...
I've looked at the code provided by user1758475 and just randomly started copy pasting solutions into an application. Don Symes's solution "just worked" and I finally figured out why: I did not (and he does) have a namespace declaration, in my source. Seems like this was the culprit! After I added the namespace the installer worked like a charm.
As Curt Nichols pointed out, the installer should not be in a module because a module effectively hides the type from the calling code.
Thank you for help in figuring this out.
For those of you who want to see a working example:
namespace FileWatcher
open System
open System.Reflection
open System.ComponentModel
open System.Configuration.Install
open System.ServiceProcess
open System.IO
open System.Configuration
type FileWatcherService() =
inherit ServiceBase(ServiceName = "FileWatcher")
let createEvent = fun (args: FileSystemEventArgs) ->
printf "%s has been %s\n" args.FullPath (args.ChangeType.ToString().ToLower())
|> ignore
override x.OnStart(args) =
let fsw = new FileSystemWatcher ()
fsw.Path <- "C:\TEMP"
fsw.NotifyFilter <- NotifyFilters.LastAccess ||| NotifyFilters.LastWrite ||| NotifyFilters.FileName ||| NotifyFilters.DirectoryName ||| NotifyFilters.CreationTime
fsw.Filter <- "*.txt"
fsw.EnableRaisingEvents <- true
fsw.IncludeSubdirectories <- true
fsw.Created.Add(createEvent)
override x.OnStop() =
printf "Stopping the FileWatcher service"
[<RunInstaller(true)>]
type public FSharpServiceInstaller() =
inherit Installer()
do
// Specify properties of the hosting process
new ServiceProcessInstaller
(Account = ServiceAccount.LocalSystem)
|> base.Installers.Add |> ignore
// Specify properties of the service running inside the process
new ServiceInstaller
( DisplayName = "AAA FileWatcher Service",
ServiceName = "AAAFileWatcherService",
StartType = ServiceStartMode.Automatic )
|> base.Installers.Add |> ignore
module Program =
[<EntryPoint>]
let main args =
printf "starting the application...\n"
if Environment.UserInteractive then
let parameter = String.Concat(args);
match parameter with
| "-i" -> ManagedInstallerClass.InstallHelper [| Assembly.GetExecutingAssembly().Location |]
| "-u" -> ManagedInstallerClass.InstallHelper [| "/u"; Assembly.GetExecutingAssembly().Location |]
| _ -> printf "Not allowed!\n"
else
ServiceBase.Run [| new FileWatcherService() :> ServiceBase |];
0
Working live production example at https://github.com/zbilbo/TB4TG/blob/master/TourneyBot.Service/Installer.fs
Think it needs to be installed with InstallUtil.exe though.
Possibly not the finest moment in coding, but that specific service code is from Don Syme more or less: http://blogs.msdn.com/b/dsyme/archive/2011/05/31/a-simple-windows-service-template-for-f.aspx, so it is probably fine, but the rest of the "surrounding" code on that repository may not be idiomatic ;-)
Don Symes blog also explains a lot more so it should be easily to adept it to your needs. It also links to a Win Service Template on VS Gallery: http://blogs.msdn.com/b/mcsuksoldev/archive/2011/05/31/f-windows-application-template-for-windows-service.aspx
Is it possible to add a description to this target? Or would I have to go about it another way?
Target "Test" (fun _ ->
trace "Testing stuff..."
)
Edit:
TargetHelper allows for the description to be shown when listTargets() is called.
At least, that's my understanding from the code here:
https://github.com/fsharp/FAKE/blob/master/src/app/FakeLib/TargetHelper.fs#L360-L365
If you just want to make your build script readable, you can add a comment in the normal F# way:
// Tests some stuff
Target "Test" (fun _ ->
trace "Testing stuff..."
)
As far as I know, there isn't anything built-in for adding descriptions to your targets in FAKE, but the nice thing about FAKE is that it is just an F# library, and so it is very customizable.
Here is one thing you could do - define your own function that wraps Target, but takes an additional description and builds a "Help" target with the descriptions automatically:
// The 'TargetDescr' function calls 'Target', but stores the description
let Description = System.Text.StringBuilder("Usage:\n")
let TargetDescr name comment f =
Description.AppendFormat(" * {0} - {1}\n", name, comment) |> ignore
Target name f
// Now you can define targets using 'TargetDescr' and get help page for free!
TargetDescr "Test" "Tests some stuff..." (fun _ ->
trace "Testing stuff..."
)
TargetDescr "Help" "Displays this help" (fun _ ->
printfn "%O" Description
)
How do I tell FAKE to compile a .fs file using fsc?
Bonus points for explaining how to also pass arguments like -a and -target:dll.
EDIT: I should clarify that I'm trying to do this without having an MSBuild/xbuild/.sln file. In other words, I want FAKE to fully take the place of MSBuild/xbuild.
FAKE has tasks to directly invoke the F# compiler. Usually you can use the Fsc task. If you want a target to compile an F# source file MyFile.fs to MyFile.exe, you can do:
Target "MyFile.exe" (fun _ ->
["MyFile.fs"]
|> Fsc (fun ps -> ps))
The Fsc task lets you compile multiple source files and specify every F# compile parameter. This simple example doesn't do that, but you can. To read up on the details, head over to the tutorial.
I recommend you read Ian Battersby's page on FAKE make on this topic
Code Excerpt:
first:
#!/bin/bash
TARGET=$1
BUILDTARGETS=$2
if [ -z "$BUILDTARGETS" ]
then
BUILDTARGETS="/Library/Frameworks/Mono.framework/Libraries/mono/xbuild/Microsoft/VisualStudio/v9.0"
fi
if [ -z "$TARGET" ]
then
CTARGET="Default"
else
CTARGET=`echo ${TARGET:0:1} | tr "[:lower:]" "[:upper:]"``echo ${TARGET:1} | tr "[:upper:]" "[:lower:]"`
fi
if [ ! -d "$BUILDTARGETS" ]
then
echo "BuildTargets directory '${BUILDTARGETS}' does not exist."
exit $?
else
export BUILDTARGETS="$BUILDTARGETS"
fi
echo "Executing command: $CTARGET"
mono packages/FAKE.1.64.6/tools/Fake.exe build.fsx target=$CTARGET
then
#I #"packages/FAKE.1.64.6/tools"
#r "FakeLib.dll"
open Fake
let buildDir = #"./build/"
let testDir = #"./test"
let fxReferences = !! #"*/*.csproj"
let testReferences = !! #"Tests/**/*.csproj"
let buildTargets = environVarOrDefault "BUILDTARGETS" ""
Target "Clean" (fun _ ->
CleanDirs [buildDir; testDir]
)
Target "Build" (fun _ ->
MSBuild buildDir "Build" ["Configuration","Debug"; "VSToolsPath",buildTargets] fxReferences
|> Log "Build-Output: "
)
Target "BuildTest" (fun _ ->
MSBuildRelease testDir "Build" testReferences
|> Log "Test-Output: "
)
Target "Test" (fun _ ->
!! (testDir + #"/*.Tests.dll")
|> xUnit (fun p ->
{ p with
ShadowCopy = true;
HtmlOutput = true;
XmlOutput = true;
OutputDir = testDir })
)
"Clean"
==> "Build"
"Build"
==> "BuildTest"
Target "Default" DoNothing
RunParameterTargetOrDefault "target" "Default"
Here's a possibly-useful -- though admittedly small -- twist on Yawar's answer above, which might make it fit in a bit better with the other FAKE examples you're likely to encounter.
The Fsc helper function wants a string list of filenames, which is fine as far as it goes. But most examples use the !! operator to find files, which results in FileIncludes which happens not to be a string list. You can convert a FileIncludes to a string list suitable for feeding to Fsc with Seq.toList.
Just to be thorough, I also convert things to relative pathnames (possibly just a personal quirk).
So here's an example of searching for all *.fs files and compiling them with some representative compiler options:
Target "BuildApp" (fun _ -> // Compile application source code
!! (srcApp ## #"**/*.fs") // Look for F# source files
|> Seq.map toRelativePath // Pathnames relative to current directory
|> Seq.toList // Convert FileIncludes to string list
|> Fsc (fun p -> // which is what the Fsc task wants
{p with // Fsc parameters: making an executable,
FscTarget = Exe // for any CPU, directing output to build
Platform = AnyCpu // area (both assembly & XML doc).
Output = ...exe file... // Executable generated
OtherParams = ["--doc:" + ...xmldoc file...) ]})
) //
As Yawar pointed out, there are a boatload of other compiler options covered in the tutorial.