Whew. I'm getting a nasty case of "rev-lock" here. Every direction I turn the various tools I want to use seem to be out of sync with every other tool. I think it's great that Microsoft is stepping up and iterating more quickly, I'm not sure if the rest of us can take the load.
I am locked into Windows Phone 8.1 because the project I'm starting requires Bluetooth LE support and that's only in Windows Phone 8.1. The BTLE support on the other MS platforms is pretty good as far as I can tell. But this is a mobile app and Windows Phones are the target.
So, I realize the no one's asking about WP specifically for CSLA, let alone WP8.1. Is there a plan at this point to address it specifically?
If I understand things correctly, the Universal App enhancement might solve this problem, but is there a timetable that can be shared for that?
Can anyone suggest an approach in the meantime that minimizes the lost time?
TIA - Bill
I thought Csla already supported WP 8. Isn't that one of the packages available?
My understanding is that Windows Phone 8 is supported, but I couldn't even get that to work. And no, I believe WP8 and WP8.1 are different animals. I am trying to avoid Silverlight because I don't want to spend time developing and learning the ins and outs when I probably won't deploy on that. Great product idea, though.
Yesterday I thought I'd just create a store app project that would allow me to add the CSLA Nuget packages just so I could get started building my model. In the time it takes me to do all that, I'm sure the landscape will change. Everything is in transition to a better world and in a few weeks all kinds of support will show up, like Telerik for WP8.1 and so on.
I spent about an hour trying to figure out which Nuget package to choose to add to my project. Never could get any of them to actually completely load without a red message telling me I was adding an unsupported package. So I gave up and just went back to thinking about the objects and their relationships for now.
If you work with all these tools all the time, I'm sure it seems very straightforward. Just an uphill battle getting started from scratch. And I'm not really lazy, just impatient. ;)
If WP8 Csla doesn't work it might be easy enough to grab the source for the Csla WP library, change it to WP8.1 and recompile. I believe that's pretty much what is done for mvc, as there usually isn't too much that really changes.
Windows Phone 8 (Silverlight 8) has been supported since it came out.
Windows Phone 8.1 (WinRT) support is in the latest beta and should be released in a couple weeks.
The biggest issue I had to deal with for 8.1 is that there's no WCF support on the new client, so I had to write a new data portal channel that doesn't rely on WCF.
That new HttpProxy/HttpPortal channel is also in the latest beta and is available for all platforms, not just WP8.1.
I see from your post that you aren't real familiar with Visual Studio.
To get at the beta release of CSLA you'll need to enable the use of pre-release code in the nuget add package dialog. There's a combobox at the top of the dialog where you can select 'stable only' or to use pre-release software. To get at the beta you'll need to enable the use of pre-release packages.
HOWEVER, now that I think about it, I don't think the WP8.1 WinRT code is in nuget yet because we haven't updated the nuget package definitions yet.
So perhaps your only option right now is to grab the CSLA source off GitHub and build it. Or look in the \Samples\Dependencies folder to see if I checked in test assemblies for WP8.1 WinRT.
Oh SNAP. I completely forgot that it would be in beta. I almost never use beta packages because I'm not capable enough to debug things and sort through the rough spots efficiently. I just now tried a store app with the beta setting and it worked great.
This will allow me to start my business classes and I'm pretty sure the framework pieces will be out of beta long before I'm ready to deploy anything.
Copyright (c) Marimer LLC