All geek questions in one place

Fabric Service Debugging Issues

I have 2 Service Fabric services that I need to debug. These services communicate with each other. I use:

VS 2017(update 7), .NET Framework 4.6.1, Azure SDK 2.9.5.3, Service Fabric Tools 2.0.20180124.2, Service Fabric 6.1.456.9494, Service Fabric SDK 3.0.456.9494

Everything went well, but at some point I started getting the following errors when I try to start debugging the second service. I do not understand why I get these errors. (Google produces absolutely nothing about these errors) Here they are:

1st error: error MSB4064 "ProjectReferencesWithConfiguration" parameter is not supported by the "GetServiceProjectReferences" task. Check if the parameter exists in the task, and this is a custom publishing example property. \ packages \ Microsoft.VisualStudio.Azure.Fabric.MSBuild.1.6.5 \ build \ Microsoft.VisualStudio.Azure.Fabric.Application.targets 95

Second error: error MSB4063 The task "GetServiceProjectReferences" may not be initialized with input parameters. \ packages \ Microsoft.VisualStudio.Azure.Fabric.MSBuild.1.6.5 \ build \ Microsoft.VisualStudio.Azure.Fabric.Application.targets 94

Here is the full scenario:

  • One of the services (no matter which one) in one copy of VS successfully started without errors.
  • I am trying to start the second service on another copy of VS. And during this attempt, I get the errors that I mentioned above.

To remedy the situation, I need to close the violating copy of VS and open the ServiceFabric service in a new copy of VS, after which the service will start working successfully. Unfortunately, all these dances become very annoying because it takes a lot of time.

Any help would be appreciated.

+5
source share
2 answers

It seems like upgrading the Service Fabric SDK to version 467 did the trick. I work all day today and do not see sluggish error messages during the launch of services.

0
source

I solved this by updating the Microsoft.VisualStudio.Azure.Fabric.MSBuild Nuget package from version 1.6.4 to 1.6.5

After that, I also had to manually change 1.6.4 to 1.6.5 in the .sfproj file, since the Nuget package manager did not do this automatically.

0
source

Source: https://habr.com/ru/post/1275629/

More articles:


All Articles