[Solved] Licensing Issue

[Tom]

I am collaborating on a project with another department, which purchased their Telerik controls separate from my department. We keep on losing the reference to the telerik controls as we open the project from Source Safe, updating our local project in the process. Is this due to the different licenses? This is not a major problem, just a minor inconvenience - we have to delete the reference, then add it back.  Is there a way to avoid  this? 

Thanks

Tom W.

[Fiko]

Hi Tom,

I am not quite sure what exactly is causing the described inconvenience in your case, but I suppose that the two departments reference two different version of a Telerik.Web.UI assembly. All references related to a project are stored inside the Visual Studio's project file. In this case when you add a reference to your assembly (for example version A), then your colleagues from other department will get an error which says that the assembly does not exist (and vice-versa), because they use different version (for example B) of the assembly. Could you please check this on your side?

I hope this helps.

Regards,
Fiko
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Tom]

Fiko,

That is exactly the problem - my assembly version, installed as soon as it was released is 2009.3.1208.35.  Their version, which they just purchased recently, is 2009.3.1314.35.

Why are there 2 different assemblies for 2009 Q3? (So I can figure out how to stay in synch in the future).

Thanks

Tom W.

[Fiko]

Hi Tom,

We provide two versions of the same assembly - one for .NET2.0 and another for .NET3.5. For example
the version 2009.3.1314.35 is built for .NET35 and the 2009.3.1314.20 is built for .NET20. In the upcoming release (a  beta version is available here) we will provide an assembly for .NET40 as well.

I hope this helps.

Best wishes,
Fiko
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Tom]

I was referring more to 2009.3.1208.35 vs. 2009.3.1314.35.  Both of our departments purchased the controls at different times, and when we installed 2009 Q3 ( at different times), we got 2 different assemblies for 3.5

Is 2009.3.1314.35 a minor version release?

It's starting to get a little tricky keeping track of different projects, different frameworks, and now different versions of the same releases - different builds.  :)

Thanks

[Fiko]

Hi Tom,

These two assemblies are two different versions. The first one (2009.3.1208.35) is SP1 for the Q3 2009 release of the controls and second one (2009.3.1314.35) is SP2 for the Q3 2009 release. Our policy is to release SP release(s) after a major release in order to be up to date with all

The information for all releases can be found on this page.

I hope this helps.

Sincerely yours,
Fiko
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.