Is Package design Sonar analysis supported for .NET projects? - sonarqube

I am new to Sonar how ever I have some basic overview of its capabilities.
My problem is that the Package design and File design widgets don't show any data.
Are these metrics supported on a C# analysis project or only Java code is supported ?..
Thanks

This used to be supported for C#, but it has been dropped in version 3.0 because it was badly supported.
See the following ticket: SONARCS-38

Related

Performance Issue after .net core 2.1 migration

Existing .Net framework 4.6.2 based web api project & class libraries have been migrated to .net core 2.1 webapi project & its class library have been migrated to .net standard 2.0 with very minimal core, mostly as part of migration either existing nuget package has been upgraded and existing package was swapped with .core compatible SDK version with very minimal/negligible code changes.
Right after the migration application's entire functionalities facing performance issue.
Once.Net framework based out code has been migrated to .net core, is the performance issue expected one?
Any effective open source tool to profile & measure performance?
Any mitigation to solve these performance issue? please suggest

For a Xamarin Forms application is the PCL architecture becoming obsolete?

I have a Xamarin Forms application that uses shared code. It has three projects, shared, iOS and Android. These are very similar to those which are created when I create a sample application from the Xamarin new project menu.
I am looking to have the application updated and published by a company that has experience in doing this but I am not sure I understand a couple of the work items that have been suggested to me:
Currently, architecture is PCL which is becoming
obsolete.
Move to .NET standards
Could someone explain to me what these work items might mean?
Yes, it will become obsolete at some point. .NET Standard is the evolvement of the PCL libraries.
With PCL libraries you could target a number of platforms and only the functionality that was supported for all targeted platforms were available to you. Associated with each combination of platforms were the profiles. A profile was identified by two or three digits. Notable ones for Xamarin were 111 or 259. Read more on PCLs here: https://learn.microsoft.com/en-us/xamarin/cross-platform/app-fundamentals/pcl
.NET Standard is a specification of the APIs associated to it. If a platform supports a certain version of the .NET Standard, you are guaranteed that all APIs are available. This way, you can simply target a specific .NET Standard version and each platform that supports it will support your application. The .NET Standard specification has gained a lot of traction and is already more cross-platform than a PCL ever was. Most of the creators of NuGet packages are supporting it already and also Xamarin/Microsoft has replaced the PCL with a .NET Standard library in their templates. Read more on .NET Standard as a concept here: https://learn.microsoft.com/en-us/dotnet/standard/net-standard
So, if you have the possibility it might be wise to start moving to the .NET Standard library. That is, if you want to keep supporting your app and need new libraries coming in. If your app is fine the way it is, you can probably keep going with the PCL for a while. Converting is basically: change the csproj structure to the new structure. Retarget your library to netstandard and reinstall all the libraries you have installed, this time to download the .NET Standard compatible version. The last step might be a bit of a pain.
A good resource on converting might be this by Adam Pedley: https://xamarinhelp.com/upgrade-pcl-net-standard-class-library/
There is also a solution to do it automatically: https://smellyc0de.wordpress.com/2018/03/23/automatically-converting-pcl-to-net-standard-2-0-project/
.Net Standard is a specification for a set of APIs. and is the way things are going. With it, comes a higher level of range of .Net SDK APIs you can use, plus most 3rd party Nuget packages will support it. They can support a wider range of platforms. by targeting .Net Standard. Thus you will get access to a larger number of nuget packages. See https://learn.microsoft.com/en-us/dotnet/standard/net-standard
I put my Forms Apps into a .Net Standard library, because it easier to unit test. There is a Xamarin Forms nuget package you can use for testing, which means a lot of UI paths can be verified in code, where previously you had to do it on a device, perhaps with automated testing. https://github.com/jonathanpeppers/Xamarin.Forms.Mocks
Upgrading an existing PCL project to .net standard is a pain. Any more, I just create a new Xamarin Forms solution with the same name/root namespace, with the app as .Net Standard, then copy files over.

Xamarin cross platform .net2.0

I've created a Cross platform Application for Xamarin in Visual Studio. The application is running on .NET Standard 2.0 and it's not possible to select a higher version.
Isn't possible to run a Xamarin project on a newer .NET version? The problem is that a want to install nuget packages that requires at least .NET 4.5.
Thanks in advance.
You are confusing .net and .net standard. .net standard gathers many other .net platform (for example .net core, uwp, windows phone etc...) including the classical .net (from 4.5 to 4.6.1). Take a look at this table to have a better understanding.
This means that you should be able to include your library that targets .net 4.5.
Now that you know that, you can define a fallback version if the library does not target .net standard. To do so add this line in your .net standard .csproj in the PropertyGroup node
<PackageTargetFallback>$(PackageTargetFallback);portable-win+net45+wp8+win81+wpa8</PackageTargetFallback>
.NET Standard is a standard, official documentation is nicely covering it. Beside that must read, here is a compatibility table.
So please, read the official documentation. Setup your mind and come back with a proper question. Currently it does not make sense.
Good luck!
P.S.: Currently you are trying to use an outdated library that does not support .NET Standard, you might want to look for alternatives.

Importing PC-lint report along with SonarQube C++ Commercial Plugin

I would like to know if there is any way where we can integrate PC-lint report along with C++ analysis using Commercial C++ Plugin.
we are using SonarQube 5.1.2 currently.
But I am ready to upgrade if that's what it takes
If you are using the SonarSource C++ Plugin, this means that you are a customer so you should contact the commercial support who will answer your question.

visual studio testing capabilities

I am looking to find out the testing tool capabilities that are offered with Visual Studio. From my research, I understand that you offer both functional and load testing tools for both web and Windows-based applications. I read the ‘coded UI Tests’ feature automates UI testing. My questions is, does this feature only work on .NET-based applications or can I use it to do UI testing on an application that was written in PowerBuilder?
You can find here the configurations that are supported by coded UI.
PowerBuilder is not in the list but depending on the technology it relies on (MFC?) it might work.
You can download a trial version of VS and try it on a PB application.

Resources