-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jaeger exporter implementation #132
Changes from 1 commit
639cd23
6d37ed2
8e45715
86db023
dd4492b
0d872b4
6fd13b8
ac5561a
7b82349
5ec204c
01f4283
41c8151
82eddea
1098705
fcab9be
ba897aa
bbbcf47
fa5fbd8
9aaa138
ac65edf
645d444
c368e2e
93c845e
89840a2
c22d3db
010dd08
3a47d48
2d8401e
b831f6e
b6e3720
3b06692
3188066
f56e7e4
916f223
5f98892
1cc3e83
aff702e
e4f9b12
b4c5f5b
6ded7ba
8620491
b18f778
604e747
d4bd960
c8a706a
011cd04
4a4a592
0341811
e2030e7
940fce7
7a98559
9fa75eb
eb1b880
4408d98
4d27578
c333fb6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,8 +5,8 @@ | |
<TargetFrameworks Condition="$(OS) != 'Windows_NT'">netstandard2.0</TargetFrameworks> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
is not needed There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually, after removing this and compiling, the code fails in .net standard 2.0. I double checked and this is the same pattern we're using in all the other projects in the solution. Should we be doing something else? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Correction: it doesn't fail in .net standard 2.0, it fails on any non-windows machine that cannot host .net Framework 4.5. The build command sees all the target frameworks and attempts to build them all. Since Framework 4.5 is not available, the framework 4.5 part of the build fails. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sample output:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ok, i see, so you are building on Mac i guess and this protects your build. Sorry for misleading advice, please put it back. |
||
</PropertyGroup> | ||
|
||
<ItemGroup Condition="$(OS) == 'Windows_NT'"> | ||
<PackageReference Include="System.Net.Http" Version="4.3.4" /> | ||
<ItemGroup Condition="'$(TargetFramework)' == 'net46'"> | ||
<Reference Include="System.Net.Http" Version="4.3.4" /> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please remove version, it is not needed
|
||
</ItemGroup> | ||
|
||
</Project> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpicking here but I believe keeping the current value of
TargetFrameworks
and appending if condition is true makes a bit more sense:The reason being, when we add
netstandard2.1
, you just need to add to the topTargetFrameworks
/add only once.Although I'm not sure what's the reason to not compile for
net46
on non Windows. ReferenceAssemblies can be used for that. Tests can run on Mono.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was getting this error:
The "Microsoft.Build.Tasks.Git.LocateRepository" task failed unexpectedly.
I can't give you specifics right now, since I just realized that I left my external drive that contains my windows image at home. I'll update this note with a more detailed error when I get home.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here dotnet/sourcelink#107 they tell "SourceLink requires .NET Core 2.1.300."
Do you have it installed on your machine? this version or later? Can you please check?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, yeah, I actually checked that the first thing when I switched over to Windows.
I just finally figured it out. I didn't have Git installed on my Windows VM because I've been managing source control through my MacOS host. I didn't even catch this when tried to clone the repo, since I cloned it using Visual Studio 2019's "Clone or check out code" feature, and Visual Studio 2019 is able to clone without Git installed.
So, it may seem like a silly thing to add to the CONTRIBUTING.md, but we might want to add a line item to install the Git command line tools. Especially since Visual Studio 2019 can now interact with Git without the tools installed.