Note: We have fixed this issue in our upcoming volume release (2015 volume 1).
Please let us know if you need any further assistance on this.
Regards, Kathiresan S.
FEFenebergApril 2, 2015 07:13 PM UTC
I try the solution.
But on the Windows 10 Preview Build 10049 it not work.
I try the commandline function, but no reaction - no error.
I reinstall the Essential Studio and tried it again. Commandline with administartor privilegs. But it did´t work.
Can you say the release date of 2015 Volume 1? I can test it.
It would be nice if it works. It is my Visual Studio 2015 Test Machine and it is not so important if it does not work.
Thanks for the feedback.
KSKathiresan Subramaniam Syncfusion Team April 3, 2015 11:00 AM UTC
Thanks for your response and we regret for the inconvenience caused.
We would like to inform that our 2015 Volume 1 going to be released in the April 4th , 2015.
The reported Assembly Manager issue has fixed in this release. So, you can able to configure all the 4.5,4.5.1 Syncfusion assemblies in your machine without any issues.
Please let us know if you have any queries.
Regards, Kathiresan S.
RWRenwick WrightOctober 4, 2018 09:50 PM UTC
I am also having the same problem, only with SyncFusion 18.104.22.168 on Windows Server 2016 Standard. Upgrading SyncFusion even to a minor version is not an option.
Currently my development environment is based on Windows Server 2012 R2. The main application I support has been migrated to .Net 4.6.1 and at the same time was migrated to SyncFusion 22.214.171.124. The libraries for .Net 4.6 installed fine at the time (18 months ago). SyncFusion Essential Studio Assembly Manager was showing all the .Net versions with none of them being grayed out.
I now have to migrated to a new development environment based on Winodws Server 2016 Standard with all version of .Net installed (3.5 - 4.7.2) . When I tried installing SyncFusion 126.96.36.199, I was surprised to see Assembly Manager has the .Net versions beyond .Net 4.0 grayed out.
I have tried the above approach of running the following command line:
However, I checked on my Windows Server 2012 R2 environment, and those lines are present in the log file as well. So I don't think this is a very useful source of information.
Finally, I know that this has been fixed in later versions of SyncFusion, even service packs. However, it is not an option to upgrade my large application to use another version of SyncFusion so I need to make this particular version work.