TemoeTosh
TemoeTosh

Reputation: 11

Azure Service Fabric in Visual Studio - hresult : 0x80131500

I'm currently trying to work on Azure Service Fabric in Visual Studio 2015 but I have a general exception (hresult : 0x80131500) when i create a new service fabric project.

For example, I got this error when i create a stateless service project, or anything else coming from service fabric... Can't post screenshots of the process for now... Thing is that when I installed service fabric packages, there were errors (already installed package but not, couldn't access the package)...

Spent hours trying to resolve this problem, I tried to uninstall everything, to change from a version to another, I searched a lot for an answer but not found. Maybe I didn't understand what is happening there, and maybe someone could help me !

Service Fabric Tools: 1.4

Visual Studio: 14.0.25431.01 Update 3

.NET framework: 4.6.1


UPDATE

Thank you everyone, Microsoft updated their packages, it seems that it was coming from them, i tried to reinstall packages again and it works now ! I don't know how this post can be marked as resolved, if someone could do it, it would be great !

Upvotes: 1

Views: 2064

Answers (2)

TemoeTosh
TemoeTosh

Reputation: 11

Microsoft updated their packages, it seems that it was coming from them, i tried to reinstall packages again and it works now !

  • Launch Web Platform Installer (type it in Windows run menu).
  • Select Microsoft Service Fabric package.
  • Install it, or update it.
  • Should work.

Upvotes: 0

Devin Breshears - MSFT
Devin Breshears - MSFT

Reputation: 141

I was able to repro this when the 3.5 .NET Framework was missing. Specifically project creation is looking for targets files under the C:\Windows\Microsoft.NET\Framework\v2.0.50727 folder triggering the exception. Need to investigate why the tooling has a dependency on the older .NEt framework.

For now to try to fix the issue, can you enable the .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature in "Control-Panel->Programs and Features-> Turn Windows features on or off" and see if it also resolves the issue for you.

Upvotes: 0

Related Questions