Re: .Net standard target for Ignite.Net client
2.4 is expected in a couple of weeks: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-4-release-td26031.html On Mon, Jan 22, 2018 at 1:12 PM, Raymond Wilsonwrote: > Hi Pavel, > > That is very good news! :) > > When do you expect 2.4 to be released > > Thanks, > Raymond. > > Sent from my iPhone > > On 22/01/2018, at 9:22 PM, Pavel Tupitsyn wrote > > Hi Raymond, > > Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET > Core on Linux and macOS (as well as Windows). > However, we are not targeting .NET Standard, since it misses some crucial > things like DynamicMethod. > > Please make sure that you don't confuse .NET Standard and .NET Core: only > class libraries can target .NET Standard. > Actual applications target .NET Core. > > In my understanding, nothing should prevent you from doing dockerized > deployments on any OS with Ignite.NET 2.4. > You can try nightly build and see if it works for your environment: > https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds > > Thanks, > Pavel > > On Sun, Jan 21, 2018 at 11:55 PM, Raymond Wilson < > raymond_wil...@trimble.com> wrote: > >> All, >> >> >> >> Are there any plans for porting the current Ignite.Net client to .Net >> Standard? Has anyone investigated how much effort there would be involved? >> >> >> >> We would like to use dockerised deployments and as we use a .Net >> development stack .Net Standard is our target platform for those >> deployments. >> >> >> >> Thanks, >> >> Raymond. >> >> >> > >
Re: .Net standard target for Ignite.Net client
Hi Pavel, That is very good news! :) When do you expect 2.4 to be released Thanks, Raymond. Sent from my iPhone > On 22/01/2018, at 9:22 PM, Pavel Tupitsynwrote > > Hi Raymond, > > Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET Core on > Linux and macOS (as well as Windows). > However, we are not targeting .NET Standard, since it misses some crucial > things like DynamicMethod. > > Please make sure that you don't confuse .NET Standard and .NET Core: only > class libraries can target .NET Standard. > Actual applications target .NET Core. > > In my understanding, nothing should prevent you from doing dockerized > deployments on any OS with Ignite.NET 2.4. > You can try nightly build and see if it works for your environment: > https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds > > Thanks, > Pavel > >> On Sun, Jan 21, 2018 at 11:55 PM, Raymond Wilson >> wrote: >> All, >> >> >> >> Are there any plans for porting the current Ignite.Net client to .Net >> Standard? Has anyone investigated how much effort there would be involved? >> >> >> >> We would like to use dockerised deployments and as we use a .Net development >> stack .Net Standard is our target platform for those deployments. >> >> >> >> Thanks, >> >> Raymond. >> >> >> >
Re: .Net standard target for Ignite.Net client
Hi Raymond, Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET Core on Linux and macOS (as well as Windows). However, we are not targeting .NET Standard, since it misses some crucial things like DynamicMethod. Please make sure that you don't confuse .NET Standard and .NET Core: only class libraries can target .NET Standard. Actual applications target .NET Core. In my understanding, nothing should prevent you from doing dockerized deployments on any OS with Ignite.NET 2.4. You can try nightly build and see if it works for your environment: https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds Thanks, Pavel On Sun, Jan 21, 2018 at 11:55 PM, Raymond Wilsonwrote: > All, > > > > Are there any plans for porting the current Ignite.Net client to .Net > Standard? Has anyone investigated how much effort there would be involved? > > > > We would like to use dockerised deployments and as we use a .Net > development stack .Net Standard is our target platform for those > deployments. > > > > Thanks, > > Raymond. > > >
.Net standard target for Ignite.Net client
All, Are there any plans for porting the current Ignite.Net client to .Net Standard? Has anyone investigated how much effort there would be involved? We would like to use dockerised deployments and as we use a .Net development stack .Net Standard is our target platform for those deployments. Thanks, Raymond.