There are bunches of contrasts between utilizing a Standard Class/Portable Class Library (PCL) and Shared ventures in a Xamarin arrangement. Be that as it may, the most evident one shows up when you open any XAML document in a Shared undertaking: In a Standard Class library you’ll get IntelliSense bolster; in a Shared Project you won’t get any IntelliSense bolster and for all intents and purposes each component in your XAML record will be hailed as a mistake (however, luckily, your answer will at present accumulate).
Except if you have a convincing motivation to run with a Shared venture (for instance: your form of Visual Studio doesn’t bolster Standard Class Library ventures), you’ll need to utilize PCL or a Standard Class Library venture … also, a Standard Class Library venture is your best decision going ahead. Truth be told, if your rendition of Visual Studio doesn’t bolster Standard Class Library Projects and you need to work with Xamarin, it may be a great opportunity to move up to a more up to date form of Visual Studio (recalling that, for instance, Visual Studio 17 Community Edition is free).
In case you don’t know which sort of task your Solution is as of now utilizing, first take a gander at the symbol adjacent to your regular venture in Solution Explorer: If it’s two covering precious stones, you have a Shared undertaking (terrible); in the event that you have a straightforward box with “C#” within it then you have a Standard Class Library (great) or a PCL (not very great) venture. To recognize a PCL and a Standard Class Library, open the venture’s properties and check whether you have a Library tab on the left. In the event that you do, you have a PCL venture (as I stated: not very great).
To change over your answer for utilizing a Standard Class Library venture, first right-tap on your Solution hub in Solution Explorer and utilize Add | New Project | .NET Standard | Class Library (.NET Standard) undertaking to include a Standard Class library venture your answer. Once the task is included, erase any default assets in the venture (you won’t require the Class1.cs record, for instance). At that point simplified any assets from your current Shared/PCL task to your new Standard Class Library venture. On the off chance that you have an App.xaml record that denotes the begin purpose of your application in your old undertaking ensure that you drag it to your new venture.
Next, right-tap on your new venture and utilize Manage NuGet Packages to add the Xamarin.Forms bundle to your undertaking. You’ll have to include some other references or NuGet bundles your unique venture was utilizing.
Presently complete a revamp on your new undertaking. In the event that you get some arrange time blunders you haven’t seen previously, open your task’s Properties and, on the Application tab, watch that the Target structure dropdown list is set to the most abnormal amount (as I compose this present, that is .NET Standard 2.0). On the off chance that it isn’t, set the dropdown to the most elevated amount and attempt another form. In the event that despite everything you have order time issues, at that point it’s too soon to move to a .NET Standard Class Library venture and you’ll need to live with your Shared or PCL venture.
Presently, the terrifying part: right tap on your Shared or PCL undertaking and pick Remove. Advise yourself that the task isn’t gone, it’s simply not part of the arrangement. In the event that it diverts out you require something from it, you can utilize Add | Existing Item to get anything you’ve overlooked (you can likewise open the old venture in Visual Studio to check any settings you may have missed).
On the off chance that you don’t yet have a XAML document (other than App.xaml) in your new undertaking, right-tap on your new venture in Solution Explorer and select Add | New Item | Xamarin Forms | Content Page to include one. On the off chance that you need this to be your begin page, ensure this new Page’s name coordinates the name in the App class’ constructor in the App.xaml.cs document (you can either give your new XAML record a coordinating name or change the name in App.xaml.cs).