I have searched all over the Internet, every answer related to this topic in StackOverFlow, but nowhere could I find an answer to this specific problem, and thus I felt the need to make a thread for this.
So when I open the vs_community.exe downloaded from the official site, it shows a getting started message, and after that this screen shows up.
Problem Screen 1
As far as I have read around websites, you are typically shown a screen where you are supposed to choose the components, languages etc. But in my case, this shows up, with the setup being apparently paused?
And when I try to click on the resume button of that unconfigured setup...
Problem Screen 2
As I said earlier, I didn't find any answers anywhere, so I am confused at this point. What might be the cause of this, and is there any way to solve it?
Related
I'm developing with Qt. Following a tiny change my program now will not start up and if I run the debugger, this dialog box is displayed:
I have looked at several other answers to questions about this error and Qt, and they all propose using a different compiler or a different version. I don't believe this will solve my problem.
Searching a little more diligently on Google, I came upon this article, about Visual C++ which suggests, very plausibly, that additional information is available but has been swallowed by one of the tools somewhere. The article goes on to suggest that by changing something in the registry, you can get additional information output when the error occurs. Now, I can run my program from the command line, with minimal intervening tools, so this looked like a really useful idea. Sadly, the link in the article that I believe will tell me more about the required registry change is dead.
Does this ring any bells with anyone? How can I found out the dll and entry point that isn't being found?
Thanks to helpful comments, I managed to get the additional trace enabled using the "image files" tab of gflags.exe. I then found an enormous quantity of trace information on the "Debugger Log" tab of the QCreator debugger.
Close examination showed that the function containing the tiny chnge which kicked off this problem was failing to load.
I have no idea what caused this, but a clean rebuild of the program in question now allows it to run to the point of the original failure that made me want to make a tiny change in the first place.
I guess the moral of the story is to do a clean build immediately when things start getting weird - before trying to pin down the weirdness!
I have come across a wierd vis studio error which only had one other question I could find that is Similar.
When I try to debug the code I hit run and it says there are errors would I like to run the last working version to which I say no. This then comes up with 91 errors which slowly disappear until there are none left.
This may be quite hard to understand what is actually going on, so I have recorded it to make things a bit easier.
Link to video
I have no idea what is going on and cant seem to find anything other than that other question, which the guy did solve but the next day he turned on his computer the same thing happened, I don't want to be fixing this everyday.
Any Suggestions would be great!
Thanks
All fixed now, I still have no idea what was wrong with it. I just deleted it all and pulled it back down from TFS and it worked, it is a bit of a strange one.
So when a program dies rather ungracefully, modern versions of Windows put up a dialog that reads:
Windows is searching for a solution to the problem
It clocks for a little while, then doesn't find anything. Well, I've never had it tell me it's found a solution.
The question is, what exactly is going on when this dialog is being shown? What are possible things it can show as "solutions"? Is there a way my application can tap into it?
Obviously, if I know enough about what could go wrong, I should handle it in the app, so I'm left wondering what this actually does.
Anyone know?
Windows Error Reporting is capturing a stack trace of the failed program and sending it off to Microsoft. The data it collects is stuffed into an enormous database for vendors to research; if this is your program, you can sign up here. If the vendor submits a patch, Windows will notify you.
You can tap into it, either by customizing the info, triggering reports for (soon to be) fatal errors, and much more.
As a web developer I use Firebug constantly, and I've had just about enough of these persistent errors/warnings that always show up no matter what. One of them is the "The Components object is deprecated" error (which should be a warning) and the other is "Exposing chrome JS objects to content without exposedProps_ is insecure and deprecated".
I've taken a screen shot of the three items I get all the time no matter: http://snaps.vertigofx.com/009/snap1330_2013-03-27_06.54.41.png
Sometimes I get other errors/warnings, too, and like the ones I already mentioned they are not related to anything I am working on, so I just have to try to ignore them. However no matter how "used to them" I may think I be, when I see that red text I automatically think I've broken something and it just bugs me.
I just recently upgraded Firefox to 19.0.2. Before that the errors/warnings were even worse, but they're still not gone. I've found one forum thread on the internet regarding the "Components object" one and the original poster said he got it to go away but wasn't specific enough on what that was.
Anyway, if anybody knows what I can do to rid myself of these, I would really appreciate it.
I've Googled around a bit on this issue and haven't been able to come up with anyone else having an issue to this one, so a) I apologize if this is a known issue; and b) I'm thinking this proves that I must be doing something horrifically wrong, yeah? :-)
My application has a very rich landing page which is the first page that is shown after a new launch. It has a panorama control, a large background image (but much smaller than the 2000x2000 limit) and recurring and ongoing animations. Prior to updating my tools to the January refresh, this page ran relatively smoothly. After updating and running the app in the emulator, the background of this page is white (despite the fact that the emulator is on the "dark" theme), performance is quite poor (both in terms of swiping through the panorama and in terms of my recurring animations). When I run the same project on my device, all is well (since, quite obviously, my device's OS is not on the updated image).
Clearly I must be doing something grievously wrong to merit such a cataclysm, but I'm not sure what it might be. I've tried disabling bitmap caching in the places where I'm using it, removing third party tools I'm using such as Peter Torr's awesome tilt effect and his memory usage counter, and several other hail-Mary-style moves, and the problem remains. I also looked through the provided resources and change log to see if perhaps something related has changed, but I didn't see anything.
I'll try to provide example code later if it would be of any use to any would-be saviors out there, but the app is pretty complex and large in terms of lines of code and file size, so it might be a bit tricky. i just thought I'd toss this out there and see if anyone might happen to see it and think of an obvious solution.
Thanks so much in advance for your time and help.
P.S.: I cross-posted this question on the official WP7 dev forums. Sorry if that's against the rules - I'm not a regular SP-poster, as you can tell. If it's a problem, let me know and I can delete the other post.
I was ultimately able to resolve this by creating a brand new project using the updated tools and copying my code, assets, and relevant project settings into it. The app now runs flawlessly on the emulator (or, at least, the flaws in it are my flaws and not the emulator's :-)).
I believe I originally created the project on an earlier version of the SDK, so maybe I had some kind of invalid or incorrect project settings. If I get a moment later, I'll compare the project files to see if I can identify a setting or difference that explains the disparity.
Thanks to all who looked (and to Matt, who even responded :-)). I'll report back if I have any more information that might be of help.
UPDATE: Updating for anyone who might be having this issue as well - my resolution above was a false positive. Creating a new solution and copying stuff in does indeed work, but only until you save and close the new solution. Upon reopening, the problem recurs. Grrrr. I'll post back if I come up with anything else.