eventhas.blogg.se - The name contentpage does not exist xamarin visual studio

#The name contentpage does not exist xamarin visual studio code#
#The name contentpage does not exist xamarin visual studio windows#

So probably a simple ContentPage will suffice here. As described before, this will contain just a text about the company. We can create these pages like we did with the first one, and of course in our Pages folder.

LocationPage: a page showing a map with our locations and some contact information.

EmployeesPage: a page with a list of our wonderful employees.

GeneralPage: a page with just a description.

So let’s create some.Īs you may have noticed I already created a few in the screenshot above. The children of a TabbedPage, which will become the actual tabs, can be any type of other pages. Xmlns:pages="clr-namespace:FourDotNet.Pages assembly=FourDotNet" x:Class=""> The start and end tag we modify to, lose the label and replace it with Children of the ContentPage.Īfter we’re done with it, this is what is looks like: So let’s open up the MainPage.xaml and start editing. The standard XAML page contains just a ContentPage with a centered label, what we are after is a TabbedPage with three tabs. Of course don’t forget to include the right namespaces and for your convenience I’ve omitted the rest of the methods in the class.

#The name contentpage does not exist xamarin visual studio code#

FourDotNet Project treeĪnd the code in my App.cs looks like this: I’ve already created some more pages in the screenshot underneath. To keep things neat I’ve created a folder to contain my pages instead of just putting them in the root.Īfter I did this my FourDotNet project looks like this:

#The name contentpage does not exist xamarin visual studio windows#

Also awesome but for me the CarouselPage feels too much like the native Panorama Windows Phone control.įirst thing I did was create a XAML page, MainPage.xaml, in the shared project, FourDotNet, and change the App.cs to use is. Let’s check out the CarouselPage just in case. NavigationPage manages a stack of pages, doesn’t fit for now.

The MasterDetailPage is a viable option, but since the app won’t have too much content, the ways to navigate within a MasterDetailPage seemed to devious. The ContentPage seemed a little to marginal for the goals I wanted to achieve. The first question arises: what layout to choose?Īs we saw in my last post there are a number of different pages already provided by Xamarin. So as a solution name I choose FourDotNet to get around it. The name of the company I work for is 4DotNet which, as it turns out, is a toughie while coding because you can’t start class names and variables etc. So start Visual Studio, create a new project, give it a name and wait a while for all the projects to be generated. Make it so! Buckle your seatbelt Dorothy, ‘cause Kansas is going bye-bye!īecause of my research I knew what project template to choose to satisfy my needs. The second one wasn’t really a goal in itself, but by providing relevant and fun content in a sexy UI I would hope to persuade potential customers to choose for us. The user would be able to contact us from anywhere within the app when they are (finally) convinced of our epic skills. Just incorporate a call and e-mail button on every page elegantly. The first ‘requirement’ would be easy to solve.

Overview of the employees and some details about them Īfter applying some common sense I figured that since I was creating a digital business card of sorts, the main goal – as a end-user – would be to be able to contact us ASAP and – as a company – create possible sales opportunities.

General description of what we do how and why we do it at all.

With the little knowledge I had upfront I knew I wanted to use XAML for my markup, the app had to be as multi-platform as can be, the code base had to be shared as possible and because it was a first for me with Xamarin I didn’t want to do a lot of fancy stuff right away. In the post before this I have told you about the different project templates you get to choose from to build a Xamarin app. No need? Just skip to the next heading then! Previously on As The World Blogs… In this continuing post I will put things in perspective for you and describe how the app has taken shape, which decisions I’ve made (and why) and the sleepless nights I’ve had because of stuff that didn’t work.įirst let’s refresh your memory a bit. In the meanwhile I have been working on this app to get it ready for the App Store, Market and/or Play Store. There I have described that my first app would be a business app for the company I work for. In my previous post I have covered the basics of starting with Xamarin, more specific Xamarin.Forms.