The Syncfusion native Blazor components library offers 70+ UI and Data Viz web controls that are responsive and lightweight for building modern web apps.
.NET PDF framework is a high-performance and comprehensive library used to create, read, merge, split, secure, edit, view, and review PDF files in C#/VB.NET.
We''ve used older version of Essential Suite and tried installing the latest beta.
One developer installed the new version, and began using it in a project. He added references to the assemblies as you would expect. It was able to build for him.
After doing a get-latest from source control, which included the new references, I right-click on the reference and go to properties. For the first developer, this gives a 4.x version number. For me, it gives a 3.x version number.
So, we tried uninstalling everything again to start from scratch. Then we noticed that there were several versions'' worth of assemblies in the GAC, despite the fact that we uninstalled.
We uninstalled those from the GAC and saw the same issue after installing 4.x again.
If we right-click on the reference in Solution Explorer, and go to properties, in addition to the "Version" being different, there is a "Path" property. When we go to that folder in windows explorer, we see several DLLs from 9/1/2005 as well as some from this December release.
Any ideas what is going on? How can one user set up a reference in a project, put that in source control, and then have those references pointing at the wrong version when someone else gets the latest from source control? Is it surprising that uninstalling doesn''t remove from the GAC or the Path indicated in Solution Explorer references list?
ADAdministrator Syncfusion Team December 14, 2005 06:16 PM UTC
Hi Plioi,
Is this folder with all the Assemblies the PublicAssemblies folder under your Visual Studio install? If so, deleting all of the Syncfusion assemblies from that folder should correct the problem.
Alternatively, you could change the hint path for your references to point to a different directory.
Regards,
Gregory Austin
Syncfusion Inc.
ADAdministrator Syncfusion Team December 14, 2005 08:34 PM UTC
Thanks. Wiping out those assemblies worked.
>Hi Plioi,
>
> Is this folder with all the Assemblies the PublicAssemblies folder under your Visual Studio install? If so, deleting all of the Syncfusion assemblies from that folder should correct the problem.
>
> Alternatively, you could change the hint path for your references to point to a different directory.
>
>Regards,
>Gregory Austin
>Syncfusion Inc.
