12/27/2022 0 Comments Enscape revit existing conditionsI already read before the RI code when I was doing some automating plug-ins for Grasshopper using RI & Revit, I had many ideas to ameliorate some details at that time & I understood the architectural pattern and the reversal logic used through the conditional compilation. I understand them all very well & I had some experiences with all such. Thank you so much about all of these details. You can check it here as well as install other frameworks. NET Framework versions per Configuration, this is not possible using the UI, but is perfectly valid for MSBUILD that at the end is who compiles the project. This allows me to use things on MSBUILD that are not exposed throught the VisualStudio UI. csproj manually except to add new files to the solution. In our case is just like this and don’t need to be modified when we introduce new Revit versions. The problem with that approach is that when you want to introduce REVIT_2021 you need to review all the source code looking for those places that you have conditinal compilation and adding || REVIT_2021. Do something specific for Revit 2018 or above here. mcneel/rhino.inside-revit/blob/3d3985681455b9d9e02f4e10d8a18b0ef752846a/src/RhinoInside.Revit/#元37Ĭonditional compilation symbols are defined in a way that we don’t need to do something like this to have some code that works from a certain version of Revit and above. mcneel/rhino.inside-revit/blob/3d3985681455b9d9e02f4e10d8a18b0ef752846a/src/RhinoInside.Revit/#L24Ībout the automatic copy of output files to APPDATA you are right it is only on the Debug configurations. I checked the project and if you pick any 2020 Configuration it should reference. Maybe as a suggestion, I think it’s better to integrate into the installer itself a function for checking about previously old version installed files, if they are existing into the old location, so then to uninstall them first, update the registry, and finally install the new version. I think The issue is from the conflict existing between %APPDATA% & %ProgramData% though logically, same files shouldn’t load twice following to the rules of loading priority in Revit.Īs the installing location of the Rhino-inside is moved to %ProgramData%. So the new installed DLLs came with the new Rhino-Inside version are without problems on my system. NET 4.7, I think with the hotfixes (2020.2.3) they upgrade it to 4.7.2Īnyway, I tried also to move the DLLs files came from the Rhino-inside installer at %ProgramData% to %APPDATA% and they worked properly. Also the source code came with a preconfigured solution using (.NET 4.6.1) but unfortunately it’s rising so many errors when compiling it. The source code from GitHub has no (Post events) so I moved manually the DLLs compiled file to %APPDATA%. Though I always try to uninstall first the Rhino-inside before installing the new version but maybe the uninstaller left over some residues into the registry and kept referring the %APPDATA% and made this conflict with the new location. Thanks again for the info, It seems you are right.Īfter compiling the source code using (.NET 4.7.2) I’ve put the DLLs into %APPDATA% and it worked.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |