Hi Marsel, thank you for providing the new version of Max.Net. Unfortunately, we have troubles installing the new version. Using the offline installer we receive an installation error dialog as shown in the picture attached to this thread. When using the online installer the installation is finished successfully, but when starting 3ds Max I get the following error: System.IO.FileLoadException: Die Datei oder Assembly "Autodesk.Max, Version=1.1.9.0, Culture=neutral, PublicKeyToken=16334a31b11f406c" oder eine Abhängigkeit davon wurde nicht gefunden. Die gefundene Manifestdefinition der Assembly stimmt nicht mit dem Assemblyverweis Überein. (Ausnahme von HRESULT: 0x80131040)
Dateiname: "Autodesk.Max, Version=1.1.9.0, Culture=neutral, PublicKeyToken=16334a31b11f406c"
(Sorry, it's in German, but it says that the assembly "Autodesk.Max" is not found, probably because the filename lacks the DLL-extension). The uninstaller doesn't work as well, so we can't use Max.Net anymore :( Anything we can do? Christian
Attached Files: |
| Hi Christian, Unfortunately, we have troubles installing the new version. Using the offline installer we receive an installation error dialog as shown in the picture attached to this thread. Did you by any chance rename the installer? Install session is part of the installer name so if you rename it, it will no longer work properly. When using the online installer the installation is finished successfully, but when starting 3ds Max I get the following error: I don't think its the extension per se. Please make sure you delete all older Max.NET assemblies from 3dsmax plugins, recompile with the newer version of Autodesk.Max.dll and let me know if the error is still there. Marsel Khadiyev (Software Developer, EPHERE Inc.) |
| I didn't changed the name of the offline-installer, I tried it one more time, and the error message showed up again. The online-installer worked. The error when opening 3ds Max was caused by my old Max.Net-based plugins, so I had to remove them and everything works fine! But that raises another question when distributing those plugins. How can I assure that the right version of Max.Net is available for my plugins, especially when there's already a Max.Net-plugin from another company installed (like Zookeeper)? The user is not able to compile those plugins for the updated version, so there have to be multiple Max.Net instances in order to work for both plugins. Christian |
| Right, I can see this as an issue. It shouldn't work like that by spec. and I think the version-binding is caused by the assembly signing used for Autodesk.Max.dll. I will definitely try to resolve this to ensure backward compatibility of Autodesk.Max.dll. I will also check the offline installer, something must have broken down. Marsel Khadiyev (Software Developer, EPHERE Inc.) |
| The offline installer should be behaving much nicer now. Also uninstalling should work properly. Marsel Khadiyev (Software Developer, EPHERE Inc.) |
| Hey Marsel, I had the problem that I could not use the uninstaller, because it requires admin-modus. I always work on an Admin-account but in Win7 you have to start programs explicitely by "Running as Administrator" from the right-mouse-click-context-menu. This is not possible within the Windows Control Panel, as you can only click the button for deinstalling what automatically calls the uninstaller. Is this problem already fixed or do you have an idea how I can nevertheless use the uninstaller? Thx in advance
Michbeck |
| Right, the installer/uninstaller currently needs admin rights (because it can potentially alter the registry and/or write to folders). I can see how this is a problem and I'll try to find a better way to handle it. I have been planning to revisit the (un)installer for some time now so its high on the TODO list. I'll let you know about any progress. Marsel Khadiyev (Software Developer, EPHERE Inc.) |
