Quantcast
Channel: Recent Threads — Xamarin Community Forums
Viewing all articles
Browse latest Browse all 204402

A lot of issues (unstable) with Xamarin.forms in Visual Studio 2017

$
0
0

Hi there,
I have a lot of issues with Xamarin.forms in VS 2017, not a single problem, but maybe someone can see a cause, and solution?

This summer I reinstalled my old PC and installed VS 2017. Trying to start using Xamarin forms, but it just don't work.
Now I reinstalled VS2017 again, but I get similar behavior.

I try to create a new project (name App5): Cross platform App (Xamarin) with code sharing: Shared Project.

Directly I get an error in my error list saying: The name 'InitializeComponent' does not exist in the current context
It's pointing at project App5.UWP and file MainPage.xaml.cs (when I double-click I get to the file under the shared project App5).

I'm trying to add an event in the shared MainPage.xaml:

<Label Text="Welcome to Xamarin Forms!" x:Name="Mylbl" />
<Button Clicked="Button_Clicked" MinimumHeightRequest="50"></Button>

In the event:

private void Button_Clicked(object sender, EventArgs e)
        {   Mylbl.     }

The intellisense didn't find Mylbl.
Then after messing around several minutes, it just worked.

A can also see I have two MainPage.xaml and App.xaml. Under the shared project App5, and under App5.UWP.
Maybe that is correct, but it's confusing, why these also exists under App5.UWP. Can someone explain?
When I above the MainPage.xaml editor, change from App5.Android to App5.UWP all types "was not found", eg ContentPage, Stacklayout etc.

The good thing is that I can run the UWP project, with all these errors.

So that was some of my problems with the environment. It's extremely unstable!!!
Should I reinstall my PC again? Is it to old (probably five years old HP with i7 2GHz 12GB)?
Please help! My development project is standing still!
BR /Magnus


Viewing all articles
Browse latest Browse all 204402

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>