For some reason, Intellisense does not work when using Visual Studio 2008. I've been using your controls for some time now and I'm not doing anything different causing Intellisense not to work. It's been tested on different PC's with Visual Studio 2008 installed and none of them work.
It doesn't matter which way I register the Telerik DLL, Intellisense doesn't show up. For example:
<%
@ Register TagPrefix="telerik" Namespace="Telerik.Web.UI" Assembly="Telerik.Web.UI" %>
or
<
add tagPrefix="telerik" namespace="Telerik.Web.UI" assembly="Telerik.Web.UI"></add>
Please advise! This is a huge roadblock for me. Thank you in advance.
19 Answers, 1 is accepted
Please try the latest build. We removed Telerik.Web.Desing.dll (now both libraries are merged).
Kind regards,
Vlad
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center

can anyone from the telerik team add to this an explain why these files enabled intellisense?
Indeed there was a similar intellisense problem with previous versions of the Prometheus suite in VS2008 -- could you confirm you are using the latest release (2007.3.1425) and you are still experiencing the undesired behavior?
Best wishes,
Manuel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center

Yes I am using the latest build - 1425. The only way I was able to get intellisense to work properly was by including the charting dll and xml files in my bin folder. Not sure if it makes a difference to this issue but I'm doing my development in DotNetNuke.
- Vinny
This is odd -- we are still unable to reproduce the problem with the latest version of the controls neither with a default installation (that puts the Telerik.Charting.dll in the GAC), nor with a clean machine that does not have the Prometheus controls installed (no Telerik.Charting.dll in the GAC). We will continue our research on this one -- hopefully it is not a major inconvenience for you to include the charting in your /bin folder (you can try install it in the GAC if you have not done so so far to see whether there is any difference).
All the best,
Manuel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center


I've tried registering the tag prefix at the top of the page and in the web.config (where, for my project, I'd prefer to have it) but neither works.
I've tried it on three Vista PCs to no avail. I'm wondering if it has something to do with the application and its files being stored on a server (which we open in VS2008 using a mapped network drive, not a local drive). I tried running the EXE installation on the server as well just in case, but it didn't help.
I remember a similar problem with ASP.NET "Atlas" before they released it as ASP.NET AJAX (back when we used VS2005), but I don't know what the ASP.NET team did to fix the problem... (for my part, I just waited for the updated dll!)
Any ideas? I'd love to get started with the controls but really need them to be properly recognized in VS. (They work fine at runtime btw, and render in my browser perfectly. They also work fine in the design view of VS).
Thanks! Jake.

Other than that I have no idea, but if it's any consolation I was dealing with the same problem for weeks before I stumbled upon the fix on my machine. Sorry I can't be of more help.

You can try the suggestions in this forum:
http://forums.asp.net/thread/1350141.aspx
Basically, the easiest solution should be to open the site with UNC, for example:
\\server\path
If this is not applicable, the process is a bit more complicated:
1/
You must be using Front Page Server Extensions 2002. Once you have this configured, and you can connect to your site on your local server - you Intellisense should start working.
2/
If your server is configured similar to mine
as above, you'll find that debugging breaks. This is due to a problem
with CNAMES / Alias's - and is easily resolved by making a minor
registry change on your development server as in this post: http://forums.asp.net/thread/942444.aspx
Hope this helps you to resolve this problem.
Greetings,Bart.

Thanks so much for your replies.
Bart - Great suggestion... I gave the first idea a go (using unc path) and had no luck :( VS still doesn't recognize the telerik tags. Unfortunately I can't try the second idea, because we're not allowed to install FrontPage extensions on our server ("because they're discontinued")...
Vinny - did you just add the Charting dll and xml files to your Bin folder, or did you also add a reference to charting in your web.config. I'm not really sure how different DNN development is from a regular asp.net web app... but did you also do anything with the GAC? I notice that Charting is already in my GAC...
Thanks again,
Jake.

Server Error in '/RadControls_Prometheus' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

All I did was add the charting files into the bin folder. I was looking at all the components in the .NET 3.5 bin folder of the examples project and added all the telerik dll's and xml files into my bin folder that weren't there. Since intellisense worked in the sample project I figured there has to be something in the configuration that was causing intellisense to work in one and not the other. I eventually narrowed it down to the charting files.
The .NET 3.5 version of System.Web.Extensions is below. This is usually upgraded when you first open a 2.0 project in VS 2008 and accept the upgrade to 3.5.
"System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"

So - to Telerik - is this something that can be fixed for those of us who want our websites stored on network shares instead of our local hard drives? I'm hesitant to buy this unless this feature can be supported.
Thanks! Jake.
The IntelliSense problem should be resolved after you add the Telerik.Web.UI.dll file in the GAC of your local machine.
As for the error received when trying to run our examples, can you replace the web.config file located in your Live Demos directory (e.g. C:\ProgramFiles\Telerik\RadControls 'Prometheus' for ASPNET Q3 2007\Live Demos) with the one named Web.config.Net35 located in the same directory?
I hope these tips help.
Greetings,
Pavel
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center

Thanks Pavel,
I can confirm that adding the Telerik.Web.UI.dll file to the GAC of my local machine and my web server worked (not sure if adding it to the GAC on the web server was necessary, but did it anyway just in case!)... I now have full IntelliSense.
Jake.
(P.S. In case it's relevant, I did this with the new Q1 2008 release.)


I also experience problems with IntelliSense and this was just appearing from nowhere ( I thought ), actually I think I can recall when it appeared since I have found how to get the IntelliSense back, but I dont like the workaround I had to do.
It most likely started when I changed my web.config file to use <trust level="Medium" />, when trust is set to Medium I do not have IntelliSense in any aspx file, but in the code-behind it works fine and I do not get any errors when running the application. If I remove <trust level="Medium" /> from the web.config I get IntelliSense back. This is though not a solution for me since my ISP is only supporting Medium trust and I want to develop under medium trust to not get any big suprises when deploying into production.
I have sent a support ticket to Telerik today and waiting for answer from them.
/ Mikael
We will review the information in your support ticket and will get back to you with more info on the subject.
Best regards,
Sebastian
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
