Skip to main content

corefx missing dependencies

EXEC : error : DIA SDK is missing at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\DIA SDK". Make sure you selected the correct dependencies when installing Visual Studio. [C:\w\corefx\src\Native\build-native.proj]
  Visual Studio Express does not include the DIA SDK. You need Visual Studio 2017 or 2019 (Community is free).
  See: https://github.com/dotnet/corefx/blob/master/Documentation/building/windows-instructions.md#required-software
C:\w\corefx\src\Native\build-native.proj(50,5): error MSB3073: The command ""C:\w\corefx\src\Native\build-native.cmd" x64 Debug Windows_NT outconfig netcoreapp-Windows_NT-Debug-x64" exited with code 1.
Build FAILED.
EXEC : error : DIA SDK is missing at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\DIA SDK". Make sure you selected the correct dependencies when installing Visual Studio. [C:\w\corefx\src\Native\build-native.proj]
C:\w\corefx\src\Native\build-native.proj(50,5): error MSB3073: The command ""C:\w\corefx\src\Native\build-native.cmd" x64 Debug Windows_NT outconfig netcoreapp-Windows_NT-Debug-x64" exited with code 1.
    0 Warning(s)
    2 Error(s)
Time Elapsed 00:03:28.80
Build failed.

Comments

Post a Comment

Popular posts from this blog

EnumeratorCancellation: CancellationToken parameter from the generated IAsyncEnumerable.GetAsyncEnumerator will be unconsumed

Introduction If you're lucky enough to be using moderately new tech at work, or you just love trying out all the new goodies, you've probably had a chance to play around with IAsyncEnumerable<T> It does not take long until you come across CS8425 compiler warning, specifically if you're using yield and await keywords, and letting compiler do the heavy lifting of generating an implementation for you. CS8425 Async-iterator member has one or more parameters of type 'CancellationToken' but none of them is decorated with the 'EnumeratorCancellation' attribute, so the cancellation token parameter from the generated 'IAsyncEnumerable<>.GetAsyncEnumerator' will be unconsumed Don't know about you, but I didn't really understand what this warning actually means the first time I saw it. And the second time too. 😁 But hey - as application developers we've authored quite a lot of unreadable error messages ourselves, we have ...
Post a Comment
Read more

Serilog with Application Insights: Correlating logs with other telemetry by using Operation Id

Despite the odds, Serilog and Application Insights are a fairly common combination. Let's dive in and find out if such partnership is well justified. Introduction Serilog  is an extremely popular structured logging library, with powerful DSL and serialization features. The  benefits of structured logging  are well known an widely appreciated, so if you're not convinced yet, do spend some time to read up on the topic. Application Insights  is a very popular APM SaaS offering from Microsoft on Azure, especially in the .NET world. Motivation Now, you might wonder -  why put those two together ? After all, not all great tech plays together well. And I completely agree with that. In fact, when starting a greenfield application, Elastic Search seems to be a better choice for storing and searching structured logs data. One of the obvious benefits would be the data ingestion pipeline speed. But logs are only part of the story, however. When we look at the AP...
4 comments
Read more

Elastic Index Lifecycle Management

Elastic Stack is quite capable of running blazing fast queries against your data. However, the more data you have, the more time it will take to query it. Most of the times, however, Elastic Stack will not be the mechanism you use for long time data retention. Consequently you will have to get rid of the old data. Let's find out how. Brief overview of steps required Pick a naming convention Create index lifecycle management policy Create an index template that connects the alias and the ilm policy Create an index  Associate an  alias  with the index Let's dig into the details. Pick a naming convention Depending on the size of your company, your topology, team and org structure, you will probably have a Elastic Stack deployment that is shared between several teams and used by multiple services (distributed tracing benefits).  Namespaces is a useful notion that we can leverage while naming ELK objects, even though the notion itself is not dir...
Post a Comment
Read more