The documentation around the AOT compilation feature of Xamarin Android states that it is only available when using Enterprise additions of Visual Studio. What does this means for AzureDevops build pipelines if the feature is enabled?
Presumably the build agents don't use an Enterprise addition of the Visual Studio build tools so does this mean a build produced via AzureDevops cannot have the AOT feature enabled? If this is true the feature seems of limited use when using AzureDevops as you won't be able to have it enabled for release builds coming from your build pipelines.
The Build Agent "Windows latest" does have VS 2019 Enterprise installed. See here for a link to the List with all included software.
In addition, last time I tried that out I had to manually install the Android NDK. I used a command line step with this:
C:\"Program Files (x86)"\Android\android-sdk\tools\bin\sdkmanager "ndk-bundle"
Although it might well be that this changed meanwhile since it is listed in the included software.
I followed the instructions of nuget license here.
I use the following code in myproject.csproj:
<PropertyGroup>
<PackageLicenseFile>LICENSE.md</PackageLicenseFile>
</PropertyGroup>
<ItemGroup>
<None Include="..\LICENSE.md" Pack="true" PackagePath=""/>
</ItemGroup>
The Nuget package is built correctly.
No build error or warning related to license.
The license file is included in the package correctly.
When I Inspect the nuspec file in the package, I find this xml code:
<license type="file">LICENSE.md</license>
<licenseUrl>https://aka.ms/deprecateLicenseUrl</licenseUrl>
In MyGet feed package, it show package license as UnKnown and point to: 'https://aka.ms/deprecateLicenseUrl'.
My Question:
Why the nuspec file included in the package show deprecateLicenseUrl?
What I missed to show license in MyGet correctly?
Why the nuspec file included in the package show deprecateLicenseUrl?
Embedded licenses were added to the NuGet client in NuGet 4.9, which corresponds to Visual Studio 2017 15.9, around November 2018. Before then, only license URLs were supported. This means that Visual Studio 2017 15.8 and earlier, as well as Visual Studio 2015 and earlier do not support embedded licenses, and so the license URL pointing to the documentation is added so that they show something, allowing customers to understand why they can't see the real license and instructions on how to find the actual license for the package. Similarly, it means that NuGet feeds need to change to support embedded licenes. The NuGet client team worked with the nuget.org team to make sure they both supported it at the same time, but the NuGet team has no direct influence of other NuGet feed implementations. If MyGet has not updated to support embedded licenses, it can use the lincense url backwards compatibility aimed at users of old versions of Visual Studio.
What I missed to show license in MyGet correctly?
You could use both embedded license and a custom license URL, but then NuGet will generate warnings when you pack, and your package may be rejected if you try to pubilsh to nuget.org. Otherwise you haven't missed anything, it just sounds like MyGet hasn't "kept up" with changes to NuGet.
I get the following error after upgrading to PostSharp 5.0.41.
Error 286 License error. The project uses non-licensed features. It is not allowed to enhance or analyze more than 10 classes in each project by features not covered by the installed licenses. Please visit https://www.postsharp.net/purchase to acquire a license of PostSharp.
I am using the essentials license and PostSharp.Aspects.
Thank you
The licensing of PostSharp 5 Essentials is no longer backward compatible with PostSharp 4.2 Express. See http://www.postsharp.net/blog/post/Announcing-PostSharp-50-RTM (look for "Changes in the Product Line and Licensing") for details.
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 am experiencing issues with my CI build server in which PostSharp is causing the build to fail with the message: The assembly 'yada-yada.dll' uses non-licensed features (Basic Features). [...]. We are using the current version of PostSharp (3.1.52) and have no troubles with the library in local development environment where developers have a registered Express license.
According to PostSharp docs, the build server should not need a license. However, they acknowledge that the automation identification could fail:
If this check does not work for any reason, you may use the license key of any licensed user for the build server. This will not be considered a license infringement. However, it is better to report the issue to our technical support so that we can fix the detection algorithms.
It is recommended to include the license key in the source control.
I'm attempting to test this theory but I can't seem to get access to my actual PostSharp Express license! The PostSharp Options aren't any help either:
Anyone have any ideas? Thanks!
You can find your license key under the registry key HKEY_CURRENT_USER\Software\SharpCrafters\PostSharp 3.
If your license key does not appear at the location specified, these steps will help you find a new one....
Uninstall any previous version of postsharp installed in visual studio by going to TOOLS > Extensions & Updates.
Open regedit. Delete the following registry key (including all child keys):
HKEY_CURRENT_USER\Software\SharpCrafters\PostSharp 3
Download the latest postsharp vs extension. At time of writing I used 4.2.17. Also make sure you are using the latest postsharp nuget package.
Begin the install & follow the steps. When selecting which kind of license you want, choose the Express User License (the last option).
Enter your details, then on the penultimate step, do not tick the box to register postsharp for all accounts on this machine.
Complete the installation, you should then find the license key in your registry under:
HKEY_CURRENT_USER\Software\SharpCrafters\PostSharp 3\LicenseKey
There are two types of keys!
for current user: HKCU\SOFTWARE\SharpCrafters\PostSharp 3
for all users: HKLM\SOFTWARE\WOW6432Node\SharpCrafters\PostSharp 3
The license might be in one of them depending on what license type you chose.