Google's documentation reads like stereo instructions and there are not many examples out there that can be used for guidance. Tokens and use them on subsequent requests. The complication was in the Authorization sequence and how to cache those The actual upload is very easy as Google provides all of the libraries for you to use.
(Google users can revoke authorizations to their Google Services in their user control panel.) Then silently upload the chosen file from then on provided the application remains authorized. The result is a pretty clean flow which will prompt the user the first time but Where my application differs from the other samples I found is that my application extends the Google sample code to store the authorization tokens and use them in subsequentĪccesses so the user is not prompted to authorize the application every time the program is run. If needed, it will open a browser so you can authorize the access and, provided you OK it, the program will upload the file you picked into your Google Drive. Select a file and the application will attempt to authenticate with Click the buttonĪnd an open-file dialog will prompt you to select a file to upload. The attached source code is a very simple WPF application that, when run, will open a window with a single button. So I started digging into the problem and when I found a solution, I felt that I should share it here. Although their sample worked, it required explicit authorization each time it was run and it didn't really address how
NET beyond a very simple sample providedīy Google. What I discovered was a lack of any documentation or working examples for doing this in. The purpose was to make the data easily accessibleįor later analysis in Excel or some other program. I wanted to have was the ability to store the data that the program logged into a user's Google Drive.
When designing my entry into the App Innovation contest (if you are interested, it is called Rev Warrior and can
0 kommentar(er)
