Dear Support Team,
we've integrated the space navigator in our software and are running into issues with Windows 8/10. Here the installation of the dotnet framework version 3.5 often causes troubles. We can't expect our customers to accept this - although it seems to be a Microsoft problem:
https://support.microsoft.com/en-us/kb/2734782
1. What are your plans regarding the dotNet Installation problems? Do you plan to update to dotNet v4? What do you recommend your customers if the installation of the dotNet framework fails and they are not willing or able to perform the DISM workaround?
2. Is there a driver-only installation we can point our customers to. The default package contains a lot of extra weight which seems unnecessary for most of our customers. Furthermore, the driver seems not to need the dotNet v3.5, but the additional tools/helpers do. If there would be a driver-only setup point one would also be ok.
Windows8/10 issues (driver only + dotnet 3.5)
Moderator: Moderators
Re: Windows8/10 issues (driver only + dotnet 3.5)
Hello mliebig,
there are legacy reasons why we make use of version 3.5 of .NET.
You can unpack the installation file twice (with 7 zip for example) and then you will find the installer for the driver only in the subfolder “components64\3DxWinCore”. The name of the file is 3DxWinCore64.msi.
there are legacy reasons why we make use of version 3.5 of .NET.
You can unpack the installation file twice (with 7 zip for example) and then you will find the installer for the driver only in the subfolder “components64\3DxWinCore”. The name of the file is 3DxWinCore64.msi.
Uta
3Dconnexion
3Dconnexion