From dev-return-64240-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Thu Feb 15 21:54:46 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id CB6E118064A for ; Thu, 15 Feb 2018 21:54:45 +0100 (CET) Received: (qmail 96969 invoked by uid 500); 15 Feb 2018 20:54:44 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 96953 invoked by uid 99); 15 Feb 2018 20:54:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 20:54:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A6C8C1800D6 for ; Thu, 15 Feb 2018 20:54:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.129 X-Spam-Level: * X-Spam-Status: No, score=1.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, KAM_LIVE=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id BVWuraKlrWDt for ; Thu, 15 Feb 2018 20:54:40 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id AC5A85F174 for ; Thu, 15 Feb 2018 20:54:40 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id c4so1330713qkm.2 for ; Thu, 15 Feb 2018 12:54:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=TYv9h2nJw/+f9ZCJoAxbYfUACydy0WzI6rkoaW++/9U=; b=svKdO2WwAbXl12wiccRkeXwW6ku+PHFv+HqPBL/DASxQiLOzE6637qSqqr2mID0uHP drx9yFpz3hr+IwWcv00+to7mJ1vXENSvMoVNbzmOBal0fzUtKGWXit3EL7593KUc3EqY 9ONveWsGtk1uk6UIqq5vshTq7ZCodyIQIEKKjxXMpibjJ34Niei0KyAm4g1xEhA69iL1 gCX+RMfrU1cyzLpAD2o7v2sTmLiK7GTyUsWz8MpULW7h3KSXWUmmeKh+Q+zmLtgg09kc lVZeiinuJF7D8ItiUSCrzDM+OzBD6f32PO7cE8PrIIogNbTF9oiRXsDpHmnG121qN0gi /MFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=TYv9h2nJw/+f9ZCJoAxbYfUACydy0WzI6rkoaW++/9U=; b=bvU9VdkiUu/LpZ3xZfPjcHzV5501iAJvOTMDW07QnAdnYkX65/H/IiRIzw4VWfEweh CDCFTyTEYrdiU6vASaZz7Uybz43uFQ3kG15A1qZSERnr9sNYec6sL0sHNzNqkteDn4ll iCsuvldPEA2W5nJFp+Ric2hasH7ivtxYa4ACLFORe5YGzSdicjhmglpjOe4/f+7JKxKk dg0O1ixMJJp8xGgYmB7oKpgW4TJWU2p/MGxzMFZhOedBiPvDe7EUJehZGucdlbGLt1O1 jO0uPOnsOIdVD2yBa/H95TVYKFds3Fdm6Z0dqcndF+H+hAjYXHbeRDDLlgyYLTNkIH4a 878A== X-Gm-Message-State: APf1xPCGm/UJ1gWLw02fEL5IwVWu0G1m+PaSOIbDY/w6nQyXugr5zC6N Jxlkr/RayARrKTaGIu1ybxL/YCgX X-Google-Smtp-Source: AH8x225PLjfSbf4gmbiDwLbNbtnFzRHUc2fbLhArgJGX48H8C7QCsrW1WBKJe4nvJQfvvMZu4d/NSg== X-Received: by 10.55.133.131 with SMTP id h125mr6300090qkd.79.1518728074095; Thu, 15 Feb 2018 12:54:34 -0800 (PST) Received: from [192.168.2.150] (c-69-143-96-107.hsd1.md.comcast.net. [69.143.96.107]) by smtp.googlemail.com with ESMTPSA id z8sm926488qta.83.2018.02.15.12.54.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Feb 2018 12:54:33 -0800 (PST) Subject: Re: [DISCUSS] Rework NMS.AMQP To: dev@activemq.apache.org References: <1489591866396-4723793.post@n4.nabble.com> <3231fca1-6b2c-250f-06fc-5249c092f532@gmail.com> <1516222239944-0.post@n4.nabble.com> <54ccf9b2-ddb9-d1b5-a6f4-82f9835cc619@gmail.com> <1518647308276-0.post@n4.nabble.com> From: Timothy Bish Message-ID: Date: Thu, 15 Feb 2018 15:54:32 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US On 02/15/2018 11:57 AM, Duane Pauls wrote: > In particular, I think we are wondering whether it would be considered > feasible to work towards an initial release with the VS2017 project and > solution files. This would require those who want to build it to either > use VS2017 to build, or to use the dotnet sdk tool, as is described in the > 'Building' section of the README.md. > > If not considered a gating item for release, we would definitely consider > it as a future enhancement if this would be perceived to be of value. > > Cheers, > Duane > > On Wed, Feb 14, 2018 at 5:28 PM, cmorgan > wrote: > >> Hi everyone, >> >> Tim's post about not having a platform to run Visual Studio 2017 recently >> sparked a discussion between Duane, Ragnar and I about adding project and >> solution files for older versions of visual studio to the NMS AMQP Provider >> and were looking for guidance. >> >> Currently, the project only contains visual studio 2017 project and >> solution >> files. This was chosen among other things to, 1) reduce the number of of >> project files by using the new csproj format multi-target framework >> capabilities, and 2) leverage the nuget package integration in the new >> csproj format. Other providers seem to contain whatever visual studio files >> they need to build. There were two points of discussion that we are >> looking >> guidance in. >> >> 1) Is visual studio 2017 too new to expected a wide variety of developers >> to >> be able to pickup and look at this project? Does anyone have any insight >> into this? >> >> 2) Is there an automated system that depends on building tools that predate >> visual studio 2017 equivalent build tools? Would it easier for CI builds if >> there were project/solution files that can be built with tools the predate >> vs2017? If this is not the right place to ask this, then where should I ask >> this? >> >> Based on the feedback from the above two points we'd like to come to a >> decision on adding project/solution files for previous Visual Studio >> versions for initial release of the new AMQP Provider. >> >> If anyone has any question about this please let me know. >> >> Chris Morgan >> I don't think there's anything inherently wrong with only including VS2017 solution files if that' the tool you are using right now for development.  In the end some things would need to be figured out though like how someone builds it and package it from the CLI if possible as that is the current workflow for the other NMS libraries although they are using Nant which is pretty much dead at this point. One thing to look at is the baseline build environment set by the AmqpNetLite project which your client is leveraging underneath. Does it use files from an older VS release, it sort of looks like it to me but I've not messed with Windows or .NET in a couple years now so I'm a bit out of the loop.  If someone needs more tools to build the dependent library than they need to build the NMS.AMQP library that could be frustrating to some. -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/