I have BIG problem. I spent hours creating a form and yesterday. I do not know what happened or what I clicked on but when I ran the program to see if my code works. the form was completely GONE. Every button, datagrid was gone.
So I thought I have to start again? but wait, the buttons and datagrid and labels I used apparently already existed. My code is still the same. I think it might be the
InitializeComponent();
I am not sure. WHY did this happen. HOW can I get my previous design back, is it possible? The code I used before was exactly the same. The code did not get deleted.
Thank you
Related
Edit: I see "Silverlight -" is in front of my question, which I realize may have something to do with the alphabetical order of my tabs... really Visual Studio 2013 should be in front, anyone know if that can be changed?
I've been using the newer Visual Studio 2013 for about a week now, and I've found some quirks with it. The one that seems to happen the most is when I'm in the XAML editor working on something, suddenly if I go over to the property window I can't enter anything. I'm not running/debugging. I can type stuff in the regular XAML code editor window.
Even stranger, one of the times, I could get the cursors to appear in the fields. I typed a bunch of junk and just one character from what I types appeared. Another time I couldn't enter values into the properties, but I could double click on an event in the events window and create a new event handler. Just a minute ago I had the opposite, where I couldn't double click in the events window.
I think VS 2013 introduced async handling of more things, could it be related to that? Or perhaps because I'm using Silverlight? Right now my only workaround is to restart VS, does anyone have any knowledge about this? Anyone else experienced this?
I'm going to submit a bug report, but it would be a while before there's a patch, so I'm wondering if maybe someone understand the problem better and has a workaround? Or maybe just confirm that this exists and that I'm not crazy/my computer's haunted.
Edit:
I should mention another weird thing that happened two nights ago. I thought it was some how my doing, but I never figured out how I could have managed it without noticing. I was working on a piece of code, went to run after changing a few lines, and suddenly I had a ton of compiler errors. I go over to a user control I haven't touched in hours and suddenly the main LayoutRoot grid is completely empty. Luckily I'd committed to source control, but still...
I found an easy way to deal with this problem. It happens a lot after debugging so what I did was I created a batch file on my desktop containing this line taskkill /f /im XDesProc.exe and I run it every time the properties start misbehaving. Its the quickest way to reload the designer's functionality. I submitted this bug to microsoft they claim it will be included in the next update.
Me and another guy are developing a silverlight app and having the same exact problem. I accidentally found where the bug lies and how to mess with it to allow you to type "very briefly". Apparently this has something to do with tooltips. If you hover over anything in the property window when this bug is happening and allow a tooltip to popup while your cursor is blinking in a field, for the duration that the tooltip is up you can resume typing normal. As soon as the tooltip times out and disappears you can't type. So the only way you can edit or search properties is while a mouse tooltip is floating active. Very unusual. Can't seem to find any kind of tooltip settings in the program and the situation is very hard to find on google because search results assume your talking about programming tooltips. As far as I know we have had this issue since before release candidate. We are currently on official update 1 with the same problem persisting.
What the crap is this "Preparing Solution" dialog that VS 2010 shows when I open solutions? Does this show up for everyone or is something screwed up on my install?
Anyone know what its actually doing?
Here's the official history, from Cameron McColl:
In Dev10 we invested in improving solution load time by looking at making the load asynchronous. Unfortunately due to time constraints this work didn’t make it into Dev10 so instead we decided to at least make the user experience slightly better by giving the user feedback on what was going on during solution load. Initially this involved a dialog that presented accurate feedback on how many projects were being loaded along with the name of the currently loading project. Early testing of this experience revealed that there was often a non-trivial delay (i.e. the spinning donut and “not responding” window title) after the projects were loaded and the existence of the dialog made this delay very apparent once the dialog was dismissed. So what is the delay? There are 2 main things going on after the solution projects have been loaded. First all previously loaded documents/editors are reopened and for some designer files this can take a few seconds. Secondly and usually much worse we call NotifyOnAfterSolutionOpen which is an extension point in VS. Any subscriber to this event gets to run their code at this point and quite often this code is very expensive. For Dev10 we didn’t have the time to go improve the perf of all of these subscribers and so it was felt that a second dialog was required to make it clear that the Solution Load was still underway. What really sucks about the second dialog is that it doesn’t tell you what part of the code is causing the delay and worse the progress control is the marquee style which means it’s non determinant (unlike the first dialog).
Moving forward we are continuing to investigate ways to make solution load truly asynchronous and as such never show such nasty dialogs.
In the dialog's defense, our research indicates that most people prefer a modal status dialog over the spinning donut or unresponsive UI. Of course, everyone prefers no delay at all, and we’re working on that for Dev11.
Delete the solutionname.sln.docstates.suo file. If Visual Studio gets stuck reopening the documents that you had open when you last closed the solution.
It's normal as far as I'm aware. It's loading the solution file and performing house-keeping to ensure all the tools are appropriately prepared for you. Not sure what you are getting riled about.
I have been using JustCode(latest ver) for about 2 months now, and have started just turning it off most of the time.
The final straw was today when I wasted about an hour trying to find out why I was getting an error(along the lines of no overload with those parameters) when I was sure the code was correct. Finally I turned JC off and the error went away.
Why does it wrongly report errors?
Why does it sometimes disable keys like backspace in a normal code block?
Why does it sometimes color the code in an ASPX page like it is commented out(all green), when it is not(after disabling it VS colors it correctly).
There are lots of other niggly problems like if my mouse is over the word im typing intellisense will not come up etc.
So am I using it wrong or something? It really does look like a promising product from the features videos etc on their site - so I hope the problem is with me :)
Sorry to hear you had such problems with JustCode. I suppose you used the Q2 version that was released in July. Some of the problems that you describe – hiding the intellisense, blocking some keys – are problems that others have also reported and were fixed in the Service Pack that was recently released. Please, go ahead and download the latest version. It has other fixes as well than could solve other niggly problems that you may have.
In case you find yourself wondering why some error is showing while you are sure your code is correct – Visual Studio successfully builds the project – try refreshing the code analysis (in JustCode menu choose – Refresh Code Analysis). That may clear the errors. If the error shows even after that – then position the cursor onto the error and hit Alt + Enter (or choose Fix… from JustCode menu). At the bottom of the popup menu you will find Report Good Code Red. This will send over a report for the issue to the team and they’ll contact you with more information on the problem. If you are irritated from the error you can choose Ignore This Error / Warning from the same popup menu.
One thing that you can always count on is accurate and prompt response from the team. If you have any problems or suggestions – please, go ahead and write a support ticket or forum post in Telerik’s web site.
Hope this helps.
This is probably a really dumb question but i'll ask anyway.
I was wondering if there was any reason as to why a form wouldn't display its code when i click "view code" from the right click context menu in vb6?
It was working awhile ago so i'm kind of stumped.
Thanks
If forms are still not visible, try Window -> Cascade - This was the way I goit my forms visible again.
Maybe it is being displayed under something else. Check under the Window menu. Do you see it there?
Does the form display if you right click and select 'View Object'? If so, try double clicking on the form - that should display the source. You might also check the permissions to the file.
This is an old question, but since it's the first link retuned by a Google search, answering here may help many people.
Like someone else said, Window/Cascade does the trick, but with time it becomes annoying.
I have the same problem on my laptop with an external display. Closing the laptop cover (thus going back to only one display) fixes the issue.
An alternate way is to display the VB6 IDE on the main display (your main display is the one with icons on the bottom right corner). You can set your main display under System Preferences/Displays. There's a checkbox called "make this one the main display", it does not need to be your monitor #1.
Problem does not seem to occur if you have 2 displays side-by-side. Also, the fact that my laptop's resolution is not the same as the external display's resolution may cause the issue.
After taking these steps, you may have to restart the VB6 IDE to fix the issue.
When I press F5 the project compiles, and the new web page launches. However, the silverlight control loads (the standard load counter counts to 100%) but then the whole control just disappear. Only the left default menu bar (feedback etc) is visible. It's a very small project, my first actually. This also happened earlier today, but then I removed each thing one at a time and found that it was some radio buttons that caused it. I deleted them and remade them and it ran fine again. Now the same thing happened again, but it is something else, not sure yet. The question is; is this a familiar bug or am I just doing something wrong? My code-behind consist mostly of visibility changes, around 20 lines of code.
I'm not sure why this happened to me, but the error stopped occurring when I used states instead.