Update to Xamarin Forms 3.0

[bseebacher]

Side note - there are quite a few package updates pending in the current source code. Pulling them in breaks the build - probably something we should iron out before the hackathon.

[rockfordlhotka]

Totally agree - there've been substantial updates to a lot of packages beyond Xamarin. I planned to do these package updates prior to the codeathon, but if you want to take a run at it I'm happy with that too 😄

[bseebacher]

If my Xamarin skills ramp up a bit while I'm taking a stab at #210, maybe I will. Right now, I'm just happy that I can get a working build.

BTW, this solution less the UWP project loads and runs great on VS for Mac. I'm doing some iOS styling, and it saves on the debugger round trip.

[bseebacher]

Since I'm feeling adventurous, I decided to branch the current reference build and try updating all the packages, including Xamarin Forms 3. It's a bit early, but here are some highlights:

• The main App.xaml view in the core project appears not to be compatible with v3. The build throws this error: 'The type 'Application' does not support direct content.'. I assume this means there's a new way to set up the root views, but since I only dabble in Xamarin, I'll need to hit the books to figure that out. (Maybe @rockfordlhotka knows better here.)
• The Windows Azure mobile authentication library has also taken on a major version update. I think our calls are coded against an extension library that I haven't yet found the equivalent for. Once I dig that up, I assume things will just work, but we may find there's more to do here.
• I had to add the .NET Standard package to the device builds to support CSLA. No surprises there.

Unless the App.xaml thing turns out to be the first sign of larger UI changes, I don't see anything too crazy here; just your standard old .NET project package update fun.

[tlhotkamcm]

Thank you Brian!

From: Brian Seebacher [mailto:notifications@github.com] Sent: Wednesday, June 13, 2018 10:35 AM To: HTBox/MobileKidsIdApp MobileKidsIdApp@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [HTBox/MobileKidsIdApp] Update to Xamarin Forms 3.0 (#221)

Since I'm feeling adventurous, I decided to branch the current reference build and try updating all the packages, including Xamarin Forms 3. It's a bit early, but here are some highlights:

• The main App.xaml view in the core project appears not to be compatible with v3. The build throws this error: 'The type 'Application' does not support direct content.'. I assume this means there's a new way to set up the root views, but since I only dabble in Xamarin, I'll need to hit the books to figure that out. (Maybe @rockfordlhotka https://github.com/rockfordlhotka knows better here.)
• The Windows Azure mobile authentication library has also taken on a major version update. I think our calls are coded against an extension library that I haven't yet found the equivalent for. Once I dig that up, I assume things will just work, but we may find there's more to do here.
• I had to add the .NET Standard package to the device builds to support CSLA. No surprises there.

Unless the App.xaml thing turns out to be the first sign of larger UI changes, I don't see anything too crazy here; just your standard old .NET project package update fun.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/HTBox/MobileKidsIdApp/issues/221#issuecomment-396982105 , or mute the thread https://github.com/notifications/unsubscribe-auth/AQhupXcxLPTN7bt63KlFL1pqVJFK91yUks5t8TEjgaJpZM4UboQc . https://github.com/notifications/beacon/AQhupR2O9KII74nnolHQe0W4ozUSjpR_ks5t8TEjgaJpZM4UboQc.gif

---

This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

[bseebacher]

Update here: I now have a very rough build going on iOS and Android. I had to comment out the Azure login services (API changes) and the Android contact picker dependency service (plugin no longer maintained, see #224). I haven't started on UWP yet. Other than this, things are generally working - we'll just keep hacking.

You can see my work in progress here. https://github.com/bseebacher/MobileKidsIdApp/tree/221

[bseebacher]

I now have an updated build for UWP, but it will need a second look from @rockfordlhotka, as I had to pull CSLA-Core from the project in order to get it to build. When I had both this and CSLA-XamarinForms, the build throws this error:

The CSLA-Core free build produced no explosions in my very limited testing, but I'm pretty sure that's not going to hold. Luckily, I think @tlhotkamcm knows the guy who writes this library :)

Code here: https://github.com/bseebacher/MobileKidsIdApp/tree/221

[rockfordlhotka]

There's now CSLA-Core-NS that supports all platforms except full .NET on the server. The CSLA-Core package only supports full .NET on the server.

(and wouldn't be necessary except for an obscure bug in full .NET when supporting netstandard 😢 )

[rockfordlhotka]

@bseebacher HOLD OFF ON DOING MORE WORK for the moment - I'm going to convert all the projects to netstandard 2.0, which is kind of major surgery, but gets us the ability to use the latest frameworks and VS tool goodness.

[bseebacher]

Sounds good, @rockfordlhotka . I took a glance at doing that, but I didn't get very far.