You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The next version of PerfView and TraceEvent will contain some potentially breaking changes, and so I want to give folks some notice.
Target Frameworks
1. TraceEvent will only be built against netstandard2.0. It will no longer be built against net462 or netstandard1.6.
2. FastSerialization will be built against netstandard2.0 instead of netstandard1.3.
There is no change to PerfView's target frameworks: PerfView will continue to be built against net462.
TraceEvent Native Dependencies
TraceEvent has several native dependencies that it carries in the TraceEvent NuGet package and extracts into architecture specific directories. Currently, all architectures are deployed even for architecture-specific builds.
TraceEvent version 3.1 will continue deploy all architectures for architecture-independent builds, but will attempt to limit deployment to the correct architecture for architecture-specific builds. This will help to reduce deployment package size for architecture-specific and single-file builds.
The text was updated successfully, but these errors were encountered:
The next version of PerfView and TraceEvent will contain some potentially breaking changes, and so I want to give folks some notice.
Target Frameworks
1. TraceEvent will only be built against netstandard2.0. It will no longer be built against net462 or netstandard1.6.
2. FastSerialization will be built against netstandard2.0 instead of netstandard1.3.
There is no change to PerfView's target frameworks: PerfView will continue to be built against net462.
TraceEvent Native Dependencies
TraceEvent has several native dependencies that it carries in the TraceEvent NuGet package and extracts into architecture specific directories. Currently, all architectures are deployed even for architecture-specific builds.
TraceEvent version 3.1 will continue deploy all architectures for architecture-independent builds, but will attempt to limit deployment to the correct architecture for architecture-specific builds. This will help to reduce deployment package size for architecture-specific and single-file builds.
The text was updated successfully, but these errors were encountered: