Whiskers,
We've had a PR for the .NET 6.0 runtime pending for awhile, but has been
awaiting feedback from the original author and it has seems to have
become stale.
I've created a new PR for the runtime that is essentially just an
upgrade of what we've done in the .NET Core 3.1 runtime:
htt
All,
I'm glad this discussion is happening because I've been wanting to implement
some sort of automatic (de)serialization framework on the .NET runtime, which
requires additional libraries, etc., that provide the bare minimum requirements
to allow this.
Speaking as generic as I can, what I wo
n Wed, Dec 16, 2020 at 12:02 AM Shawn Black
wrote:
> Howdy, all!
>
> I wanted to get some feedback on the current state of .NET within the
> OpenWhisk ecosystem.
>
> Right now, we support .NET Core 2.2 (not LTS and no longer supported)
> and .NET Core 3.1 (LTS).
>
> .NET
Howdy, all!
I wanted to get some feedback on the current state of .NET within the
OpenWhisk ecosystem.
Right now, we support .NET Core 2.2 (not LTS and no longer supported)
and .NET Core 3.1 (LTS).
.NET 5.0 was recently released, but I would like to skip supporting this
version as it is no
+1 Approve the release
[+] Download links are valid.
[+] Checksums and PGP signatures are valid.
[+] Source code artifacts have correct names matching the current release.
[+] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[+] All files have license headers as specified b
+1
computing sha512 for openwhisk-runtime-dotnet-1.14.0-sources.tar.gz
SHA512: openwhisk-runtime-dotnet-1.14.0-sources.tar.gz:
2359D1BB 46C54D1A 5C637805 8D40E8D0 107F07B7 96C14B0C F9DE4CE8 B1A812DE DB9ACD86
1B37E72F 332AE5A2 00F23F63 63B931AF 07E96E7B 02288F8C A9EA9BD0
validating sha512... pass
checks out and the PR is completed then I say lets put it in
the 1.14.0 release :-).
Please let me know if you have any questions.
Thanks!!
Shawn
On 2019/12/18 20:35:18, "David P Grove" wrote:
>
>
> Shawn Black wrote on 12/18/2019 02:57:21 PM:
> >
> > Yes -- .N
Yes -- .NET 3.1 (LTS) was released and I was planning on migrating 3.0 to 3.1
and essentially skip having a 3.0 runtime.
I haven't had the time to yet due to work and the holiday schema, but it is a
simple change that I can knock out when I find an hour or two.
Thanks!!Shawn
On Wednesday, De
Howdy, all!
It's been awhile since I've done anything with OpenWhisk, but since Microsoft
released .NET Core 3.0 at the end of September, I figured I'd go ahead and get
the .NET Core runtime repo updated to support it.
The following PR has a handful of updates ...
Dotnet 3.0 by shawnallen85 · Pul
I believe the incubator-openwhisk-runtime-dotnet is good to go.
Happy Thursday!Shawn
On Thursday, February 21, 2019, 11:20:34 AM CST, Rodric Rabbah
wrote:
If you've contributed to one of these runtime repos please take a moment to
read this and also review the runtime repo that you've w
All,
Sorry for the long delay in response to this, but I just wanted to follow up.
For the .NET runtime, is Apache.OpenWhisk an acceptable namespace (similar to a
package name in the JVM world)?
While .NET namespaces are similar to Java packages in terms of purpose, they
differ in one area -- .N
OpenWhisk devs,
I created a new pull request for incubator-openwhisk-utilities to include .cs
files and ignore obj directories (binaries and code gen for dotnet builds).
https://github.com/apache/incubator-openwhisk-utilities/pull/51
Please let me know if you have any questions or concerns.
Thank
Howdy, all!
I would like to contribute the code for the .NET 2.1 runtime that I had demoed
earlier today during the 2018-10-10 Apache OpenWhisk Tech Interchange meeting.
The current GitHub repo is:
https://github.com/shawnallen85/openwhisk-runtime-dotnet
Thanks!!Shawn
Howdy,
I've been working on a dotnet 2.1 runtime for OpenWhisk and would like to show
what I've completed so far.
Using the runtime-docker and runtime-java as guides I have been able to build
the application and docker image and execute the base unit tests as well as
ones specific to the runtim
14 matches
Mail list logo
