Hello That’s really strange, I’ve been able to run it using Visual Studio 2015. But using Visual Studio 2017 (I’ve restarted the editor), I still get the issue.
Kind regards [cid:B4C12B98-8B1E-4E3E-9273-44D89CEED820] Mathias Herbaux mathias.herb...@xbrain.io <mailto:mathias.herb...@xbrain.io> Skype: mathias.herbaux xbrain.io<http://xbrain.io/> From: Pavel Tupitsyn [mailto:ptupit...@apache.org] Sent: Friday, 15 June, 2018 14:00 To: user@ignite.apache.org Subject: Re: DotNet version issue Invalid flag value: 0 I am able to clone that repository and run the application as is, it works. Please check again that no IGNITE_ environment variables are set. Environment variable changes take effect only when you re-open the application (Visual Studio, etc). You can log off to make sure. PS Do not put NuGet packages and binaries into the source control. packages.config is enough. On Fri, Jun 15, 2018 at 8:21 PM, Mathias Herbaux <mathias.herb...@xbrain.io<mailto:mathias.herb...@xbrain.io>> wrote: Hello, Here’s the solution on github https://github.com/mathrb/test_ignite Kind regards Mathias Herbaux mathias.herb...@xbrain.io <mailto:mathias.herb...@xbrain.io> Skype: mathias.herbaux From: Pavel Tupitsyn [mailto:ptupit...@apache.org<mailto:ptupit...@apache.org>] Sent: Friday, 15 June, 2018 01:35 To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: DotNet version issue Invalid flag value: 0 Can you please post your entire solution? On GitHub or any other way. On Fri, Jun 15, 2018 at 12:28 AM, Mathias Herbaux <mathias.herb...@xbrain.io<mailto:mathias.herb...@xbrain.io>> wrote: Hello Pavel, Thanks for the reply. I removed the IGNITE_HOME from my environment vars. I still get the same issue with a fresh project, installing ignite 2.5 from NuGet, and with only Ignition.Start() Using the solution from the official repo, I’ve got another error when I start Apache.Ignite.examples project: Java class is not found (did you set IGNITE_HOME environment variable?) Thanks [cid:B4C12B98-8B1E-4E3E-9273-44D89CEED820] Mathias Herbaux mathias.herb...@xbrain.io <mailto:mathias.herb...@xbrain.io> Skype: mathias.herbaux xbrain.io<http://xbrain.io/> From: Pavel Tupitsyn [mailto:ptupit...@apache.org<mailto:ptupit...@apache.org>] Sent: Monday, 11 June, 2018 05:09 To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: DotNet version issue Invalid flag value: 0 Hi Mathias, Can you please post your entire solution? On GitHub or any other way. This error is likely caused by mismatching JAR versions, so make sure you have no IGNITE_HOME set. Thanks, Pavel On Sat, Jun 9, 2018 at 12:33 AM, Mathias Herbaux <mathias.herb...@xbrain.io<mailto:mathias.herb...@xbrain.io>> wrote: Hello, I’m trying to run a sample with Apache Ignite 2.5. I’m using Visual Studio 2017, and NuGet to add ignite to my console project. I unchecked the “Prefer 32-bit” in the project properties. When running the project, I get the following error: An unhandled exception of type 'Apache.Ignite.Core.Binary.BinaryObjectException' occurred in Apache.Ignite.Core.dll Additional information: Invalid flag value: 0 .Net stack : at Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck() at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.IgnitionStart(Env env, String cfgPath, String gridName, Boolean clientMode, Boolean userLogger, Int64 igniteId, Boolean redirectConsole) at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg) Message: class org.apache.ignite.binary.BinaryObjectException: Invalid flag value: 0 at org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1995) at org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1334) at org.apache.ignite.internal.processors.platform.utils.PlatformConfigurationUtils.readIgniteConfiguration(PlatformConfigurationUtils.java:623) at org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.processPrepareResult(PlatformDotNetConfigurationClosure.java:199) at org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.prepare(PlatformDotNetConfigurationClosure.java:186) at org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.apply0(PlatformDotNetConfigurationClosure.java:113) at org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:50) at org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:27) at org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:40) at org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75) Before 2.5, I successfully used the 2.4 version. To be sure it’s not an upgrade issue, I started from scratch with a new solution. I also tried using the sample solution from the git repository, but I got exactly the same issue Any advice about this? Mathias Herbaux mathias.herb...@xbrain.io <mailto:mathias.herb...@xbrain.io>
