* Disable PathMap for debug to fix symbols mapping
Enabling it for debug prevent debugger from loading symbols
* Update Directory.Build.props
* Fix tests
---------
Co-authored-by: Keith Cully <2370032+K-Cully@users.noreply.github.com>
Co-authored-by: artempushkin <32305353+artempushkin@users.noreply.github.com>
Co-authored-by: Neil <49037171+neilr81@users.noreply.github.com>
* Adding NetStandard support for Abstractions Library
Netstandard is still needed in one place down the chain. Updated all other projects to use netcore versions and reduced library targets to the Abstractions project
* remove netcore check
---------
Co-authored-by: Neil Richardson <neil.richardson@microsoft.com>
* Updating tests to run on the latest version of .NET
Both versions is unnecessary since .NET Standard support was dropped. Also don't need an OS check anymore.
* Update Directory.Packages.props
* Update Directory.Build.props
Test setting framework explicitly.
* Update Directory.Build.props
* Update dotnet-initialize.yml
* Fixing secret suppression
Also removing .NET Framework from unit tests as it's not used by any projects.
* Update Directory.Build.props
* Update Directory.Build.props
* Update Directory.Build.props
* added dotnet 6 to targets
* unittest only .NET 7
* unittest SettingsGen only net7
* web unittest only .net 7
Co-authored-by: Pavel Gajdusek <pgajdusek@microsoft.com>
* Remove .NET 5 from targets
No need of targeting it explicitly, since most of the consumers updated or can use `.netstandard2.0` dll.
* Update build.yml
* Update Dockerfile
* Attempt remove net472 as a targets for packages
Theoretically, we don't need net472 as a target anymore since it could use netstandard2.0 instead, we'll see how it will work :)
* Fix unit test targets
* Order variables
* Fix naming
Create extension projects to simplify the usage of common logic:
Microsoft.Omex.Extensions.Abstractions for common interfaces
Microsoft.Omex.Extensions.Compatability to support old logging and validation logic
Microsoft.Omex.Extensions.Logging implementation of LoggerProvider
Microsoft.Omex.Extensions.TimedScopes abstraction to measure code execution using Activity
Microsoft.Omex.Extensions.Hosting providers entry point with initialized logger timedscopes and DI
Microsoft.Omex.Extensions.Hosting.Services entry point for SF Services
Microsoft.Omex.Extensions.Hosting.Services.Web entry point for SF Web Services
A sample usage would be:
public async Task Main(string[] args)
{
await Host
.CreateDefaultBuilder(args)
.AddOmexCompatabilityServices() // Microsoft.Omex.Extensions.Compatability, needed only if you want to use ULSLogger or Code.Validate
.BuildStatelessService( // Microsoft.Omex.Extensions.Hosting.Services
"MyAwesomeService",
builder =>
{
builder
.AddServiceAction(RunAsyncAction1)
.AddServiceAction(RunAsyncAction2)
.AddServiceListener("MyListener1", Listener1)
.AddServiceListener("MyListener2", Listener2)
.AddKestrelListener<Startup>( // Microsoft.Omex.Extensions.Hosting.Services.Web
"MyWebListener",
ServiceFabricIntegrationOptions.UseReverseProxyIntegration);
})
.RunAsync();
}