Configuration :: Unrecognized Attribute "targetFramework" Note That Attribute Names Are Case - Sensitive While Hosting
Nov 29, 2010
i'm trying to host an .net framework4.0 application in IIS7. i got an error while clicking on the manage module in modules .like ("Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive. ") .I changed my application poll to .net4.0.I am able to browse my application
</system.serviceModel>
</configuration>
View 5 Replies
Oct 20, 2010
I installed Microsoft Visual Studio 2010 Ultimate Trial and converted existing asp.net 2.0 web application and I am getting this error: znrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive. It's coming from this section in the web.config which was auto-generated by VS2010 when I converted the project:
<compilation defaultLanguage="c#" debug="false" targetFramework="4.0">
<compilers>
<!--<compiler language="c#" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" extension=".cs" compilerOptions="/d:DEBUG;TRACE" /></compilers> -->
<compiler language="c#" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" extension=".cs"/></compilers>
<assemblies>
<add assembly="Microsoft.JScript, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies></compilation>
View 1 Replies
May 7, 2010
I just download XAMPP, and it is running in my local computer. I added the index pages, and it works fine. However, when I copied my pages and all related information,I tried to access the page. Then, it displayed the error message below.
Parser Error Message: Unrecognized attribute 'requestValidationMode'. Note that attribute names are case-sensitive.Line 31: <system.web>Line 32: <httpRuntime requestValidationMode="2.0"/>Line 33: <trace enabled="true" requestLimit="40" localOnly="false" />
Note: The <httpRuntime requestValidationMode="2.0" is required because I am using a chkeditor with a textbox to create a microsoft word like effect. I remove itfrom the web config file, but then I get a similar error. This time, it was complaining about <add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
View 9 Replies
Apr 15, 2010
I have an XDocument that looks similar to
<root>
<a>
<b foo="1" bar="2" />
<b foo="3" bar="4" />
<b foo="5" bar="6" />
<b foo="7" bar="8" />
<b foo="9" bar="10" />
</a>
</root>
I wish to change the attribute foo to something else, and the attribute bar to something else. How can I easily do this? My current version (below) stack overflows with large documents, and has an awful smell to it.
string dd=LoadedXDocument.ToString();
foreach (var s in AttributeReplacements)
dd = dd.Replace(s.Old+"=", s.New+"=");
View 2 Replies
May 10, 2010
I am trying to host a web site developed by me on my windows server 2003. I used visual studio 2008 and sql server 2005 for developing.
I copied the file into my root folder of iis and when i right click and click browse it gives the following error.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Server Error in '/' 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: Unrecognized attribute 'type'.
Source Error:
Line 10: <configuration>
Line 11: <configSections>
Line 12: <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
Line 13: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
Line 14: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
Source File: D:Inetpubwwwrootpublishweb.config Line: 12
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2379; ASP.NET Version:1.1.4322.2379
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is my webconfig file
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the web admin tool to configure settings for your application. Use the Website->Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in WindowsMicrosoft.NetFrameworkv2.xConfig
-->
<configuration>
<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>
<appSettings/>
<connectionStrings>
<add name="ADConnectionString" connectionString="LDAP://test.testdomain.com/CN=Users,DC=test,DC=testdomain,DC=com" />
<add name="testareaConnectionString" connectionString="Data Source=SHARADVI;Initial Catalog=testarea;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString2" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString3" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString4" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString5" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString6" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString7" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString8" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString9" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString10" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString11" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString12" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString13" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString14" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString15" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString16" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString17" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString18" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString19" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString20" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString21" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString22" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString23" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ebusinessConnectionString24" connectionString="Data Source=SHARADVI;Initial Catalog=ebusiness;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="false">
<assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
</compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Forms">
<forms name=".ASPXAUTH" loginUrl="login.aspx" defaultUrl="default.aspx" protection="All" timeout="30" path="/" requireSSL="false" slidingExpiration="true" cookieless="UseDeviceProfile" domain="" enableCrossAppRedirects="false">
<credentials passwordFormat="SHA1"/>
</forms>
</authentication>
<authorization>
<deny users="?"/>
<allow users="*"/>
</authorization>
<membership defaultProvider="MyADMembershipProvider">
<providers>
<add name="MyADMembershipProvider" attributeMapUsername="sAMAccountName" type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="ADConnectionString"
connectionUsername="testadministrator" connectionPassword="password"/>
</providers>
</membership>
<!--
The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
<pages>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</controls>
</pages>
<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>
</system.web>
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="OptionInfer" value="true"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
</compilers>
</system.codedom>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary for previous version of IIS.
-->
<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules>
<remove name="ScriptModule"/>
<add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</modules>
<handlers>
<remove name="WebServiceHandlerFactory-Integrated"/>
<remove name="ScriptHandlerFactory"/>
<remove name="ScriptHandlerFactoryAppServices"/>
<remove name="ScriptResource"/>
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</handlers>
</system.webServer>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
View 1 Replies
Jan 21, 2010
we are making a project to run in ASP.Net on Mono/*nix Our problem is that we develop on Windows, and we just build and test it every so often on Mono. So we have been having a lot of trouble recently with case sensitive filenames. Everything seems to work good in Windows and then we move to Mono and it's silently broken.(as in, it builds but won't run or parts of it don't work)
How would you recommend that I detect this while we are developing on Windows? Basically, how do we make the case-sensitive filenames look wrong in our code where the code works on Windows but not *nix?
View 2 Replies
Nov 18, 2010
To start with then we have a LinkButton whose text is actually an image tag. The image it links to is a Png and resides in a folder in the web directory. This is IIS V6 and win Server 2003.
The path is [URL]
Admin is a virtual directory configured in IIS.
The above url doesn't work but if you change it to [URL] (lowers case 'a') then the image is served, change it back to 'A' and it takes you to login, you log in and it loops back to log in. change to 'a' and voila the image is served. Weirdly this problem doesn't always occur and I have hunted for a resolution for days to no avail.
As requested this is the complete link button
<asp:LinkButton ID="lnkCommitAll" runat="server" CausesValidation="false"><asp:Image ID="imgCommitAll" runat="server" ImageUrl="~/Images/Grid/confirm_16.png" AlternateText="Commit All Changes" /> Commit All</asp:LinkButton>
View 1 Replies
May 1, 2010
I have a ASP.NET site, in which i have to register the dlls which i have created in VB.NET. I configured this project on Win2003 Server and register the dlls. It was working fine.
But when i rehosted it on same machine but by different folder, and try to register the dll, it is showing me the following warning.
C:WINDOWSMicrosoft.NETFrameworkv2.0.50727>RegSvcs f:homeintermeshweberp1BinIndiamart.dll Microsoft (R) .NET Framework Services Installation Utility Version 2.0.50727.3053 Copyright (c) Microsoft Corporation. All rights reserved.
WARNING: The assembly does not declare an ApplicationAccessControl Attribute. Application security will be enabled by default.
Installed Assembly:
Assembly: f:homeintermeshweberp1BinIndiamart.dll
Application: Indiamart
TypeLib: f:homeintermeshweberp1BinIndiamart.tlb
View 1 Replies