Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support .NET Core 1.0 #695

Closed
OlsonDev opened this issue Mar 9, 2016 · 12 comments
Closed

Support .NET Core 1.0 #695

OlsonDev opened this issue Mar 9, 2016 · 12 comments
Assignees

Comments

@OlsonDev
Copy link

OlsonDev commented Mar 9, 2016

Apologies if this is the wrong place to ask.

When/will there be support for DNX Core 5.0 .NET Core 1.0?

@henkmollema
Copy link

Any update on this?

@jskeet
Copy link
Collaborator

jskeet commented May 23, 2016

It's definitely something we're interested in, but no firm plans/timescales yet I'm afraid.

@henkmollema
Copy link

henkmollema commented May 23, 2016

I was just about to ask you on Twitter Jon 😄

Using imports in project.json, I am able to restore the packages. However, it looks like one of the blockers now is ServiceAccountCredential. Any idea why that is not available on .NETStandard?

@tkrotoff
Copy link

tkrotoff commented Jun 8, 2016

This would allow to run the code under Windows, OS X and Linux (.NET Core => multiplatform vs .NET Framework => Windows only).

@OlsonDev OlsonDev changed the title Support DNX Core 5.0 Support .NET Core 1.0 Jun 8, 2016
chrisdunelm added a commit that referenced this issue Jul 18, 2016
Adds netstandard1.3 support to the support libraries. Initial commit for #695
@ipoley
Copy link

ipoley commented Jul 26, 2016

Can these libraries be used in a .NET Core application yet? I'm also having trouble getting ServiceAccountCredential to work correctly in the following snippet.

ServiceAccountCredential sCredential = new ServiceAccountCredential(
    new ServiceAccountCredential.Initializer("someone@gmail.com")
    {
        Scopes = new[]
        {
            CalendarService.Scope.Calendar,
        },
        User = "someone@gmail.com"
    }.FromCertificate(certificate));

It looks like the closest match is ServiceCredential, however just swapping ServiceCredential for ServiceAccountCredential does not work, either. Any help is appreciated.

@jskeet
Copy link
Collaborator

jskeet commented Jul 26, 2016

No, they can't - at least not in any released Nuget packages. I think we're hoping to get netstandard1.3 support into the next release (so 1.15) but Chris may be able to correct me.

@henkmollema
Copy link

@ipoley

ServiceAccountCredential does not work because package uses Windows-specific API's to parse the certificate (FromCertificate). This has to be implemented cross-platform first to get API calls with service accounts working.

@chrisdunelm
Copy link
Contributor

chrisdunelm commented Jul 28, 2016

Yes, we hope to get netstandard1.x support into 1.15, which will add support .NET core; we don't have a firm date for this. ServiceAccountCredential will almost certainly be supported.
The 1.14 libraries do not support .NET core.

The .NET core work is being done the in netcore branch in this repo.

chrisdunelm added a commit that referenced this issue Aug 4, 2016
* NetStandard1.3 (#769)

Adds netstandard1.3 support to the support libraries. Initial commit for #695

* Generated libraries target netstandard1.3 (#772)

#695

* Fix NetStandard build (#773)

Perform nuget restore for all NetStandard projects before build

* Netcore tests (#774)

Adding scripts, and project.json definitions for .NET Core test projects. The .NET Core projects only test the .NET Core compatible code.

* Improve build (#782)

Add NuGet.Config; use local package repository for all builds; fix XML comment issue

* Tidy up NetStandard1.3 build gened libs (#783)

Fix nuget restore for netstandard1.3, and improve .proj files

* Fix support library dependecies (#784)

Replace NetStandard.Library deps with explicit dependency list

* Netcore test improvements (#788)

* Improve .NET core testing

Enable ~100 more GoogleApis.Tests test-cases in .NET core. Tidy up project.json's. Remove unneeded Moq & Ionic.ZLib dependencies from test project. Tidy up run_tests_dotnetcore.bat.

* Authtest improvements

Enable all auth tests in NET core, by using alpha Moq support for core.

* Adding travis runner (#789)

* Adding the test runner container.

* Adding the script to run the tests in a container.
* Fixing NuGet.Config to use v2 of the Nuget protocol.

* Removing the unnecessary files. (#790)

* Better NET Core testing (#792)

* Better NET Core testing

Implement a minimal HttpListener so all HTTP-based tests can now run on core.

Remove NET core tests for the moment that require internal access to libraries

Sign netstandard libraries

Delete cached Google.* packages before restoring NET Core tests

* Appveyor support for the repo. (#793)

* Remove ServiceAccountCredentials from netstandard (#794)

Due to missing platform support.

Also temporarily remove tests that run slowly on appveyor.

* Update version 1.14.1 -> 1.15.0
@chrisdunelm
Copy link
Contributor

v1.15.0 has just been released which adds a netstandard1.3 target to all Google.Apis.* packages :)

Please open new issues if you experience any problems when using these libraries on .NET Core.

@henkmollema
Copy link

@chrisdunelm seems like ServiceAccountCredential is still not ported. Is that true?

@chrisdunelm
Copy link
Contributor

@henkmollema You are correct, ServiceAccountCredential is not available in netstandard/NETCore.
This is because it uses cryptographic classes (E.g. RSACryptoServiceProvider) that are not available on some netstandard platforms (e.g. Linux). See #758 for more details.

@henkmollema
Copy link

@chrisdunelm I see. I also just opened an issue: #797. You can close it if you consider it a duplicate of #758.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants