Home Dashboard Directory Help
Search

Error Creating Control - Button 1 by Caddis1


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 328345
Opened: 2/12/2008 8:24:11 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I cannot add anything to a new ASP.NET web site without an error. For example, when I try to add a button, I get the following message - "Duplicate component name 'Button 1'. Component names must be unique and case-insensitive."

The following warnings also show up in the error list:

Warning    1    Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.    C:\Users\Owner\Documents\Visual Studio 2008\WebSites\WebSite3\Default.aspx    14    17    C:\...\WebSite3\

Warning    3    Unrecognized tag prefix or device filter 'asp'.    C:\Users\Owner\Documents\Visual Studio 2008\WebSites\WebSite3\Default.aspx    14    6    C:\...\WebSite3\

Warning    4    C:\Users\Owner\Documents\Visual Studio 2008\WebSites\WebSite3\Default.aspx: ASP.NET runtime error: Child nodes not allowed. (C:\Users\Owner\Documents\Visual Studio 2008\WebSites\WebSite3\web.config line 118)    C:\Users\Owner\Documents\Visual Studio 2008\WebSites\WebSite3\Default.aspx    1    1    C:\...\WebSite3\

Details
Sign in to post a comment.
Posted by jwoodruff on 11/7/2008 at 4:53 PM
Uninstalling the .NET 3.5 framework and reinstalling it with a freshly downloaded copy took care of this problem for me.
Posted by Microsoft on 3/31/2008 at 9:11 AM
Hello

Most probably .NET framework assembly version is incorrect: System.Design.dll and System.Web.dll should be 2.0.50727.13xx or later. Try uninstalling 3.5 and 2.0 frameworks and reinstalling them.

Thanks
Posted by Microsoft on 2/19/2008 at 1:55 AM
Thanks for your response. We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Caddis1 on 2/16/2008 at 11:27 PM
This was what I got when I ran .Net validation tool.

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Owner>NetFx35_detect_issues.bat
THE FOLLOWING SCRIPT will check to make sure that .NET Framework 3.5
is installed properly and will tell you what is not configured appropriately
WINDOWS VERSION: 6.0.6000
POTENTIAL ERROR: REGISTRYDUMP: reg query "HKLM\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v2.0.50727" /v "SP"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727
    SP    REG_DWORD    0x0

ERROR: NetFx2.0 SP1 is not installed
POTENTIAL ERROR: REGISTRYDUMP: reg query "HKLM\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v3.0" /v "SP"


ERROR: The system was unable to find the specified registry key or value.
ERROR: Netfx3.0 SP1 is not installed

C:\Users\Owner>
Posted by Microsoft on 2/14/2008 at 1:30 AM
Hi

Regarding your case, the underlying issue maybe that the .Net Framework is not updating correctly.
In order to short circuit diagnosing that you're in this state, one of my colleagues on the deployment team has written a tool that will tell you whether or not the .Net Framework is installed correctly or not.
If you are having issues, please take a look at this tool http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx.
It will tell you whether or not your .Net Framework installation is correctly installed.
After that, have a look at this tool to collect log files: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx
Once you have collected this information, please attach it.

Thank you and sorry for any inconveniences.
Kylin
Posted by Microsoft on 2/12/2008 at 11:58 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided. We tried to repro with the following steps:

1. repro this issue on Windows XP SP2 with VS 2008
2. repro this issue on Windows Vista Ultimate with VS 2008

It may help if you provide us with:

1. more snapshots.


If we do not receive a response from you after 7-days , we will automatically close your issue. There is no obligation to respond -- at any time you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Sign in to post a workaround.