Service Fabric SDK installation - azure-service-fabric

I am facing a problem while installing MS Service Fabric SDK 2.7.198 using Web Installer 5.0 for Visual Studio 2017 v15.2, previously I had installed other versions of SF on different or on same system and it was installed without any problem. But this time I am unable to install it and installation is failed and message says Service Fabric Runtime version 5.7.198.9494 need to be install. I have installed it using Visual Studio installer. Please suggest where I am doing wrong.

Uninstall and re install the visual studio with azure service fabric tools resolved the problem.

I have install only runtime this way. Hope this will help you to install runtime only.

Related

Failed to connect with PostgreSQL from PowerBI Desktop

I've installed the followings
PowerBI desktop
PostgreSQL
Npgsql v4.1.1 (from https://github.com/npgsql/Npgsql/releases)
Visual Studio 2019 (community)
Even after installing all the above, still I am getting
This connector requires one or more additional components to be installed before it can be used.
Is there anything else, I've to install?
I've re-installed the Visual Studio 2019 and it works.

Getting error in AWS toolkit for Visual Studio: Error loading AWS profile

I have installed AWS SDK toolkit for VS 2017. It was working fine. All of a sudden since few days back i am getting error "Error loading AWS profiles: Method not found:'Amazon.Runtime.TcpKeepAlive Amazon.Runtime.ClientConfig.get_TcpKeepAlive()"
I have tried uninstalling and reinstalling the toolkit, also i tried installing it on other machine with VS 2013, but both giving same error.
Is it problem with toolkit or anything changed on AWS side?
I have Windows 10 with latest updates.
VS2017 community edition
VS2013 community edition
Thanks in advance.
It is mostly caused an older version of AWSSDK.core that has already been added to GAC and is forcing your VS to use an older version of AWSSDK.core.dll.
After uninstalling all the other/previous versions of AWSSDK libraries (AWSSDK.S3.dll etc) from GAC solved the problem for me.
Also installing the latest AWSSDK.core.dll to GAC can work.
Hope this info helps someone.
Solution here that worked for me :
https://github.com/aws/aws-sdk-net/issues/1138
I have resolved this issue by uninstalling the latest one and installing this previous stable version of aws toolbar from visual studio update website(exact link https://aws.amazon.com/visualstudio where previous vsix downloaded).. if you cannot find the previous version here I added to my drive you can download.. https://drive.google.com/open?id=1Fkrxmv-dM8fwGDjNqse1Ssdm0k3YYbcH
Once you install old extention, be sure to disable auto update extension in VS.

Service fabric tooling in VS2017 seems to be broken

I have updated service fabric core SDK to 2.5.216 (released March 21st)and also installed Visual Studio 2017. When I open my sf projects in VS2017 it starts showing this message.
I guess this maybe because VS2017 SF tools weren't updated to latest version? I also see that there is no update on thatyet in the new VS2017 installer. Can anyone help me out to figure this issue?
Update:
Looks like the release notes already explains that next version of VS2017 update will include 1.5 version of SF tools. Do you have an estimated timeline on when that update could be released?
Thanks!
You can get the new tooling for VS2017, by installing Visual Studio 2017 preview https://www.visualstudio.com/vs/preview/. The preview can run side by side with other instances of Visual Studio 2017 and contains updates to other parts of Visual Studio. For Service Fabric tooling, we do not support round tripping between Service Fabric tooling in VS2017 preview and VS2017.
We are working on being able to get updated Service Fabric tooling that you can install in to non-preview versions of Visual Studio 2017 going forward.
Unfortunately right now the tooling in VS 2017 is still 1.4. In the .sfproj file there are references to the MSBuild package - which were not updated.
Try to delete the packages folder and reinstall MSBuild package for service fabric project
Install-Package Microsoft.VisualStudio.Azure.Fabric.MSBuild
VS2017 as of today April 05, 2017 released an update which fixed this issue.

Connect-ServiceFabricCluster : Argument 'Connect-ServiceFabricCluster' is not recognized as a cmdlet: Unable to load DLL 'FabricCommon.dll'

I installed Service Fabric by using the Install the Service Fabric runtime, SDK, and tools for Visual Studio 2015 Update 2 link from Prepare your development environment.
Trying to publish a Service Fabric Application fails with:
2>Connect-ServiceFabricCluster : Argument 'Connect-ServiceFabricCluster' is not recognized as a cmdlet: Unable to load
2>DLL 'FabricCommon.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Same error described in Troubleshoot your local development cluster setup, but it does not matter what PowerShell version I use, 64 or 32.
The Service Fabric SDK version I got is 2.1.163.
I am running Windows 10 10586 with Visual Studio 2015 Update 3.
FabricCommon.dll is located at c:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\FabricCommon.dll
What am I missing?
I will focus on this error first:
DLL 'FabricCommon.dll': The specified module could not be found
You can fix this by re-installing the service fabric SDK. This happens to me before during installation and I thought it was fixed but you never know.
Also make sure you are using the same version of the SDK and nuget package that you referenced in your Service Fabric application.
A workaround for this issue (which does not include reinstall of the Service Fabric SDK) is to add the following to your path environment variable and restart the application which is throwing error (Visual Studio or PowerShell so that it can access the new environment variable):
C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code
You do not need to restart your computer, just restart the application after you have update the path environment variable. The dll fabricCommon.dll lives in this folder.
This workaround is inspired by (but is not identical to) the solution to a somewhat related issue presented here: https://social.msdn.microsoft.com/Forums/azure/en-US/6c8cc261-6c84-4097-be03-e8073cbc9397/unable-to-load-dll-fabricruntimedll?forum=AzureServiceFabric&prof=required
All I had to do is restart Visual Studio and it worked. This happens time to time.
Please Run Windows PowerShell as Administrator and then try.
I have experienced the same problem on my Win10 box, and even adding the relevant powershell module that contained necessary cmdlets didn't work. The solution that worked for me was: Control Panel -> "Programs and Features", uninstall Service Fabric SDK, then click "Turn Windows features on or off" link and uninstall PowerShell. Next, reboot Windows, back to Control Panel -> "Programs and Features" -> "Turn Windows features on or off", install PowerShell, after which download/install Service Fabric SDK. Again, restart the PC, start the Service Fabric Cluster Manager (if it doesn't auto-start), right-click its icon on the task-bar and try creating 1-node or 5-node cluster.
I was facing same issue on vs2017 and window server 2016. I reinstalled service fabric sdk and issue fixed.
I had similar issue after creating a cluster on windows server 2016.
In my scenario all I had to do was log out/in again and issue was fixed.
You could try restarting VM too - only if it still fails would I try re-installing the SDK.

Unable to install Visual Web Developer 2008 Express Edition

I got a problem to install the visual web developer 2008 express edition. When I starting to install this application it start installing with visual c++ runtime prerequisites it process a minute or two after that it shows an error The folowing component could not be downloaded visual c++ runtime prerequisites I read an article regarding this at http://forums.asp.net/t/1487605.aspx
It says completely remove vwd 2005 before installing vwd 2008. I did it but it display same error I have net connection also. Where I am wrong to install the application. Please suggest to overcome this problem. Thanks
I would try installing it through Web Platform Installer. If 2008 isn't available anymore, just install 2010, which is fully backward compatible to .Net 3.5