|
|
Rank: Newbie
Groups: Member
Joined: 9/17/2009
Posts: 3
|
Hi Essential Objects,
The problem that I have is when I try to insert a menu into a existing project.
When I slide the object into the page a message box appear with following text:
Attempted to read or write protected memory. This is often an indication that other memory is corrupt
doyou know why?
I was searching the reason, and I made a new project and i slided the menu object and it works good in that, but i don´t want a new project, i just want to put the menu into a existing Web Application.
Thank you very much!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
This appears to be Visual Studio bug and unfortunately we do not know the root cause either. Creating a new project does seem to correct the problem. Another thing you can try is to delete the .suo file (if you have one) and see if it helps.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/4/2012
Posts: 2
|
I am using VS2010 and have deleted the .suo file and the problem still exists. Do you have any other recommendations?
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
No. Unfortunately no we do not have any other recommendations because we do not know the root cause of this issue. You may want to contact MS about this.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/4/2012
Posts: 2
|
Do you have any plans to look into this? I am evaluating your product but can't seem to get past this. Is there an alternative method I can use to design the menu?
I have created a new project with a master page.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
No. We do not have any plan to look into this. We are quite sure this is an issue on MS's side and since Visual Studio is black box to us, there is virtually nothing we can do for this case. We might be able to "guess" something around and hit a way to avoid this, but without knowing the root cause, there is no way for us to guarantee it won't happen again when MS "might" break it again --- maybe after a security update or something, or you "might" trigger it again with some other change in your project. The bottom line is we do not have the ability chase a MS bug. As such at this moment the only alternative is to use a new project, or if you are willing to spend time on it, try to compare your old project and new project to find out what might be triggering that problem.
Thanks!
|
|