Visual Studio doesnt recognize(see) ATLAS from LAN!

When I try to open a website from server(LAN) I get following error within VS 2005:

Error 1 Element 'ScriptManager' is not a known element. This can occur if there is a compilation error in the Web site. ...

but the site works properly anyway... This error just annoys me, I can't see any Intellisence code for atlas components...

I have installed VS on server and installed Atlas components there too. VS shows Atlas tags properly when I launch VS from server, but doesn't do that when I try to open the same project from another computer.

The other computer has installed VS 2005 too...

Can anyone answer how to solve this?

hello.

i think this has been reported here...if i'm not mistaken, it only works without any problems when you open a local project.

Visual Studio wont recognize some AJAX components when there is a master page

This is a really weird thing. I have installed AJAX and the toolkits and the validators, and everything was working fine. Then, suddenly, Visual Studio won't let me switch to design view b/c the script Manager and the update panels are now "not known elements," and so are all the labels, panels, dropdownlists, etc inside the update panels. Oddly enough, the components in the AJAX toolkit are still recognized just fine. when this problem first started happening, i would click over to the master page and click back to the aspx page and everything was fine. Now that doesn't even work. And the craziest part is that the web site runs just fine when I debug it, AJAX functionality and all!

I would have blamed this on the way I installed the AJAX framework, but this only happens on pages with master pages.

Does anyone have any experience with this? Or is it just my machine? No one else here at work is having this problem, but I am the only one who is really using AJAX.

Any ideas would be welcome. Thanks in advance

Hi,

As far as I know, the error message indicates the issue is related to permission. It seems your ASP.NET applications run in partial trust. This is configured through the <trust level="xxx" /> setting in web.config or machine.config. Please change the "xxx" to medium and try again to figure out whether the problem still occurs.

Best Regards

Thanks for your suggestion. I don't even have any trust level permissions in my web.config files, so I am assuming that the problem is in my machine.config file. But before I go messing around in there, I would like to try to override it in the web.config. This is what I have in my web.config. But the error I am getting on the page declaration of the default.aspx page is "Unable to read the security policy file for trust level 'medium'." Where are the policy files located?

<location allowOverride="false">
<system.web>
<securityPolicy>
<trustLevel name="Full" policyFile="internal"/>
<trustLevel name="High" policyFile="web_hightrust.config"/>
<trustLevel name="Medium" policyFile="web_mediumtrust.config"/>
<trustLevel name="Low" policyFile="web_lowtrust.config"/>
<trustLevel name="Minimal" policyFile="web_minimaltrust.config"/>
</securityPolicy>
<trust level="medium" originUrl=""/>
</system.web>
</location>

VS cant recognize all tags from AJAX framework.

For some reason starting from Beta VS marks all tags that represent AJAX makeup as invalid even though page compiles and runs OK.

Did anybody see this?
Thanks

there's already 4 or 5 topics on this... here's one of them (http://forums.asp.net/thread/1435993.aspx)

VS doesnt recognize tags asp

Hei,

I'm getting started with ajax, i do a lot of things with the ajaxToolkit but i still have a problem,

When i put an update panel on a page, visual studio can't recognize all the asp tag, and my code loose its formating and i can't use completion (ctrl+space) anymore.

Is it a problem of web.config?

Thanks to help me.

ps: Sorry for my english ...

This is my web config

<?

xmlversion="1.0"?>

<

configuration>

<

configSections>

<

sectionGroupname="system.web.extensions"type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

<

sectionGroupname="scripting"type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

<

sectionname="scriptResourceHandler"type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"/>

<

sectionGroupname="webServices"type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

<

sectionname="jsonSerialization"type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"/>

<

sectionname="profileService"type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"/>

<

sectionname="authenticationService"type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"requirePermission="false"/>

</

sectionGroup>

</

sectionGroup>

</

sectionGroup>

</

configSections>

<

connectionStrings>

<

addname="DBConnectStr"...."/>

</

connectionStrings>

<

system.web>

<!--

Recupere la langue du browser-->

<

globalizationuiCulture="auto"culture="auto" />

<

trustlevel="Medium"/>

<

pagesstyleSheetTheme="Default">

<

controls>

<

addtagPrefix="asp"namespace="System.Web.UI"assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

controls>

</

pages>

<compilationdebug="true">

<

assemblies>

<

addassembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addassembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>

</

compilation>

<

httpHandlers>

<

removeverb="*"path="*.asmx"/>

<

addverb="*"path="*.asmx"validate="false"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addverb="*"path="*_AppService.axd"validate="false"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addverb="GET,HEAD"path="ScriptResource.axd"type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"validate="false"/>

</

httpHandlers>

<

httpModules>

<

addname="ScriptModule"type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

httpModules>

</

system.web>

<

system.web.extensions>

<

scripting>

<

webServices>

</webServices>

</scripting>

</

system.web.extensions>

<

system.webServer>

<

validationvalidateIntegratedModeConfiguration="false"/>

<

modules>

<

addname="ScriptModule"preCondition="integratedMode"type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

modules>

<

handlers>

<

removename="WebServiceHandlerFactory-Integrated"/>

<

addname="ScriptHandlerFactory"verb="*"path="*.asmx"preCondition="integratedMode"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addname="ScriptHandlerFactoryAppServices"verb="*"path="*_AppService.axd"preCondition="integratedMode"type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<

addname="ScriptResource"preCondition="integratedMode"verb="GET,HEAD"path="ScriptResource.axd"type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</

handlers>

</

system.webServer>

</

configuration>noone for me?

VS Editor does not recognize Atlas tags

This is what I have in web.config:

<controls>

<addtagPrefix="asp"namespace="Microsoft.Web.UI"assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<addtagPrefix="asp"namespace="Microsoft.Web.UI.Controls"assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<addtagPrefix="asp"namespace="Microsoft.Web.Preview.UI"assembly="Microsoft.Web.Preview"/>

<addtagPrefix="asp"namespace="Microsoft.Web.Preview.UI.Controls"assembly="Microsoft.Web.Preview"/>

</controls>

This is my aspx page:

<asp:ScriptManagerID="ScriptManager1"EnablePartialRendering="true"runat="Server">

</asp:ScriptManager>

This is the error I am getting in VS:

Error 1 Element 'ScriptManager' is not a known element. This can occur if there is a compilation error in the Web site. C:\Documents and Settings\RAFAL\My Documents\development\RFMain\ImportData\MainSite\Auctions.aspx 53 10 http://localhost/ekit/

Oh, I have figured this out. It was coming from master page. This line was creating problem:

<style>

.row {

background-color:white;

}

.rowSelected {

background-color:gray;

}

</style>

hi

could you (or anyone else) explain what you changed to make this work? What was the couse of your problem?

I have the same problem but I don't understand your fixit post and I can't see how that relates to what I have here.

cheers

A

hi.

I have a similar problem here.If my page has a master page then I can't get to see the ajax tags in the content page. If the page doesn't have a master page then i can see the ajax tags.

I can't understand how your fix works - would you (or anyonw) be able to explain why it solves the problem?

cheers

A

Seems like if there is any syntax problem on the page or the master page, that is when it is happening. Not sure how to find that original syntax problem. Maybe somebody else can recommend... Try to check manually for all HTML/ASP tags, make sure all is correct, that is what I can recommend now. Do it for the page and master as well as those are joined together later...