Last post Aug 01, 2007 05:10 PM by axxon
Oct 21, 2006 11:32 AM|conquer0|LINK
I have just installed ajax beta 1 & ctp.
All works fine BUT I have no IntelliSense inside of masterpages (inside of asp:Content blocks)
And I have syntax errors on ajax controls and all default asp controls. But only if these are after a ajax control.
I tried this with a new "AJAX-Enabled Web Site" & "AJAX CTP-Enabled Web Site", same problem!!
There are no problems inside of a 'standard' aspx page!
I have no atlas dlls inside of my projects or somewhere else.
can somebody help me please?
Oct 21, 2006 04:24 PM|conquer0|LINK
strange! I get no syntax error if I open the Masterpage and let it open!
maybe a bug?
Oct 21, 2006 05:27 PM|albertpascual|LINK
Oct 21, 2006 06:14 PM|conquer0|LINK
I do this steps:
Title="Untitled Page" %>
and now, I have the following 2 errors and no intellisense
Error 1 Element 'UpdatePanel' is not a known element. This can occur if there is a compilation error in the Web site. E:\Workspace\Test\AJAXBeta1\Default2.aspx 3 6 E:\...\AJAXBeta1\
Error 2 Validation (XHTML 1.0 Transitional): Element 'contenttemplate' is not supported. E:\Workspace\Test\AJAXBeta1\Default2.aspx 4 6 E:\...\AJAXBeta1\
If I open the masterpage now and go back to my default2.aspx site I have the intellisense back and no errors :)
Oct 21, 2006 10:44 PM|chadly|LINK
I am having the same problem. Very aggrevating... No intellisense on any of the AJAX controls (UpdatePanel, Timer, etc...) or any of the AjaxControlToolkit controls. All of the ajax controls generate a "not a known element" parsing error when looking
at a page in source view. Anything within the AJAX controls (inside of an update panel, etc.) also display the "not a known element" error.
It happens on content pages when using a master page.
Oct 22, 2006 12:47 AM|aschreiber2|LINK
Whew! I thought I was the only one having these problems. Everything worked fine when I used Atlas. Then I installed Beta1 and the CTP and it all went down the tubes. I followed all of the instructions and modified my Web.Config accordingly. In fact, just
to be on the safe side I started a whole new project using the new web project templates that are now available and even those don't compile!
What's even stranger is that even regular ASP.NET controls now are being flagged as errors. In my code below, the UpdatePanel and DetailsView controls all have squiggly red lines beneath their respective tags. Nothing will compile
SelectedValue='<%# Bind("TitleID") %>'>
Checked='<%# Bind("isPrimaryTitle") %>'
ToolTip="Set this title as the contact's primary title?"
Text='<%# Bind("TitleID") %>'></asp:TextBox>
Text='<%# Eval("TitleName") %>'></asp:Label>
SelectedValue='<%# Bind("OrganizationID") %>'>
Text='<%# Bind("OrganizationID") %>'></asp:TextBox>
Text='<%# Eval("OrganizationName") %>'></asp:Label>
SelectedValue='<%# Bind("StateID") %>'>
Text='<%# Eval("StateName") %>'></asp:Label>
SelectedValue='<%# Bind("CountryID") %>'>
Text='<%# Bind("CountryID") %>'></asp:TextBox>
Text='<%# Bind("CountryID") %>'></asp:Label>
Oct 22, 2006 01:01 AM|aschreiber2|LINK
When I start a new project using the Ajax ASP.NET template my site DOES compile -BUT I still get the squiggly lines and no IntelliSense.
Oct 22, 2006 04:36 AM|Jason Hill|LINK
It looks like a few people are having this problem (including me!) and I posted to this thread earlier today:
The problem only seems to occur for me when using a Master Page...is that the same for you? I also tried creating a fresh project using the installed VS template but the problem is the same. Seems like it could be a problem with the beta release.
I hope this gets fixed soon because I have migrated a site from Atlas to beta 1 and I don't fancy undoing/redoing all of that!
Oct 22, 2006 10:22 AM|conquer0|LINK
Just open your masterpage after opening your aspx page and you can debug! I know it's not a nice solution.. but it is a solution.
Or you can close all files first and then debug.
Oct 22, 2006 11:38 AM|Jason Hill|LINK
Oct 22, 2006 04:28 PM|ericpopivker|LINK
A temporary fix (till MS fixes it) is to change the 'asp' prefix in web.config file back to 'atlas' (actually anything other 'asp' would work) and then change prefix to 'atlas' on UpdatePanel and ScriptManager controls. Then intellisense works again.
Oct 22, 2006 11:05 PM|pedro.machado|LINK
good tip Eric. Yesterday I was testing the beta 1 of ajax and had that problem. Your tip helped me,
Oct 22, 2006 11:29 PM|weerasin|LINK
I had the same error. I opened my site master page and left it open in VS2005 and then opened my page with ScriptManger and UpdatePanel. The squigllies are gone and not I am getting Intellisense again.
I looks like it a bug related to master pages. Please confirm if this works for other people with the same problem.
Oct 22, 2006 11:31 PM|weerasin|LINK
Oct 22, 2006 11:50 PM|aschreiber2|LINK
Just to update my posting again, yes I am also using Master Pages. I think that pretty much everyone is here. I with we could make an amendment to the thread title to include "... while using master pages".
I am also confirming that when I open up the master page in the IDE and switch back to my content pages, the squiggly lines disappear and IntelliSense is now working.
On a separate note, does anyone here know how to remove all references to a project/website so it never appears in Visual Sudio again?
Here is what I have done so far to date.
For websites running on local IIS, I delete the site from IIS and the root folder and all of it's subfolders and files get deleted with it. I also make sure to delete the project folder containing the solution files from the
C:\My Documents\Visual Studio 2005\Projects folder AND I also deleted the entries to the projects from the
C:\Documents and Settings\Username\Local Settings\Application Data\Microsoft\WebsiteCache folder and removed the site entry from the Websites.xml file located in the WebsiteCache folder.
The problem I am running into, is that each time I do that and try and create a new project with the same name as the one I thought I just deleted it uses the format NewProjectName(1). Which can only mean that somewhere else on my computer there must still
be a reference to the old project name that I have not removed and as a result Visual Studio cannot give it the same name as the the other project so it appends the (1) to the name (which I don't want).
Any tips would be appreciated.
Oct 23, 2006 12:20 AM|Jason Hill|LINK
Nice one Eric...changing the tag prefix to atlas worked like a charm.
Oct 23, 2006 02:30 AM|weerasin|LINK
I am not 100% sure but I think you have to also delete the dynamically compliled assemblies under "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\" folder. ASP.NET 2.0 compiles the website in real time and places the content in a
supfolder under the above folder. I am not exactly sure of the relationship between VS Projects folder and content in the folder. VS 2005 locks this folder when the project is open. You web references are also in here.
Close VS2005 and then delete the SUBFOLDER for your project.
Oct 23, 2006 03:28 AM|aschreiber2|LINK
Thanks for your response Mike. I already tried that with no luck. Anyhow, I don't want to take this thread off topic so I'll just end my post here and open up a new thread under the regular ASP.net message board as opposed to the Ajax one.
Oct 25, 2006 04:38 AM|AlanGrant|LINK
Had the same problem and this worked for me (opening the master page in the ide)
Oct 26, 2006 12:17 AM|chadly|LINK
I don't know if all of you are ALSO using the Beta of VS 2005 SP1? I am and it
might be a problem with the VS SP1 Beta. See here:
Nov 08, 2006 06:00 AM|asifcs|LINK
I am also working on VS2005 SP1 Beta1. And I am not getting Itellisence support on markup pages! Should I try uninstalling SP1 beta??? May be I will.
Nov 08, 2006 06:11 PM|aschreiber2|LINK
Nov 09, 2006 08:16 PM|Jason Hill|LINK
Nov 10, 2006 12:01 AM|conquer0|LINK
I think this a Visual Studio Bug.
I am using Ajax Beta2 and Visual Studio without SP1 Beta1, but I think SP1 Beta1 has the same Problem!
Jan 15, 2007 08:14 PM|baileyrt|LINK
Kudos to you, Eric.
No combination of master page and default.aspx page (open, closed, position on the tab bar, etc) would get rid of the horrid squigglies and the lack of intellisense. But changing the tagprefix to "ajax" worked like a charm.
ajax update panel
AJAX .NET RC1
Jan 16, 2007 06:01 AM|asifcs|LINK
This is a problem of VS2005. They say it is fixed in VS2005 SP1. And Yes it is fixed in VS2005 SP1. Did you install the service pack yet? If no Scott Gu of ASP.NET team has provided another temp solution. you may try it. its entry is called Lost HTML Intellisense
within ASP.NET AJAX Controls
--- If This post answers your Question/problem then mark it as answer!
Jan 16, 2007 12:06 PM|Balzak|LINK
i have the same problem and im not using the sp1 of vs2005 but when we remove the updatepanel all intelissense and bug erros just disapears
this errors are just bugs they dont make ur aplication to stop work they just confuse u when something else isnt working u just need to find what isnt working and fix it then ur aplication will build and will run just fine and for me if u delete the updatepanel
everything just go back to normal and when u finish the page u just need to add the updatepanel again
Feb 08, 2007 02:51 PM|ashen419|LINK
Jun 18, 2007 09:41 PM|CiscoCylk|LINK
I am getting these same errors plus the compiler is coughing up on this line from my web.config. (I too am using Master Pages, but none of the solutions about opening up pages in a certain order and refrreeshing them work for me....and I cannot run at all,
I am stuck!)
Error 1 Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. \\ecad-cs1\Subscriber_Security\WebSites\MasterECADDSS\pgDesignRequest.aspx 344
Also when I added the Ajax controls to the IDE I must have done something different (I don't think its wrong) because in the source code the prefix is CC1 not ajaxToolkit, and I know it works because if I open a totally new website project and create Ajax
application it works fine, but it will not work on this exisiting website that I am trying to retro fit to be Ajax enabled.
I also do not understand where in the web.config that I am supposed to change a prefix from ASP to AJAX...do you mean here?
Notice how this is the line that the compiler is failing on as well.
Jun 28, 2007 10:28 PM|m_karbala|LINK
Jun 28, 2007 10:30 PM|m_karbala|LINK
it worked for me
Jun 29, 2007 09:19 PM|CiscoCylk|LINK
OK this other thread is a better explanation of what my problem was and how I fixed it.
Aug 01, 2007 05:10 PM|axxon|LINK