Service fabric tooling in VS2017 seems to be broken - azure-service-fabric

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.

Related

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.

CrystalReports For Visual Studio 2017 Previous Versions on NuGet

I moved development over to a new workstation and Visual Studio 2017. I installed all the Crystal Decisions References using NuGet Package Manager for Solution from within VS2017 tools and installed the Runtime for 13.0.3501 Everything looked okay, until I tested the app on my client's PC where he also has SAGE 100 running a previous version of Crystal Reports.
SO, I need to back out Crystal Reports Engine for VS2017 to a previous version, I believe it will be 13.0.2000.0.
On NuGet I can only see V13.0.3500.
(I also see CrystalDecision 1.0.0 which is confusing...what's CrystalReports vs CrytalDecisions?)
How,where can I get a previous version? I looked on the SAP website but didn't see how to get previous versions...if indeed this is the right approach to fixing the incompatibility issues.

Deploy Acumatica Framework Tools fails

I am trying to Deploy Acumatica Framework Tools using the Framework Configuration Wizard and I getting the following error:
Exception occurred while installing resources.
Inner Exception:
Can't find the Visual Studio template items location.
I have Visual Studio 2017 Enterprise running on Windows 10 Pro. Both are up to date.
Any ideas on how to correct this. I’m going to the Acumatica Summit next week and need to do the T100 and T200 course.
Thanks
Tom
The wizard is likely looking for the VS2015 registry folder. Until installers are fixed to check in the VS2017 location I recommend you create the VS2015 registry folders with these 4 dummy string keys pointing to VS2017 folder.
The key values in the picture below point to the default VS2017 folders. I tested this workaround a couple months ago on a colleague computer and we experience no ill effects:
I faced the same problem, but I could not change my registry due to company policy. My regedit.exe was unavailable:
So, to fix this issue I installed Visual Studio 2015 Community Edition .
That fixed the issue.
Do not forget to restart your computer after installation, otherwise - you will get the same error. If you solve this problem with installation of VS2015, you will be able to use Visual Studio Template
in VS2015 only. It will not be available in other versions of Visual Studio.

I can't get Nuget push command to work on Visual Studio Online using latest Nuget tasks

I am using Visual Studio 2017 and Visual Studio Online. My team has recently switched to Asp.Net core 1.1 for our web development. Before we had a working nuget publishing process, but that doesn't work anymore because the old nuget tasks are deprecated.
I'm already aware that there should be Nuget package task before the push task, but that task has a known bug for .Net core. Instead I set up my project in VS so that the build task generates my .nupkg file.
Here is my setup from vs-online:
My setup for Nuget push task
The result looks like this:
The result when running.
I solved my problem myself.
I changed the path to:
**/*.nupkg;-:**/packages/**/*.nupkg;-:**/*.symbols.nupkg

SQLite provider in VS2017

I want to connect sqlite using EF6 in VS2017.
I installed "System.Data.SQLite" nuget package.
I also installed "sqlite-netFx46-setup-bundle-x86-2015-1.0.104.0.exe" from http://system.data.sqlite.org, but I cannot see the sqlite provider when adding ADO.NET data entity.
Am I missing something? or the above package not supporting VS2017 (it said it is for VS2015)
There is no DDEX provider package for VS 2017 (yet). https://system.data.sqlite.org/index.html/tktview?name=8292431f51
Basically you need to wait for: sqlite-netFx46-setup-bundle-x86-2017-1.0.1xx.0.exe
"Official" update:
The current estimate is that support for Visual Studio 2017 will
be included in the 1.0.106.0 release, which should be released at
some point in the mid-June timeframe.
mistachkin added on 2017-05-28 20:41:40: At this point, it seems unlikely that I'll be able to add VS 2017 support for the design-time components (e.g. table designer, entity wizard, etc).
UPDATE: I have created a DDEX provider that enables SQLite support (for EF6 only) in Visual Studio 2017, see the how-to guide here: https://github.com/ErikEJ/SqlCeToolbox/wiki/EF6-workflow-with-SQLite-DDEX-provider
The issue was solved after installing SQLite/SQL Server Compact Toolbox.
Please try. https://marketplace.visualstudio.com/items?itemName=ErikEJ.SQLServerCompactSQLiteToolbox
The VS 2017 installer is really a pain in the b***.. Installing packages via an automated deployment works, but detecting installation state and such is near to impossible..
Seems like microsoft devs finally got sick of msi packages and implemented their own installer / package manager for VS2017, as other teams did for Office 365 and such..
According to the url provided by the sqlite-netFX46-bundle-win32-2015-1.0.108.0 intaller log : https://system.data.sqlite.org/index.html/info/8292431f51119807241632b092774e60189018d9 Visual Studio 2017 support isn't available yet
I tryied many things without any result, the worst is that I installed also a VS 2015 but cannot install because of the VS 2017 installation on my computer.