We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on : November 16, 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Versioning Difficulties

Thread ID:

Created:

Updated:

Platform:

Replies:

38477 Dec 13,2005 10:19 PM UTC Dec 14,2005 08:34 PM UTC General Discussion 2
loading
Tags: General Discussion
Plioi
Asked On December 13, 2005 10:19 PM UTC

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?

Administrator [Syncfusion]
Replied On 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.

Administrator [Syncfusion]
Replied On 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.

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

;