in

The ORM Foundation

Get the facts!

Visual Studio 2017 support

Last post Wed, Apr 24 2019 16:57 by Matthew Curland. 8 replies.
Page 1 of 1 (9 items)
Sort Posts: Previous Next
  • Wed, Oct 4 2017 14:23

    Visual Studio 2017 support

    I know it hasn't been out that long, but is there a plan for supporting Visual Studio 2017 with NORMA or will the VS 2015 version work with VS 2017?

     I realize that the project is being done by volunteers, and it is appreciated.  I rely on this tool and am upgrading to VS 2017 and wanted to see where the newest version of Visual Studio is on the road-map. 

  • Wed, Oct 4 2017 16:50 In reply to

    • Ken Evans
    • Top 10 Contributor
      Male
    • Joined on Sun, Nov 18 2007
    • Stickford, UK
    • Posts 789

    Re: Visual Studio 2017 support

     As you say, the NORMA upgrade to Visual Studio 2017 awaits volunteers to do the work.

    You can see the current status here.

    Please let me know of anyone who wants to help. 

    Ken 

  • Wed, Jan 24 2018 10:25 In reply to

    • evorobey
    • Top 100 Contributor
    • Joined on Fri, May 22 2009
    • Posts 4

    Re: Visual Studio 2017 support

     Dear Ken

    Why is NORMA being developed by volunteers? It is a part of VS, that is Microsoft's product, right? Are Microsoft interested in development of NORMA?

    Elena. 

     

     

  • Wed, Jan 24 2018 12:05 In reply to

    • Ken Evans
    • Top 10 Contributor
      Male
    • Joined on Sun, Nov 18 2007
    • Stickford, UK
    • Posts 789

    Re: Visual Studio 2017 support

    Hi Elena,

    NORMA is not “part of” Visual Studio (VS), NORMA is an extensionto VS.

    I discussed ORM with Microsoft’s Visual Studio manager in 2001 and my most recent contact with a person from Redmond was in late 2016. Much of Microsoft’s income is derived from selling licenses for their software. However, NORMA is open source and free. Microsoft stopped workon their own ORM project more than ten years ago.

    NORMA started life in 2005 as a University project led by Dr Terry Halpin and manyof Terry’s students made contributions to the code. In recent years, only Terry and Matt Curland have worked on the technical aspects of NORMA and Matt Curland’s most recent contribution is the VS 2015 release which is a free download. (Thanks Matt)

    However, some of the reported bugs have remained unresolved for more than ten years and having only one part-time developer is a big risk so in September 2016, I set up this JIRAproject to provide a structured environment that allowed more people to contribute.

    As many ORM users will tell you, ORM and NORMA are much more cost effective than alternative methods and some organisations such as the European Space Agency have got the message. We are making progress – albeit slowly.

     

    Ken

     

  • Mon, Jan 29 2018 14:45 In reply to

    • evorobey
    • Top 100 Contributor
    • Joined on Fri, May 22 2009
    • Posts 4

    Re: Visual Studio 2017 support

     Hello, Ken 

    Thank you very much for so detailed description of the current ORM status. 

    I believe that ORM is underestimated as by domain developers as by tool developers.

    ORM could add a significant value to any modelling tool. 

    I have been using ORM since 2002 year as my primary modelling tool and I appreciate your and your colleagues’ outstanding contribution to ORM. 

    Regards, Elena.

  • Sun, Apr 29 2018 17:10 In reply to

    • Ken Evans
    • Top 10 Contributor
      Male
    • Joined on Sun, Nov 18 2007
    • Stickford, UK
    • Posts 789

    Re: Visual Studio 2017 support

    Hi Elena,

    We are now testing NORMA for Visual Studio 2017.

    If you would like to test a pre-release version of NORMA for Visual Studio 2017, please send an email to vs2017@ormfoundation.org with a summary of your interest in ORM and how the VS2017 version will help you.

    Thanks

    Ken 

     

    Filed under:
  • Wed, Apr 24 2019 3:49 In reply to

    Re: Visual Studio 2017 support

     The official version of NORMA for Visual Studio 2017 is late, but Visual Studio 2019 is right on time.

     

    1. To install from inside Visual Studio, open the extensions dialog (Tools/Extension and Updates in 2017, Extensions/Manage Extensions in 2019)
    2. Click on the Online node on the left in the dialog.
    3. Search for NORMA
    4. Download and install the Natural ORM Architect extension as directed by Visual Studio.
    The extension is published by ORM Solutions and digitally signed by ORM Solutions, LLC.
     
    This integration with the Visual Studio Marketplace is meant to provide a much more natural NORMA integration and upgrade experience moving forward. Q&A is available in the marketplace. Issues and pull requests can be raised at https://github.com/ormsolutions/NORMA.
     
     
    -Matt 

     

  • Wed, Apr 24 2019 9:59 In reply to

    • Ken Evans
    • Top 10 Contributor
      Male
    • Joined on Sun, Nov 18 2007
    • Stickford, UK
    • Posts 789

    Re: Visual Studio 2017 support

    Hi Matt,

    Well done for publishing your "official" version of NORMA for Visual Studio 2019.

    Unfortunately, your VS2019 version still has the same long list of unresolved bugs (40+)  that are still present in your VS2015 version and in earlier versions. Even worse, my tests show that your VS2019 version has also introduced new bugs that are not present in the your VS2015 version.

    Some of the 40+ unresolved bugs were reported more than ten years ago.

    Do you intend to fix the bugs in your VS2019 version? 

    Ken 

    Filed under:
  • Wed, Apr 24 2019 16:57 In reply to

    Re: Visual Studio 2017 support

    Hi Ken,

    I went one item at a time through your list of the 74 issues. I found 15 where the comment text indicated actual code changes; the rest were evaluations of defects from years ago with no current code changes. If I missed some with actual code changes please expand the following. Of those 15:

    1. 4 were directly related to your 2017 installation process, so not existing defects
    2. 3 (40, 53, 95) are 'enhancements' that I would not pull into the master branch. I'm happy to discuss why on individual items.
    3. 7 (88,91,92,96,98,101,116) are small changes I can likely do in an afternoon without seeing your code changes.
    4. NOR-97 looks like the only issue with substantive code changes, but is clearly a design change and not a straight defect. I can't evaluate further without seeing the code, but this likely needs to occur as part of a broader initiative.
    If you have other issues, please report them individually, not in aggregate. Bug counts are just noise meant to introduce FUD and can clearly be misleading (note 7/74).
     
    Better yet, join the open source project by forking the github project and making pull requests. That's how millions of successful open source projects work. NORMA licensing (which I have carefully worked under and respected for years as the original copyright still belongs to Neumont University) states that you are welcome to make private changes to the core modules for your own use. However, as soon as you release the software publicly (which you have), you also need to release your code publicly (do you have a link?).
     
    I look forward to your specific feedback and continued contributions to NORMA.
     
    Thanks,
     
    -Matt

Page 1 of 1 (9 items)
© 2008-2019 The ORM Foundation: A UK not-for-profit organisation -------------- Terms of Service