Closed GoogleCodeExporter closed 9 years ago
Read more:
http://blogs.msdn.com/b/visualstudio/archive/2014/04/14/using-visual-studio-to-b
uild-universal-xaml-apps.aspx
http://blogs.msdn.com/b/dotnet/archive/2014/04/30/get-your-libraries-ready-for-w
indows-phone-8-1.aspx
Original comment by pele...@google.com
on 6 Jul 2014 at 9:31
https://code.google.com/p/google-api-dotnet-client/source/detail?r=c12653247d5ce
5e6782d3c210f9bf7f26d8a4ede
Original comment by pele...@google.com
on 28 Jul 2014 at 12:50
Issue 461 has been merged into this issue.
Original comment by pele...@google.com
on 31 Jul 2014 at 2:51
Issue 461 has been merged into this issue.
Original comment by pele...@google.com
on 31 Jul 2014 at 2:55
JSON.NET was upgraded to 6.0.4.
Now:
1. Create Windows 8.1 Portable extension
2. Update nuspec files
3. Update the profile on the generated client libraries
Original comment by pele...@google.com
on 3 Aug 2014 at 8:54
Here's my current work. WebAuthenticationBrokerUserControl.xaml.cs is not
finished yet, the rest should work fine.
https://drive.google.com/folderview?id=0B16Ld_4e5TuARzNrcU9pYXBxS3c&usp=sharing
I wasn't able to upload the files directly (HTTP error 500)
Original comment by l1234567...@gmail.com
on 4 Aug 2014 at 9:10
Issue 469 has been merged into this issue.
Original comment by pele...@google.com
on 9 Aug 2014 at 2:29
Hi,
As I see you have several issues yet. I've 15 erros.
I'll try to check what you did and solve that with solution that will replace
the WinRT assembly eventually.
I'll be happy to get your help in this one.
Thanks!
Eyal
Original comment by pele...@google.com
on 11 Aug 2014 at 9:45
I think that you targeted Windows Phone 8.1 while I want to target Windows 8.1
and Windows Phone 8.1.
Your project is different then the one I tried to make using your code.
my csproj contains the following:
<TargetFrameworkProfile>Profile32</TargetFrameworkProfile>
While yours:
<TargetPlatformVersion>8.1</TargetPlatformVersion>
As a result most of the code doesn't compile.
Did you create a new Class library (Portable for Universal Apps) project or is
it some other kind?
Thanks
Original comment by pele...@google.com
on 11 Aug 2014 at 9:50
Windows phone 8.1 does not stand for the old windows phone apps (they are
called something like Silverlight for WP 8.1) but for the windows phone
component of universal apps. Universal apps are mostly the same for WP and win8
apps but some areas differ. One of them is the class that is used in the WinRT
component of this lib. There is a equivalent API for WP 8.1 but its using
strange andContinue methods that are pretty much useless in this scenario. A
universal app is not just one app project, but rather two apps that have a
mostly shared core. That's why I choose to provide different libs for the
different platforms. One could also provide one lib only that uses compiler
flag. So my project structure is the way it is supposed to be.
Original comment by l1234567...@gmail.com
on 11 Aug 2014 at 10:33
I think I found a bug in my own code: In line 51 of
WebAuthenticationBrokerUserControl.xaml.cs I think it should be true instead of
false.
Original comment by l1234567...@gmail.com
on 11 Aug 2014 at 10:44
When I tried to copy your code into a universal portable library (I created
a new project like I mentioned before), the code didn't compile.
I'm not an expert in universal app, but as I understand I would want to
create a universal portable dll that will be shared between wp and windows
8.1. (Just like our
Google.Apis PCL).
Makes sense?
On Mon, Aug 11, 2014 at 3:44 PM, <google-api-dotnet-client@googlecode.com>
wrote:
Original comment by pele...@google.com
on 11 Aug 2014 at 11:14
No that was exactly what I tried to explain. Universal Apps share the same APIs
but they are not exactly the same on both platforms. If you create a universal
app in vs 2013 (with update 2) then there are 3 projects: the shared code, the
WP code and the win code (but the WP part is not the same you get when you only
create a WP project). The shared code has no references, so you have to add a
win 8.1 compatible reference to the win 8.1 project and a WP 8.1 compatible
reference to that project. I know this is really confusing.
So you have two possibilities for creating the lib. You kann create a single
project or to different. The problem is that the code base is mostly shared but
not always (for example when using the given OAuth implementation; the WP
variant is useless).
So I decided to port over the old WP Silverlight code to non Silverlight WP 8.1
(which is used in universal apps).
I hope I could help you with this. If you still don't understand what I mean,
then try to create a universal app yourself and compare it to a WP Silverlight
app
Original comment by l1234567...@gmail.com
on 12 Aug 2014 at 8:14
I'm still not sure why it doesn't compile in my end.
Do you have time to set a hangout together?
You can ping me your personal email (privately.. to peleyal@google.com) and
we can take it from there.
Thanks!
Eyal
On Tue, Aug 12, 2014 at 4:14 AM, <google-api-dotnet-client@googlecode.com>
wrote:
Original comment by pele...@google.com
on 18 Aug 2014 at 2:29
I just talked to l1234567890987654321l, and we agreed that we should work on
using the suspension and continuation managers in order to support
authentication in WP8.1 application.
Useful links:
http://msdn.microsoft.com/en-us/library/dn631755.aspx
http://dotnet.dzone.com/articles/how-use
Original comment by pele...@google.com
on 19 Aug 2014 at 1:43
A new sample was created, it's currently under review -
https://codereview.appspot.com/168160043/
Original comment by pele...@google.com
on 4 Nov 2014 at 6:20
Original comment by pele...@google.com
on 10 Nov 2014 at 10:18
https://codereview.appspot.com/168160043/ was submitted.
It contains a full sample for universal app.
Next: create Google.Apis and Google.Apis.Auth projects for Windows Phone 8.1
Original comment by pele...@google.com
on 11 Nov 2014 at 8:26
https://codereview.appspot.com/176220043/
Original comment by pele...@google.com
on 24 Nov 2014 at 11:41
Original comment by pele...@google.com
on 25 Nov 2014 at 3:30
Original comment by pele...@google.com
on 15 Dec 2014 at 12:59
Original issue reported on code.google.com by
kkband...@gmail.com
on 26 Jun 2014 at 2:06