Catching exception when failing to read config in partial trust

[stimms]

Fix Issue #416 .

Expand the area under try catch to allow for client initialization in partial trust scenarios, specifically as part of a Dynamics 365 plugin.

• [x ] I ran Unit Tests locally.

[msftclas]

All CLA requirements met.

[stimms]

I'd love some insight as to why the build failed on this trivial change but the devops builds aren't publicly accessible.

[cijothomas]

azurepipelines infra is down. nothing to do with this PR. will merge after we get infra back.

[cijothomas]

@stimms The build is failing with stylecop checks. Can you build locally in Release, and you will be able to see the same errors.

[cijothomas]

There is this test failure, about the new Warning trace.

Test method Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSourceTest.MethodsAreImplementedConsistentlyWithTheirAttributes threw exception:
System.Exception: ApplicationInsightsConfigNotAccessibleWarning is implemented incorrectly: EventId. expected: '45', actual: '0' ---> System.Exception: EventId. expected: '45', actual: '0'

Stack trace
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.AssertEqual[T](T expected, T actual, String message) in \Test\TestFramework\Shared\EventSourceTest.cs:line 115
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.VerifyEventId(MethodInfo eventMethod, EventWrittenEventArgs actualEvent) in \Test\TestFramework\Shared\EventSourceTest.cs:line 76
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.VerifyMethodImplementation(EventSource eventSource, MethodInfo eventMethod) in \Test\TestFramework\Shared\EventSourceTest.cs:line 34
--- End of inner exception stack trace ---
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.VerifyMethodImplementation(EventSource eventSource, MethodInfo eventMethod) in \Test\TestFramework\Shared\EventSourceTest.cs:line 41
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.MethodsAreImplementedConsistentlyWithTheirAttributes(EventSource eventSource) in \Test\TestFramework\Shared\EventSourceTest.cs:line 18
at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSourceTest.MethodsAreImplementedConsistentlyWithTheirAttributes() in \Test\Microsoft.ApplicationInsights.Test\Shared\Extensibility\Implementation\Tracing\CoreEventSourceTest.cs:line 14

[cijothomas]

Failed MethodsAreImplementedConsistentlyWithTheirAttributes
Error Message:
Test method Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSourceTest.MethodsAreImplementedConsistentlyWithTheirAttributes threw exception:
System.Exception: ApplicationInsightsConfigNotAccessibleWarning is implemented incorrectly: EventId. expected: '45', actual: '0' ---> System.Exception: EventId. expected: '45', actual: '0'
Stack Trace:
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.AssertEqual[T](T expected, T actual, String message) in /mnt/a/1/s/Test/TestFramework/Shared/EventSourceTest.cs:line 115
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.VerifyMethodImplementation(EventSource eventSource, MethodInfo eventMethod) in /mnt/a/1/s/Test/TestFramework/Shared/EventSourceTest.cs:line 35
--- End of inner exception stack trace ---
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.VerifyMethodImplementation(EventSource eventSource, MethodInfo eventMethod) in /mnt/a/1/s/Test/TestFramework/Shared/EventSourceTest.cs:line 41
at Microsoft.ApplicationInsights.TestFramework.EventSourceTest.MethodsAreImplementedConsistentlyWithTheirAttributes(EventSource eventSource) in /mnt/a/1/s/Test/TestFramework/Shared/EventSourceTest.cs:line 16

[cijothomas]

/AzurePipelines run

[azure-pipelines]

For the Azure DevOps organization bhyada, no matching pipelines using the Azure Pipelines app were found for this pull request.

[cijothomas]

/azp help

[azure-pipelines]

Supported commands
     help:
          Get descriptions, examples and documentation about supported commands
          Example: help "command_name"
     run:
          Run all pipelines or a specific pipeline for this repository using a comment. Use
          this command by itself to trigger all related pipelines, or specify a pipeline
          to run.
          Example: "run" or "run pipeline_name"

See additional documentation.