RE: Cannot change any control id in vs2005 web project



Hi Brad,

From your description, you're encountering some problem on renaming control
ID in ASP.NET 2.0 project's webform designer/properties windows, correct?

Based on my research, the problem you're suffering is likely due to an
existing issue of the Visual Studio 2005 IDE. The Visual Studio 2005 IDE
will create some temp files to record some design-time settings and status
info of web application projects. And these files will be stored in a cache
storage on the machine. Generally this storage is per logon user specific
and stored in the following location:

"%userprofile%\Local Settings\Application Data\Microsoft\WebsiteCache"

And each web project will has a own sub cache directory under it. The
problem here is that under some certain condition, the cache directory of a
certain ASP.NET 2.0 web project is deleted (manually or by IDE due to some
problem), then the next time the web appliation is opened, we'll get error
when try renaming control id on designer surface(properties windows).
Our product engineers have addressed this issue and specially file a public
bug on the product feedback site so that other community member and users
and find it. Here is the link to this issue:


#Renaming of control fails with error on designer surface
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac
kID=101992

In this bug report, you can find that there are several conditions that
could cause the problem and it has provided two workarounds. I'll paste the
workaround here for your convenience:

===========================
There is a bug in Visual studio that when you have more than one instance
of the IDE open and close a web-site it will delete the WebSiteCache
directory of other web-sites. This is the common way to get into this
situation. However, you could also get into the situation by deleting the
directory manually (per the repro steps of this bug report.)

The quick fix is to make VS re-build the web site cache:
a) shut down all instances of VS
b) remove cache from command prompt> rd /s /q "%userprofile%\Local
Settings\Application Data\Microsoft\WebsiteCache"
c) re-open your web site and the cache will be re-created

An alternative method to fix the one web site without deleteing the entire
cache is the following:
a) shut down all instances of VS
b) open "%userprofile%\Local Settings\Application
Data\Microsoft\WebsiteCache\websites.xml"
c) locate the entry for your web site and get its CacheFolder name. Usually
the name of the web.
d) Ensure a sub-directory of that name exists under "%userprofile%\Local
Settings\Application Data\Microsoft\WebsiteCache\"
===========================

Since this is an known issue and planed to be fixed in the next version or
service pack, if you find that the above workaround still not quite address
your problem or you need a rapid hotfix, you can consider contact the
Microsoft CSS for a hotfix against this issue.

Hope this helps. If there is anything else we can help, please feel free
to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial

response from the community or a Microsoft Support Engineer within 1
business day is

acceptable. Please note that each follow up response may take approximately
2 business days

as the support professional working with you may need further investigation
to reach the

most efficient resolution. The offering is not appropriate for situations
that require

urgent, real-time or phone-based interactions or complex project analysis
and dump analysis

issues. Issues of this nature are best handled working with a dedicated
Microsoft Support

Engineer by contacting Microsoft Customer Support Services (CSS) at

http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.





.



Relevant Pages


Loading