On that (virtual) machine, ArcGIS Runtime .NET 100.0 doesn't work at all (Call to constructor of MapView crashes). I need to find a way to argue to the system administrator why this machine doesn't meet the system requirements.
Note: We've found Windows 8+ on VMs works a lot better than Windows 7, due to its better GPU hardware emulation. We're currently looking into adding some software fallback for Win7 for a future update.
Btw which crash are you getting? And do you have a call stack from the crash? (preferably enable "native debugging" in the debug settings of the app to get a better callstack that covers both managed and native code)
_message=Zeilennummer "14" und Zeilenposition "10" von "Durch den Aufruf des Konstruktors fr Typ "Esri.ArcGISRuntime.UI.Controls.MapView", der den angegebenen Bindungseinschrnkungen entspricht, wurde eine Ausnahme ausgelst.".
Message=Zeilennummer "14" und Zeilenposition "10" von "Durch den Aufruf des Konstruktors fr Typ "Esri.ArcGISRuntime.UI.Controls.MapView", der den angegebenen Bindungseinschrnkungen entspricht, wurde eine Ausnahme ausgelst.".
bei System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
_message=Invalid ArcGISRuntime deployment, unable to load native dll. Maybe a missing native dependency, checking with dependency walker may help resolve this issue. C:\src\ArcGISApp1\bin\Debug\arcgisruntime100.0\client32\RuntimeCoreNet.dll
Message=Invalid ArcGISRuntime deployment, unable to load native dll. Maybe a missing native dependency, checking with dependency walker may help resolve this issue. C:\src\ArcGISApp1\bin\Debug\arcgisruntime100.0\client32\RuntimeCoreNet.dll
Please note, that the most inner Exception Message "Das angegebene Modul wurde nicht gefunden -> The module has not been found" is wrong. The RuntimeCoreNet.dll exists in the path, even more, it is loaded into the process at the time, the exception is thrown.
I haven't gotten a more detailed StackTrace by enabling "Native Code Debugging". But I think I should have gotten at least some obscure Dissamblies (no .pdb available..). I will try bit more to get a real native StackTrace..
After double checking the system requirements page, I saw "Windows 10 Universal C Runtime" and "Microsoft Visual C++ 2015 Redistributable Update 3" under the deployment targets chapter. Installed both in the development VM and now, the application starts, displays a white are with "Powered by Esri" and... crashes
To check your feature level, run "DXDIAG" to open the DirectX Diagnostics. Go to the display tab and look at "Feature levels" in the Drivers section. You should see at least 9_3, preferably higher. 2D will for the most part work in 9_1, but you can easily hit certain layers that would require a higher level (and there's no guarantee this will continue to be the case).
Generally if the DirectX Device can't be created, you should see an error message over the mapview with the specific DirectX Error (this is usually just an error code, but if you google it, you should find the description of the directx error)
a) the versions supported on a given OS
b) The graphics card and drivers you are using and their dependency (or lack thereof) of a minimum DirectX version
c) Most importantly, the requirements of the games/applications you want to run . I.E. If the game you want to run requires a specific DirectX version as a minimum, it won't work with an earlier version
d) Potentially backward compatibility issues that a given games/applications may have with too new a DirectX version. Though issues are more likely to stem from too new a graphics card and/or driver version than the DirectX version installed as DirectX is generally pretty good with backward compatibility
However, if using a single machine for Windows 9x/ME compatible stuff, my experience/preference so far is that practically anything needing up to DirectX 9 or earlier (and not requiring Windows XP) can usually be handled by using a single machine running Windows 98SE with DirectX 9 and 2 graphics cards :
I am not sure what I am trying to accomplish, I have a radeon 9600 pro for winME, I also have 2 much stronger machines that dual boot windows XP.
So maybe, at what dx level of games does the radeno 9600 pro become weak?
I agree. My artificial limit means absolutely no DirectX9 on Windows 9X. A Ti4200 (or when I used to own a 4600) is as fast as I will take Windows ME. Windows 98SE gets all Voodoo2 and later 3dfx. Windows 95 gets PowerVR and Voodoo1/Rush.
Correct, you cannot rollback DirectX without a reinstall; except possibly in the case of Windows XP and rollback of Service Pack 2 or 3 to Service Pack 1. (Though I have never tested this to confirm).
I hope it turns out OK. This is the gamble I have tired of taking with Windows 9X for many years now. There was fun in trying to get things working without starting from scratch, but life is too short.
d3342ee215