I will try to improve this in next version so that you don't have to enter locations if they are at the default locations
you might encounter one issue depending on which approach you will take
@mzorec OK, will try it.
I mean I'll try GitVersion.
or set it BuildTask
explicitly
context.CreateTarget("Build")
.AddCoreTask(x => x.Build().FileVersion());
.AddCoreTask(x => x.Build().FileVersion());
if you take this approach i recomend that you do it in this way:
public GitVersion Version { get; set; }
protected override void BeforeBuildExecution(ITaskContext context)
{
Version = context.Tasks().GitVersionTask().Execute(context);
}
protected override void ConfigureTargets(ITaskContext context)
{
context.CreateTarget("test")
.AddCoreTask(x => x.Build().Version(Version.SemVer));
}
this will be simplified in FlubuCore 5.0
which will be released shortly
Does FlubuCore depend on GitVersion command line tool?
Thanks very much for your help!public GitVersion Version { get; set; } protected override void BeforeBuildExecution(ITaskContext context) { Version = context.Tasks().GitVersionTask().Execute(context); } protected override void ConfigureTargets(ITaskContext context) { context.CreateTarget("test") .AddCoreTask(x => x.Build().Version(Version.SemVer)); }
Changelog with samples https://github.com/dotnetcore/FlubuCore/blob/master/CHANGELOG.md
yes sure it is possible
@Elron1179 if this is the case take a look at this example https://github.com/dotnetcore/FlubuCore.Examples/blob/master/MVC_NET4.61/BuildScripts/BuildScript.cs
and read the comment in ConfigureBuildProperties. Example adds target "Generate.commonassinfo" which generates common assembly information(more about common assembly information can be read for example here https://amido.com/blog/shared-assemblyinfo-dont-repeat-yourself/) for all projects in solution. Compile target then picks up this generated common assembly information file where version information is stored. Version information is set by "update.version" target.
and read the comment in ConfigureBuildProperties. Example adds target "Generate.commonassinfo" which generates common assembly information(more about common assembly information can be read for example here https://amido.com/blog/shared-assemblyinfo-dont-repeat-yourself/) for all projects in solution. Compile target then picks up this generated common assembly information file where version information is stored. Version information is set by "update.version" target.
or you have newer project files targeting .net framework?
thank you for your response.
yes, for the moment I still have to create my projects in .net. The switch to .net core was discussed but is not near yet.
I like the concept of FlubuCore, especially having the build process as a project in the solution.
Sadly for the moment I ran into some other problem, where I found infos for .net core, but not for .net and I just could not afford to put more time into recherche.
So for the moment, I had to hit the breaks and head back for cake.
As soon as I get the clearance to start migrating projects towards .net core, I will give FlubuCore a more serious attempt.
Btw: 'common assembly info'. never heard of that concept before but I really like it and will have a look into that.
So thanks again and I hope to see you in the future with a proper .net core build project.
yes, for the moment I still have to create my projects in .net. The switch to .net core was discussed but is not near yet.
I like the concept of FlubuCore, especially having the build process as a project in the solution.
Sadly for the moment I ran into some other problem, where I found infos for .net core, but not for .net and I just could not afford to put more time into recherche.
So for the moment, I had to hit the breaks and head back for cake.
As soon as I get the clearance to start migrating projects towards .net core, I will give FlubuCore a more serious attempt.
Btw: 'common assembly info'. never heard of that concept before but I really like it and will have a look into that.
So thanks again and I hope to see you in the future with a proper .net core build project.
@Elron1179 But even if you have to create projects for .net you can use new csprojs targeting old .net framework so you can use .net core cli and other new features
you can also use for example .net core mvc in .net full framework. We did this in our web APIs alot of times when something was not available in .net core then switched to .net core when we could.
If you do all this then the migration from .net to .net core is much easier