My colleague started on Telerik a few weeks ago. I am about to try and get up to speed. He gave me a project which I have set up with data on my workstation. We got Telerik, MM.NET and its Telerik subclasses installed, and figured out how to manually browse to the Telerik.Web.UI file i the Telerik install location.
However, I had downloaded a slightly later version of Telerik, Version=2010.2.929.35, from our shared account. The SP.NET app still had one reference error, and if we tried run it it would barf on the web.config file saying it could not find the Telerik.Web.UI.
My colleague showed me an email or exchange on forum from Telerik saying that for a the version in question, you could get the PublicKeyToken from the xml file.
We are using .NET 3.5 version, so in the \35 folder, I verified the version number in the properties of the Telerik.Web.UI.dll as 2010.2.929.35.
However, in the Telerik.Web.UI.XML, the only reference to a PublicKeyToken was in these two lines:
<example>
<code lang="CS" title="C#">
spell1.CustomDictionarySourceTypeName = "RadSpellExtensions.CustomDictionarySource, RadSpellExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b5e57ccb698eab8e";
</code>
<code lang="VB" title="VB">
spell1.CustomDictionarySourceTypeName = "RadSpellExtensions.CustomDictionarySource, RadSpellExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b5e57ccb698eab8e"
</code>
</example>
Naturally, the value there when placed in the web.config file did NOT solve the problem.
On another thread here
so for the heck of it, we tried it in the web.config, and the program fired up.
So the question is, where are we SUPPOSED to be able to get the correct PublicKeyToken for a version of the .dll??
It is clearly not in the xml file in the \35 folder with this version.
However, I had downloaded a slightly later version of Telerik, Version=2010.2.929.35, from our shared account. The SP.NET app still had one reference error, and if we tried run it it would barf on the web.config file saying it could not find the Telerik.Web.UI.
My colleague showed me an email or exchange on forum from Telerik saying that for a the version in question, you could get the PublicKeyToken from the xml file.
We are using .NET 3.5 version, so in the \35 folder, I verified the version number in the properties of the Telerik.Web.UI.dll as 2010.2.929.35.
However, in the Telerik.Web.UI.XML, the only reference to a PublicKeyToken was in these two lines:
<example>
<code lang="CS" title="C#">
spell1.CustomDictionarySourceTypeName = "RadSpellExtensions.CustomDictionarySource, RadSpellExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b5e57ccb698eab8e";
</code>
<code lang="VB" title="VB">
spell1.CustomDictionarySourceTypeName = "RadSpellExtensions.CustomDictionarySource, RadSpellExtensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b5e57ccb698eab8e"
</code>
</example>
Naturally, the value there when placed in the web.config file did NOT solve the problem.
On another thread here
we found a reference to the version number, and a PublicKeyToken:
add tagPrefix="telerik" namespace="Telerik.Web.UI" assembly="Telerik.Web.UI, Version=2010.2.929.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4"/>
so for the heck of it, we tried it in the web.config, and the program fired up.
So the question is, where are we SUPPOSED to be able to get the correct PublicKeyToken for a version of the .dll??
It is clearly not in the xml file in the \35 folder with this version.
6 Answers, 1 is accepted
0
Hi Ronald,
You can use .NET Reflector, to see the Public Key Token of the assemblies. Also you can use sn.exe as an extrenal tool in VisualStudio. Additionally, if the assembly is added to your GAC, you can see its Public Key Token there as well.
If you regularly exchange this project with your colleague and the differences of your Telerik.Web.UI assemblies is not crucial, you can use non fully qualified name when referencing the assemblies:
This way you will not have to fix the references every time he sends you the project.
Best wishes,
Vasil
the Telerik team
You can use .NET Reflector, to see the Public Key Token of the assemblies. Also you can use sn.exe as an extrenal tool in VisualStudio. Additionally, if the assembly is added to your GAC, you can see its Public Key Token there as well.
If you regularly exchange this project with your colleague and the differences of your Telerik.Web.UI assemblies is not crucial, you can use non fully qualified name when referencing the assemblies:
<add tagPrefix="telerik" namespace="Telerik.Web.UI" assembly="Telerik.Web.UI"/>Best wishes,
Vasil
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
0
Peter
Top achievements
Rank 1
Rank 1
answered on 29 Nov 2011, 10:30 PM
I do not understand why Telerik are not publishing the version number and the PublicKeyToken together with the download instructions for Q releases?
I am not a VS programmer. I am comfortable with editing master pages in SharePoint and web.config files but I need the information to be able to update it - why is this so difficult. I have already wasted 2 hours of my time on this.
I am not a VS programmer. I am comfortable with editing master pages in SharePoint and web.config files but I need the information to be able to update it - why is this so difficult. I have already wasted 2 hours of my time on this.
0
Hello Peter,
The PublicKeyToken the same for all versions "121fae78165ba3d4", and you could find it in several places in our help including the article about Deploying the controls in SharePoint.
All the best,
Vasil
the Telerik team
The PublicKeyToken the same for all versions "121fae78165ba3d4", and you could find it in several places in our help including the article about Deploying the controls in SharePoint.
All the best,
Vasil
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now
0
Peter
Top achievements
Rank 1
Rank 1
answered on 30 Nov 2011, 02:17 PM
Thanks - useful to know. What about the version number?
The reason I suggested this was in plain sight on the download instructions is because this would be easy to do and is the logical place for such information. I spent hours searching telerik site on things like publickeytoken and did not find the key information I needed.
The reason I suggested this was in plain sight on the download instructions is because this would be easy to do and is the logical place for such information. I spent hours searching telerik site on things like publickeytoken and did not find the key information I needed.
0
Hi Peter,
I forwarded your request to our managers for further discussions.
And if I could make an additional note here is that you could also use JustDecompile to see the information of the assembly.
All the best,
Vasil
the Telerik team
I forwarded your request to our managers for further discussions.
And if I could make an additional note here is that you could also use JustDecompile to see the information of the assembly.
All the best,
Vasil
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now
0
Peter
Top achievements
Rank 1
Rank 1
answered on 01 Dec 2011, 03:26 PM
Thanks for the input.
I have found that the easiest way to find the publickeytoken and version information is to look in the c:\windows\assembly which clearly shows all this information.
I also think that the Q release downloads should be accompanied by a what to do guide particularly if you are using Telerik with SharePoint. SharePoint people are not necessarily VB or coding experts and a lot of the guides seem structured for the development community. I do find telerik to be a critically important resource and your support and knowledge bases are great - keep it up!
I have found that the easiest way to find the publickeytoken and version information is to look in the c:\windows\assembly which clearly shows all this information.
I also think that the Q release downloads should be accompanied by a what to do guide particularly if you are using Telerik with SharePoint. SharePoint people are not necessarily VB or coding experts and a lot of the guides seem structured for the development community. I do find telerik to be a critically important resource and your support and knowledge bases are great - keep it up!