Microsoft.ServiceFabric.Data.Impl.pdb not loaded

608 Views Asked by At

I am working on Service Fabric (my first service fabric project). And I get this strange error that says Microsoft.ServiceFabric.Data.Impl.pdb not loaded. I am sure its not mistake in my code because I tried to comment parts of my code and that error always shows up. As I understood it by now its not some part of my code that is a problem its more in witch point of time is happening in some background thread that is not my doing but Service Fabric thread. That is just my current conclusion, it could be totally wrong.

But when I debug my project without an breakpoints my application just exits (same effect as someone press stop debugging button).

enter image description here

In Diagnostic Events Window there is this enter image description here

Does anyone know why is this happening or what does it mean. Or how can i get some more information about the bug I getting.

EDIT

Program.cs

 try
        {
            // The ServiceManifest.XML file defines one or more service type names.
            // Registering a service maps a service type name to a .NET type.
            // When Service Fabric creates an instance of this service type,
            // an instance of the class is created in this host process.

            ServiceRuntime.RegisterServiceAsync("CECacheMicroserviceType",
                context => new CECacheMicroservice(context)).GetAwaiter().GetResult();

            ServiceEventSource.Current.ServiceTypeRegistered(Process.GetCurrentProcess().Id, typeof(CECacheMicroservice).Name);

            // Prevents this host process from terminating so services keep running.
            Thread.Sleep(Timeout.Infinite);
        }
        catch (Exception e)
        {
            ServiceEventSource.Current.ServiceHostInitializationFailed(e.ToString());
            throw;
        }
1

There are 1 best solutions below

4
On BEST ANSWER

Can you run Install-Package Microsoft.ServiceFabric.Data.Impl -Version 0.10.0-preview-01 in package manager console for your solution and check if this issue still persists?