Skip to content
This repository was archived by the owner on Feb 12, 2023. It is now read-only.

GitLink.exe should in 'tools' folder instead of 'lib' #87

Closed
nobitagamer opened this issue Jun 22, 2016 · 7 comments
Closed

GitLink.exe should in 'tools' folder instead of 'lib' #87

nobitagamer opened this issue Jun 22, 2016 · 7 comments
Milestone

Comments

@nobitagamer
Copy link

In the latest version published on nuget.org the .exe file is inside 'lib' folder but the package i downloaded on 06/21/2016 it's in corrected 'tools' folder

@GeertvanHorrik
Copy link
Contributor

From what I remember at the time I wrote it, my logic was that via NuGet, you want to use as library (thus lib), from chocolatey it installs as a tool.

@dazinator
Copy link
Member

dazinator commented Jun 23, 2016

I use NuGet for tools packages quite a bit, I find it convenient for them to be in the solution directory and restored on package restore. It just helps me to keep builds isolated. Imho it would make more sense to have a tools package, as consuming GitLink.exe is probably the intention, rather than referencing the library. No harm in having an additional nuget package for the library though

@tpluscode
Copy link
Contributor

@dazinator It's sidestepping the issue, but if and only if you would consider using Paket instead of the default package manager, you'll be able to add Nugets to your solution without actually referring them in any project - true tools-only usage.

@GeertvanHorrik
Copy link
Contributor

It's now inside the build folder since GitLink directly integrations with msbuild.

@GeertvanHorrik GeertvanHorrik added this to the 3.0.0 milestone Jul 29, 2017
@dazinator
Copy link
Member

dazinator commented Jul 29, 2017

@GeertvanHorrik that's cool - does the build task run under dotnet core builds too? Is there a sample with it being used with the new vs2017 csproj format somewhere? Is it as simple as just adding a PackageRefernece or do you need to add a cli tools package reference?

@GeertvanHorrik
Copy link
Contributor

From the readme:


The simplest way to use GitLink is to install its NuGet package into your project.

Install-Package GitLink

Once installed, it automatically integrates with MSBuild to add source download instructions to your PDB.


I haven't tested against dotnet core just yet, but it depends whether you are using portable pdb's or not. For portable pdb support, this will be (or already is) in SourceLink. We're trying to combine efforts with the SourceLink team to come up with a single solution that works for all.

@dazinator
Copy link
Member

dazinator commented Jul 29, 2017

@GeertvanHorrik Cheers. If your msbuild task is built on the full desktop version of the msbuild assemblies (i.e if these references are the desktop version of msbuild: https://github.com/GitTools/GitLink/blob/develop/src/GitLinkTask/GitLinkTask.csproj#L53) then dotnet build won't work as the dotnet cli tooling (an the version of msbuild used) will complain that it can't load the task, as the assembly is not compatible with netcore.

I believe you have to build your task against the netstandard compatible msbuild assemblies - I.e: https://www.nuget.org/packages/Microsoft.Build.Framework/15.3.0-preview-000388-01

Easy way to see the problem, is to create a new project, add git link nugget package, then drop to the command line and dotnet build it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants