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 DLL and PDB filenames contain "Windows-Managed", and if they're included in a C# project as content (as only the winmd file is included as a reference), Visual Studio interprets the dash in the filename as a language name (just like with en-US), and generates a warning during packaging since the app doesn't actually support such as "language"
The text was updated successfully, but these errors were encountered:
Need to notify our partners who might have been using this with an old .dll name(s). It'd make sense to consistently rename the .dll for all platforms, using the following naming convention:
Microsoft.Applications.Telemetry.Windows.UWP - for Universal Store apps, expose WinRT-style platform types.
Microsoft.Applications.Telemetry.Windows.native - for Universal Store apps written in C++ only, light SDK flavor that does not include WinRT-style projection - we expose STL projection. That is the flavor used by Outlook Universal store and Office, so we need to notify them about the renaming from dash to dot accordingly.
Microsoft.Applications.Telemetry.Windows.NET - for .NET 4.0 framework, expose C# system types.
@mkoscumb@kindbe - this .dll renaming may affect Office immersive apps packaging. If you have objections on this, we can keep -native suffix for native C++ .dll
Shouldn't be too bad for Office. We consume the 1DS C++ SDK from static source drops or via NuGet drops. I'll give a head's up to the teams that consume the SDK.
The DLL and PDB filenames contain "Windows-Managed", and if they're included in a C# project as content (as only the winmd file is included as a reference), Visual Studio interprets the dash in the filename as a language name (just like with en-US), and generates a warning during packaging since the app doesn't actually support such as "language"
The text was updated successfully, but these errors were encountered: