Hans Karlsen (talk | contribs) |
No edit summary |
||
Line 1: | Line 1: | ||
=== | === Background of the installer === | ||
VS 2022 extensions are not backwards compatible. [https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2022 Article with details] | |||
VS 2022 extensions are not backwards compatible. | |||
https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2022 | |||
For historic reasons, we have delivered MDriven as an installer exe - and not as is normal in VS a VSIX. | For historic reasons, we have delivered MDriven as an installer exe - and not as is normal in VS a VSIX. | ||
Line 10: | Line 6: | ||
Starting from VS2022, we will need to rewrite and target the VSIX instead of exe. | Starting from VS2022, we will need to rewrite and target the VSIX instead of exe. | ||
=== | === MDriven framework in VS2022 === | ||
You download the VSIX-installer file from [https://mdriven.net/downloads downloads on MDriven.net] | |||
Just run the file on the local computer to install or update the current installation. | |||
===== Referenced packages ===== | |||
If you reference MDriven packages in your code, you can use the file path <code>C:\Program Files (x86)\CapableObjects\MDriven\7.0\bin</code>, but going forward we recommend using our [[NugetProject|Nuget packages]]. | |||
=== VS2022: Error Generating Code/Changes Not Saving === | === VS2022: Error Generating Code/Changes Not Saving === | ||
Line 21: | Line 20: | ||
'''Solution:''' In the project's root folder, delete the hidden '''.vs''' folder that might contain the older backups of previous versions of VS. MAKE SURE you have checked in pending changes to GIT before deleting the .vs folder. | '''Solution:''' In the project's root folder, delete the hidden '''.vs''' folder that might contain the older backups of previous versions of VS. MAKE SURE you have checked in pending changes to GIT before deleting the .vs folder. | ||
[[File:2023-02-24 10h22 06.png|none|thumb]] | [[File:2023-02-24 10h22 06.png|none|thumb]] | ||
=== Building the Project (Admin and Developers) === | |||
Add an environment variable RevNumber and set this to a number like 123. This variable is used by the buildscript 2022BUILDMDrivenVSIX.cmd that will inject the number into a file source.extension.vsixmanifest based on the template source.extension.vsixmanifest.template. | |||
Later, the build engine will update the RevNumber from the svn version id. | |||
[[Category:Visual Studio]] | [[Category:Visual Studio]] |
Revision as of 09:03, 2 March 2023
Background of the installer
VS 2022 extensions are not backwards compatible. Article with details
For historic reasons, we have delivered MDriven as an installer exe - and not as is normal in VS a VSIX.
Starting from VS2022, we will need to rewrite and target the VSIX instead of exe.
MDriven framework in VS2022
You download the VSIX-installer file from downloads on MDriven.net
Just run the file on the local computer to install or update the current installation.
Referenced packages
If you reference MDriven packages in your code, you can use the file path C:\Program Files (x86)\CapableObjects\MDriven\7.0\bin
, but going forward we recommend using our Nuget packages.
VS2022: Error Generating Code/Changes Not Saving
Problem: If you recently upgraded to VS2022 and you have trouble saving your changes or got this error while trying to code generate, try this:
Model file "C:\_path_to_your_project\YourProject.ecomdl" belongs to the "Misc Files" project. Please add it to a real project, then close and reopen the editor tab
Solution: In the project's root folder, delete the hidden .vs folder that might contain the older backups of previous versions of VS. MAKE SURE you have checked in pending changes to GIT before deleting the .vs folder.
Building the Project (Admin and Developers)
Add an environment variable RevNumber and set this to a number like 123. This variable is used by the buildscript 2022BUILDMDrivenVSIX.cmd that will inject the number into a file source.extension.vsixmanifest based on the template source.extension.vsixmanifest.template.
Later, the build engine will update the RevNumber from the svn version id.