Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F36EE19137 for ; Mon, 21 Mar 2016 12:29:25 +0000 (UTC) Received: (qmail 24525 invoked by uid 500); 21 Mar 2016 12:29:25 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 24410 invoked by uid 500); 21 Mar 2016 12:29:25 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 24388 invoked by uid 99); 21 Mar 2016 12:29:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Mar 2016 12:29:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 96CE12C1F5D for ; Mon, 21 Mar 2016 12:29:25 +0000 (UTC) Date: Mon, 21 Mar 2016 12:29:25 +0000 (UTC) From: "Pavel Tupitsyn (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-2694) .NET: AnyCPU build MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204066#comment-15204066 ] Pavel Tupitsyn edited comment on IGNITE-2694 at 3/21/16 12:29 PM: ------------------------------------------------------------------ QA info: * There is now a single set of binaries in the distribution (platforms/dotnet/bin no longer has x86 folder) * These binaries can be used both in x86 and x64 modes. Mode depends on the parent application platform and OS. ** "Parent app" is the application that uses Ignite.NET binaries. Bundled examples are such an application. ** If the parent app is x86, or OS is x86, then Ignite runs in x86 mode ** If the parent app is x64, then Ignite runs in x64 mode ** If the parent app is AnyCPU (examples are), then the OS defines execution mode => To test examples in x86 mode, either use x86 OS, or add x86 solution configuration via Build->Configuration Manager menu (don't forget about proper JAVA_HOME). By default, examples solution should only have AnyCPU build platform. was (Author: ptupitsyn): QA info: * There is now a single set of binaries in the distribution (platforms/dotnet/bin no longer has x86 folder) * These binaries can be used both in x86 and x64 modes. Mode depends on the parent application platform and OS. ** "Parent app" is the application that uses Ignite.NET binaries. Bundled examples are such an application. ** If the parent app is x86, or OS is x86, then Ignite runs in x86 mode ** If the parent app is x64, then Ignite runs in x64 mode ** If the parent app is AnyCPU (examples are), then the OS defines execution mode => To test examples in x86 mode, either use x86 OS, or add x86 solution configuration via Build->Configuration Manager menu (don't forget about proper JAVA_HOME). > .NET: AnyCPU build > ------------------ > > Key: IGNITE-2694 > URL: https://issues.apache.org/jira/browse/IGNITE-2694 > Project: Ignite > Issue Type: Improvement > Components: platforms > Affects Versions: 1.1.4 > Reporter: Pavel Tupitsyn > Assignee: Vasilisa Sidorova > Fix For: 1.6 > > > Currently we provide separate x86 & x64 binaries. NuGet is x64-only. > This is inconvenient both for us and the user. > The only thing that prevents AnyCPU is unmanaged "common" project. > But we load it dynamically from resources, and we may as well detect current process platform (x64 or not) and load a proper unmanaged resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332)