My infrastructure guy just install the new BC with CU 10 (August 2019), I double-checked and its runtime is 2.4
I even get the below error when I try to install an extension with Runtime 3.0:
The runtime version of the extension package is currently set to '3.0'. The runtime version must be set to '2.4' or earlier in the app.json file in order to install the extension package on this platform.
based on this link, if I'm on CU10 then it should give me the runtime 3.0
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-json-files
Does anyone have any idea how to get the runtime 3.0 on business central on-perm?
Here you can find a detailed list of Business Central versions:
https://www.navisionplanet.com/business-central-download-version-list/#BC15
It's an annoying website that jumps to ads once in a while! Find your version and upgrade one generation, I think 14.1 is the first version with Runtime 3.
Related
I have a .net core Blazor Server App which is currently using version 6.03 of .net core.
Version 6.04 came out a few days ago, and I need to upgrade the project and then publish it so it is using the new bits.
I have:
Install the latest SDK from here which includes 6.04.
I also used Nuget to ensure all libs are on 6.04.
However, when I open the project, and check the file versions, it is still using 6.03.
I have looked for any setting in the project file that would indicate which version of .net 6, it is using, but I don't see any such setting. I only see this setting:
<TargetFramework>net6.0</TargetFramework>
Is there some way to get VS to use 6.04 instead of 6.03?
After quite a bit of working with this, I found that the minor version is tied to the Version of Visual Studio that you are using.
So, I was using VS 2022 Version 17.2.0 Preview 4, and the .net 6.0.4 bits had not been released yet for this version. So those bits are not accessible from this version.
However, the 6.0.4 bits have been released for VS 2022 Version 17.1.5. So by downloading and installing 17.1.5, the project then opened up using 6.0.4 without any other changes.
I am sure that soon the bits will be released for the 17.2 version soon.
I'm trying to build a windows application. But I'm running to the below error. I tried to download the version 10.0.18362.0 and rebuild the solution, but still runs into the same error.
"DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. You currently are running version 10.0.17763.1397. Please update your OS, or change your deployment target to a device with the appropriate version."
Appreciate any suggestions on how to proceed.
Note: I followed other similar questions to change the target and minimum version. But still runs into the same error.
Thanks
According to the error message, this is because your current system version is lower than the minimum version required by the application.
The safer way is to upgrade the system. The current version of your system is 17763 (1809), you need to upgrade to at least 18362 (1903).
Here is the download address of the upgrade tool: Download Windows 10.
Another way is to reduce the minimum version requirements of the application.
Right-click the UWP application project, select Properties , and change the Min version to a lower version (such as 17763).
If the entire solution contains projects other than UWP application projects (such as some class libraries), the minimum version also needs to be adjusted.
This is not a safe method. Because some APIs used by the application may only be provided in versions 18362 and above, the version cannot be lowered in this case.
The official documentation does not work.
Do I need VS 2017 Preview?! Or to restart my pc every time I install "Latest stable 2.2.3" SDK's? Perhaps its not so stable? Should I try 2.2.1 lol
VS 2015 will work up for up to .NET Core 1.1 (now EOL). VS 2017 will work for up to .NET Core 2.2. .NET Core 3.0+ requires VS 2019.
It's not clear what your exact issue is, but the process is basically this:
Download the appropriate .NET Core SDK version. Be careful because the SDK version is somewhat independent of the .NET Core version. Pay attention to specifically what version of .NET Core the SDK supports, not the version number of the SDK itself.
Edit your project file and change the target to the new .NET Core version. This will be the minor version, not patch releates. In other words, for any .NET Core 2.2.X, you'd use netcoreapp2.2 as your target.
That's it. After you save, any NuGet dependencies of your project, such as Microsoft.AspNetCore.App will update to the latest version within that target, i.e. 2.2.X. However, note that some packages may not always have new versions. Most of the major parts of ASP.NET Core, for example, change enough with each version that the NuGet packages get bumped as well. However, it is possible that you may still use a 2.1.X package if nothing changed in that for 2.2. In any case, you'll be able to see in Visual Studio if it's fully updated or not.
I want to upgrade SonarQube and I haven't done this before so I have few question. Please could you help me with them?
How can I find which edition is installed on my server?
How can I find if the installed version is licensed or not?
How can I upgrade from 5.6.4 to 6.7 LTS? Do you have upgrade guide for the same?
You can always find which version is installed by logging into the SonarQube web app and looking at the footer of the page or by going to Administration / System / System Info. If you for some reason can't log in to the web app, and installation folder name does not contain the version number as it does by default, look in the "lib" folder for a file that looks like "sonar-application-6.3.1.jar". That will tell you the version number as well.
Here are the general steps for upgrading, from the Upgrade the Server docs:
Download and unzip the SonarQube distribution of your edition in a
fresh directory, let's say $NEW_SONARQUBE_HOME
Manually install the
non-default plugins that are compatible with your version of
SonarQube. Use the Compatibility Matrix to ensure that the versions
you install are compatible with your server version. Note that the
most recent versions of all SonarSource code analyzers available in
your edition are installed by default. Simply copying plugins from
the old server to the new is not recommended; incompatible or
duplicate plugins could cause startup errors.
Update the contents of
sonar.properties and wrapper.conf files (in
$NEW_SONARQUBE_HOME/conf) with the settings of the related files in
the $OLD_SONARQUBE_HOME/conf directory (web server URL, database,
ldap settings, etc.). Do not copy-paste the old files. If you are
using the Oracle DB, copy its JDBC driver into
$NEW_SONARQUBE_HOME/extensions/jdbc-driver/oracle
Stop your old
SonarQube Server
Start your new SonarQube Server
Browse to
http://yourSonarQubeServerURL/setup and follow the setup
instructions
Analyze your projects (and compute your
Views|Portofolios|Application if you own the Enterprise Edition
product) to get fresh data
Before embarking on this, you will want to check out the intermediate upgrade notes for each version in order: 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, and 6.7.
Note that upgrade notes for versions after 6.7 are hosted at the new documentation site.
we have upgraded to SonarQube 4.3 and C# plugin 3.0 but we are struggling to get the integration with resharper working.
Which version of the Reshaprer plugin shall be available for SonarQube 4.3?
In update center I find version 1.0 but when I look at the reshaper plugin documentation there shall be a version 1.1 available.
Can I upgrade to the resharper plugin to version 1.1 in any other way? I have tried to put the 1.1 jar file in the plugin directory but then SonarQube refuse to start due to missing dependencies.
The reason for wanting version 1.1 is that we need to use our own dotsettings file and this seems to not be available in version 1.0. We also can´t get the reuseReport mode to work at all with the current installed version. Even if we use “sonar.resharper.mode=skip” resharper is trigged in the analysis.
The situation is quite messy, there indeed was a ".NET ReSharper" plugin available in version 1.0 and 1.1. This plugin is only compatible with the .NET ecosystem 2.1.
C# 3.0 is only compatible with a "ReSharper" plugin, which only exists in version 1.0.
Please refer to the following documentation: http://docs.sonarqube.org/display/SONAR/ReSharper+Plugin
Indeed the ReSharper 1.0 plugin does not support reuseReport mode (and it is not planned to add it currently).
However, there are plans to be able to import/export DotSettings files from/to SonarQube quality profiles: https://jira.codehaus.org/browse/SONARPLUGINS-3738
Have also a look at the example project: https://github.com/SonarSource/sonar-examples/tree/master/projects/languages/csharp
Final note: The .NET ecosystem 2.1 is not compatible with SonarQube 4.3.