ErrrorUsing installed Noram with VS 2019

[cybersteer]

Hi
Please also see attached Word doc.
VS 2019 Community Edition is installed.
NORMA is installed.
When I go FILE > New >File and then select GENERAL > Object-Role Modeling File I get an error message
(See attached Errors.doc).
Thank you in advance for any help you can provide.
Very respectfully
Barry
650 380 1466
Errors.docx

[cybersteer]

Thank you for looking into this for me. Please feel free to call.

[mcurland]

This assembly is installed in the stock Visual Studio PublicAssemblies directory and is not one we track directly (see recent changes in 6fa0883 for dependency checks on assemblies that may not be installed in PrivateAssemblies). It appears that there are other similar issues in other products (for example, see https://github.com/microsoft/DataConnectors/issues/198) that occur when there are no Workloads installed. For NORMA code generation you'll need a .NET Framework workload (C# project, for example) installed at a minimum because this is the only way in NORMA to generate code from the model files.

Having said that the project does not actually use this assembly in VS2019 (or anything after VS2008) so there is really no reason to reference the assembly, and we build and run file without it. I'll add a conditional line to the assembly reference to remove the assembly dependency in versions where it isn't needed. The same fix likely needs to be applied to the database import wizard.

[cybersteer]

Sorry to appear dim but what should I do?

…

On Mon, Jul 27, 2020, 02:34 Matthew Curland ***@***.***> wrote: This assembly is installed in the stock Visual Studio PublicAssemblies directory and is not one we track directly (see recent changes in 6fa0883 <6fa0883> for dependency checks on assemblies that may not be installed in PrivateAssemblies). It appears that there are other similar issues in other products (for example, see microsoft/DataConnectors#198 <https://github.com/microsoft/DataConnectors/issues/198>) that occur when there are no Workloads installed. For NORMA code generation you'll need a .NET Framework workload (C# project, for example) installed at a minimum because this is the only way in NORMA to generate code from the model files. Having said that the project does not actually use this assembly in VS2019 (or anything after VS2008) so there is really no reason to reference the assembly, and we build and run file without it. I'll add a conditional line to the assembly reference to remove the assembly dependency in versions where it isn't needed. The same fix likely needs to be applied to the database import wizard. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOD6PJKBDF7SQUYBB45AKTR5UNXFANCNFSM4PHWWQZA> .

[mcurland]

Before I push a fix in please verify your configuration for me. I can remove the dependency for the basic ORM file, but the database import will always need this assembly, which means I would need to update setup to add a backup copy of the assembly plus possible assembly loading code just in case it isn't installed (similar to the change shown above) to support database import in this minimal VS environment. This isn't horribly difficult, I just need to verify the settings in your environment that are causing the problem before investing time in a fix.

First, please take a look at you installation.

1. In the start menu type 'developer'. You should see a link for a Developer Command Prompt for Visual Studio. This should open in the C:\Program Files (x86)\Microsoft Visual Studio\2019\Community directory.
2. cd Common7\IDE\PublicAssemblies
3. dir Microsoft.VisualStudio.TemplateWizardInterface.dll (if your getting this error then this should be an empty result)
4. You'll probably want to close the command prompt before applying updates (steps below).

Now lets look at your Visual Studio installation

1. Launch VS (if you're still in the Developer Command Prompt, just type devenv and press Enter)
2. At the top of the Tools menu click 'Get Tools and Features...'
3. Update the Visual Studio Installer if prompted
4. This should eventually open to a page for modifying Visual Studio Community 2019. The default tab there is called 'Workloads'
5. See what you have checked (if anything) and report back here.
6. NORMA code generation was designed for classic .NET C# and VB projects. There is now a newer project format, but the generators have not been updated to work in this environment. The easiest way to get something you can generate code from is to select '.NET desktop development'.

After setup has finished adding your component go back to PublicAssemblies and verify that Microsoft.VisualStudio.TemplateWizardInterface.dll is now there. When you relaunch VS your new ORM file should open cleanly.

[cybersteer]

Dear Matthew. Thank you for your email. RESULTS. File was not found. Under tab workloads nothing is checked. However under individual components Natural ORM Architect is checked. PLiX Code Generator is checked. Barry 650 380 1466

…

On Mon, Jul 27, 2020, 17:05 Matthew Curland ***@***.***> wrote: Before I push a fix in please verify your configuration for me. I can remove the dependency for the basic ORM file, but the database import will always need this assembly, which means I would need to update setup to add a backup copy of the assembly plus possible assembly loading code just in case it isn't installed (similar to the change shown above) to support database import in this minimal VS environment. This isn't horribly difficult, I just need to verify the settings in your environment that are causing the problem before investing time in a fix. First, please take a look at you installation. 1. In the start menu type 'developer'. You should see a link for a Developer Command Prompt for Visual Studio. This should open in the C:\Program Files (x86)\Microsoft Visual Studio\2019\Community directory. 2. cd Common7\IDE\PublicAssemblies 3. dir Microsoft.VisualStudio.TemplateWizardInterface.dll (if your getting this error then this should be an empty result) 4. You'll probably want to close the command prompt before applying updates (steps below). Now lets look at your Visual Studio installation 1. Launch VS (if you're still in the Developer Command Prompt, just type devenv and press Enter) 2. At the top of the Tools menu click 'Get Tools and Features...' 3. Update the Visual Studio Installer if prompted 4. This should eventually open to a page for modifying Visual Studio Community 2019. The default tab there is called 'Workloads' 5. See what you have checked (if anything) and report back here. 6. NORMA code generation was designed for classic .NET C# and VB projects. There is now a newer project format, but the generators have not been updated to work in this environment. The easiest way to get something you can generate code from is to select '.NET desktop development'. After setup has finished adding your component go back to PublicAssemblies and verify that Microsoft.VisualStudio.TemplateWizardInterface.dll is now there. When you relaunch VS your new ORM file should open cleanly. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOD6PLU32XYBE35L6CNE6LR5XTZ5ANCNFSM4PHWWQZA> .

[mcurland]

OK. Thanks for verifying that you have no workloads checked, that was my guess.

If you check and install the '.NET desktop development' workload are you able to create a new ORM file?

[cybersteer]

Dear Matthew, My heartfelt thanks. It all worked. I don't what i can do to say thank you but if i can ever be of any help. Please let me know. Sincerely, Barry

…

On Tue, Jul 28, 2020, 00:59 Matthew Curland ***@***.***> wrote: OK. Thanks for verifying that you have no workloads checked, that was my guess. If you check and install the '.NET desktop development' workload are you able to create a new ORM file? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOD6POBZ7XYELN5WV7QBPLR5ZLKLANCNFSM4PHWWQZA> .