-
Showing both flavors of the tool (Per User and the All Users admin-installed version) is problematic. The Marketplace writeup on the extensions makes it very clear this is a really bad idea (click on More Information in extensions, which also tells you the difference with the Per User version). It appears the VS team does not have schema writers ...
-
Expounding on this VS2017/VS2019/VS2022 versions of NORMA all install through Visual Studio Marketplace. There is no longer a separate download and traditional msi setup install.
Open the Visual Studio Extensions dialog (Tools/Extensions in VS2017, Extensions/Manage Extensions in VS2019 and VS2022).Select the Online section on the left of ...
-
You need to make sure you're working in a .NET Framework project to run the custom tool, not .NET Standard or .NET Core. The generator isn't currently supported in the other project types. If you see 'Dependencies' in the solution explorer then you're not in the right project type.
While I'd like to have this running there ...
-
It took a long time (and some pestering) for Microsoft to get back to me and then another chunk of time to find the issue, but we got it.
A small error in a build script copied the wrong PLiX.vsix file into the 64-bit version. The site was catching what the VSIX compiler and the VS installer both missed: the identifier of the embedded package did ...
-
Quick update:
The existing and PerUser versions were updated in the Marketplace for VS2019 and VS2017.
Unfortunately the correspond install files for VS2022 are currently being rejected by the marketplace site with a totally generic error message. I have absolutely no idea what the problem is.
I opened a ticket with Microsoft last week ...
-
Hello,
I'm very close to an official VS2022 version (digitally signed and ready to post to the Visual Studio store). You can see the latest commit at https://github.com/ormsolutions/NORMA.
Unfortunately there is always something that goes wrong between versions, especially with the 64-bit change for VS2022. The normal registration for ...
-
Hello Tye,
So, the difficulty on merging these files is that either a large part of these files (x.orm) or all (x.dcil.xml, x.ddil.xml) are generated, which makes merging difficult. The generated sections of .orm files also have non-stable identifiers, which makes them exceedingly difficult to merge.
It doesn't really matter if the ...
-
Hi Pete,
A lot of the limitations here are due to the underlying technology that NORMA is built on. The Microsoft Modeling Framework (formerly DSL tools) is an in-memory representation of the data with no native integration with external data sources (either other DSL Store objects or external databases). This means that any live coordination ...
-
Visual Studio 2017 is late, but Visual Studio 2019 is right on time.
To install, open the extensions dialog (Tools/Extension and Updates in 2017, Extensions/Manage Extensions in 2019)Click on the Online node on the left in the dialog.Search for NORMADownload and install the Natural ORM Architect extension as directed by Visual Studio.The ...
-
Hi Steve,
Please let me solve the mystery for you. There are not two verbalization engines, there is only one. The report generator simply uses a different set of 'verbalization snippets' to produce different styling for the report. Verbalization snippets are simply format strings with replacement fields, and all of the NORMA ...