Take the 2-minute tour ×

for a few days i have a problem with my visual studio here. everytime i want to open an Android landscape layout (default layouts load normally) it tells me "The Operation could not be completed: Üngültiger Zeiger" (Invalid Pointer) (english studio on a german Win 7) i've found some threads in different forums, but most were related to a font change, what i never did. my font is Consolas right now

another thing i found was this one: Link
but i never found those lines in my .csproj files

so... what is wrong here?

share|improve this question
this problem just started again –  EaranMaleasi Jan 22 '13 at 15:10
Having a similar issue, but with editing an ASP.NET page. –  mikeTheLiar Jan 29 '13 at 19:18

2 Answers 2

up vote 0 down vote accepted

I had a similar issue, and for some strange reason, renaming the solution file (.sln) to something else resolved the issue.

I haven't figured out why though.

share|improve this answer
thanks for the answer but i can't test it, because i did sth i don't know anymore (maybe deleting and recreating the layout files). but if this happens again i wil sure test that –  EaranMaleasi Jun 7 '13 at 6:10
So did this work or not? I did what is described here and it didn't work. You claim that you couldn't test it but still marked the answer as correct. –  DaveDev Jun 18 '13 at 10:18
maybe try to delete the files (not only in VS but in your VS folder on your PC. sometimes VS tells me its deleted but it was not..) and recreate them. copy all you have done in the old files into the new ones and it could work. –  EaranMaleasi Jun 20 '13 at 6:40
I got this error when trying to open a xaml file, but I got the exact same error, so I figured the designer had the same mishap. Since there are a few "solutions" to this I just wanted to get this out there in case it helped someone else. –  Patrick Jun 20 '13 at 11:36

I was having this problem briefly, I immediately came to this thread and renaming the solution did not work for me. However, once I restarted visual studios and reopened the issue went away (and has not come back since).

share|improve this answer

Your Answer


