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 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.
Is it possible to use the report designer in the current release of Visual Studio 2017?
The SAP crystal report wiki for visual studio integration only states: "RC build currently not supported - Tested opening existing app and it works".
I have installed the latest developer SDK (Support Pack 19 v.13.0.19.2312), but when I try to open an existing report (.rpt), i got the following message:
There is no editor available for 'C:...\Report.rpt'.
Make sure the application for the file type (.rpt) is installed.
EDIT (2018/02/28)
By the time of asking this question I had installed SP19 on my machine. The current version which should resolve all my issues is SP22, which was released at 2018/01/11. All necessary information and download links are still available in the SAP crystal report wiki.
EDIT (2019/03/20)
Thanks to #ANewGuyInTown: The current version is 13.0.24.
Visual Studio 2017 is supported in Crystal Reports SP 21, which is available for download as of 1 Sep 2017.
This error occurs because at the end of the installation of Crystal Reports SP21 for Visual Studio 2017, the following screen appears:
Do not check to install in runtime, this default to come marked to me is wrong. Install only Crystal Reports SP21 for Visual Studio 2017.
Please wait Support Pack 21 in September 2017
UPDATE:
More info
https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads
VS 2017 - Tested opening existing app and it works, CR for VS is not integrated into the app so no new CR projects available- should be fully integrated in SP 21
About release
Link: https://answers.sap.com/questions/168439/crystal-report-for-vs-2017.html
Moderator Don Williams said:
Not supported yet, I tried to get it into SP 20 but due to time constraints DEV can't get it into VS until SP 21, due out in September time...
I had a workaround for this problem. I created dll project with viewer in vs2015 and used this dll in vs2017. Report showing perfectly.
Starting with Visual Studio 2010, crystal reports is no longer installed with Visual Studio. It can be installed separately by downloading the install from SAP crystal reports website. SAP crystal reports provides two installations. The first is SAP Crystal Reports version for visual studio that is installed for working with crystal reports in visual studio. The other is SAP Crystal Reports runtime engine for .NET Framework that is installed when the application is deployed on server machine.
SAP Crystal Reports in Visual Studio 2017 is now planned for Service Pack/Support Pack 21 (as of Apr 04'2017). The current available service/support pack is 19. Service/Support Pack 21 is expected to be released in September 2017.
You can use the MSI to install on the VS PC, it won't integrate into VS so you won't be able to design reports within the VS IDE but your app will compile. There will not be any Templates either so just add the CR Viewer to the Tool bar. Upgrading an exist VS app will simply work.
So in the meantime to edit rpt files you'll need the stand-alone Crystal Reports Designer until Support Pack 21 comes along.
Sources:
https://forums.asp.net/t/2110984.aspx?VS+2017+and+Crystal+Reports
https://answers.sap.com/questions/168439/crystal-report-for-vs-2017.html
To integrate SAP Crystal Reports with Visual Studio 2017 below steps needs to be followed right:
Uninstall all installed components from system related to Crystal Report. [If any]
Install compatible Crystal Report Developer Edition (as per target VS) with administrator priviledge. [As of writing, latest compatible service pack is 23]
Install appropriate Crystal Report Runtime (x86/ x64) for Visual Studio. [Not mandatory]
Open solution in VS and remove all assembly references from project related to Crystal Report. [If any]
Include following assembly references in project:
CrystalDecisions.CrystalReports.Engine
CrystalDecisions.ReportSource
CrystalDecisions.Shared
CrystalDecisions.CrystalReports.Design
CrystalDecisions.VSDesigner
Make sure "Copy Local" property is set to "True" in reference properties.
Build/ Rebuild project.
Crystal Reports SP 19 does not support Visual Studio 2017. According to SAP they are targeting Visual Studio 2017 compatibility in SP 20 which is tentatively scheduled for June 2017.
I post an answer because I can't comment but I followed #DrCJones steps. I installed the new Crystal Reports SP21 for Visual Studio 2017 with an older version running on my Windows 10. Installer warned me that it detected an older version and that it will overwrite it. Installation were through but I had the following message when I tried to open a project with reports in VS2017:
The Crystal Reports Tools Package did not load correctly
I couldn't edit reports either. So, I manually uninstalled CR Runtime Engine & CR for VS, then reinstalled SP21, finally rebooted.
Now it works :)
Extracted from official SAP site https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads.
Item # 3 fixed my installation.
This applies for ANY Patch after SP 21
FlexNet and In-Place Upgrade does not work: Once user receive the update notification from FlexNet server and finish SP21 upgrade, the product will NOT work. User MUST repair CR4VS and CRRuntime64 in Control Panel\Programs. That’s a by design change to installer.
a. Please notice that we are still facing problems on configuring FlexNet upgrade server, so currently user will NOT receive SP21 notification
Microsoft Windows Update KB2999226 is a prerequisite for SP21.
a. This is same as BI 4.2 SP4 and BI 4.1 SP10. Please refer to SAP Note 2451830.
For VS2017 integration, user needs use “run as Administrator” by right-clicking setup.exe, even if you are already log on by using Administrator account
As most of CR/RAS .NET Assemblies are now re-versioned from 13.0.2000.0 to 13.0.3500.0, user MUST remove all old CR assemblies from Reference list and add the new version of CR assemblies, then rebuild the application.
a. For those customer/user who do not wanted to rebuilt their application, there’s workaround to use in app.config/web.config, please see attachment.
WinFormCRViewer.zip
For reports using the ADO.Net DB connection, in previous SP's, you could only work under .Net Framework 2.0/3.5, so using in app.config is required. Now in SP21, ADO.Net is only supported on .Net Framework 3.5 or above.
I had exactly the same problem with my VS 2013 solutions when I install VS 2017 and Crystal Reports SP21.
In fact it's because VS does not necessarily convert the solution in the first launch.
Once you have installed Crystal Report SP 21, make sure that VS 2017 upgrade your solution : a window must appear "SAP Crystal Reports, version for Visual" with a radio button "Convert the solution".
Screenshot in french :
When I used the menu "File / Open / Project/Solution", the conversion was not done.
I have to do that :
Add VS 2017 on the tasks bar
Run VS 2017 and Open the solution with File menu
Try to build the project, errors appear with Crystal Reports
Close VS 2017
Right click on VS 2017 shortcur in then tasks bar and open the solution directly
The conversion run this time, you can open .rpt and the solution build without error.
I had the same problem and I solved by installing Service pack 22 and it fixed it.
So to sum up, this is what worked for me after upgrading my VB 2010 (CR18) to VB 2017:
Uninstall all runtimes AND CRforVS.
Reboot
Install CRforVS SP23 (no runtimes needed on developer machine).
Open project, remove old DLL references.
Add new references (DLL files that you need from C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet)
Rebuild All.
Have fun.
As of 20/03/2019 -> There is a new version of Crystal report for Visual Studio.
The version is 13.0.24.
The provided version in the accepted answer is 13.0.21.
The newer version worked for me without having to do any workaround.
FYI: Taken from: https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads
Overview
Support Packs for “SAP Crystal Reports, developer version for Microsoft Visual Studio” (SAP Crystal Reports for Visual Studio) are scheduled on a quarterly bases and support the following versions of Visual Studio:
VS 2010 – original release and higher
VS 2012 – SP 7 and higher
VS 2013 – SP 9 and higher
VS 2015RC – SP14
VS 2015 – SP 15 and higher
VS 2017 - SP 21 and higher
Download Crystal Reports developer, for Microsoft Visual Studio
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.
I've seen this discussion on upgrading from a previous version of Visual Studio to VS 2008, that is distributed using ClickOnce. I'm wondering about going from VS 2008 to VS 2010. We used Crystal Reports XI Release 2, back when we wrote that original app. Now I'd like to upgrade it to VS 2010. However, on a previous project we also had to upgrade Crystal to Crystal Reports for VS 2010. if I update this project to VS 2010, I'm assuming I'll be forced to upgrade the version of Crystal as well. What issues do I face, upgrading an older version of a .NET app from .NET 3.5 SP1 to .NET 4, going from CR 11 R 2, to CR for VS 2010, and is deployed using ClickOnce?
When we upgraded the prerequisites of our ClickOnce applications, we changed the deployment accordingly and published it to a new URL. Then we took the old version of the application and added code to it so it would uninstall itself and then invoke the new installation from the new URL. This worked like a charm. You get your new prerequisites installed (if needed), and the app is installed with its new target framework (etc).
This article about certificate expirations has the code for doing the uninstall/reinstall. We've used it several times and it worked great. It even clicks OK on the uninstall dialog for the ClickOnce app. We even used a variant of this code to do an uninstall/reinstall of a VSTO application.