Would like to seek your help regarding a Data Viewer bug. I am performing a simple Extract and Load with Data Viewer enabled. However when run the Data Viewer screen did show up, but it displayed a blank screen (like when an app is not responding) without any visible data or actionable buttons - Play, Detach, Copy Data...
I tried to disable and re-enable Data Viewer multiple times but still not working.
Any idea what the cause is ?
Thank you
Try opening Visual Studio in safe mode using the following command:
devenv.exe /safemode
If it works, then there are some add-ins that are causing this issue.
thanks a lot guys ! Finally the fix is to reinstall visual studio and the add-ins again.
Related
I worked on a Console Application with a friend today. Is it possible to share the default console during a Live Share session? What I mean is that we had to compile and run our program manually through the default Windows Terminal to see output(which wasn't the best idea, there was a ton of empty lines displayed every time we would input anything), and debugging was impossible because we just couldn't see the console (only the host could).
According to the docs, it's possible to share the terminal in both VS Code and Visual Studio, but I don't think there's a way to share the console that comes up when you debug a console app. The solution I see is simply sharing a terminal, running your app in it manually and if you want debugging, you can try attaching the VS debugger to the console app's process after you start it manually by following this guide.
I have a really tricky problem and I can't find out how to solve it.
I created a UWP app with notification feature, saving all the data into .txt files in the App's LocalFolder.
The problem is that, when the UWP creates succesfully a notification schedule (saving all the notification data into this .txt file correctly)... the app just crashes when restarting it!
The most strange thing is that if I try to rerun the app itself by recompiling from VS, it doesn't crash... but it can't get data saved in that .txt file yet.
So, I was wondering how to simulate app restart in VS 2017, without needing to interrupt the debugger, as I need it to find out this problem that's making me crazy.
Thank you all for the attention.
Best regards.
http://developer.nokia.com/community/wiki/images/thumb/9/9c/One.png/360px-One.png
http://developer.nokia.com/community/wiki/images/thumb/9/9c/One.png/360px-One.png
The image in this link shows some unidentified UI portion on the top right of the screen. Can someone please describe why it keeps on showing ?
I am unable to identify and correct it.
These framerate counters only shows up in development when the debugger is attached. You'll notice if you run your app when Visual Studio isn't connected and running this UI will disappear.
Here's some more info about it:
http://msdn.microsoft.com/library/windows/apps/gg588380(v=vs.105).aspx
And how to hide it if your really want to:
https://stackoverflow.com/a/5393504/250254
http://www.jeff.wilcox.name/2010/07/counters/
I'm working on a Windows Phone 7.1 project and got most of my work done and decided to add to the project the images for my tiles (62x62 and 173x173 PNGs) plus the JPG file for the splash screen (SplashScreenImage.jpg 480x800).
Before adding these images to the project my project was running fine! After adding them and setting the tiles images to the 2 new files, my project still builds ok, but when running on the 7.1 simulator (my acer laptop doesn't have hardware assisted virtualization enabled in order to run the wp8 emulator) the app crashes when trying to load MainPage with "The parameter is incorrect" exception (in the Application_UnhandledException handler).
I've been trying to find a solution on the web for the last 1-2 days, found few mentions of this error and few possible causes, but none of my findings helped so far. The exception doesn't say anything helpful and it's getting really frustrating considering that most of the serious work is done and I'm very close to releasing the app to the marketplace.
Did anybody run into this issue before? Any ideas what could have gone wrong and how I could solve this exception? Any help is much appreciated!
Thank you in advance!
Andrei
Whenever I wish to change the Splashscreen and other images, here is what I do:
Locate the file on disk using Windows Explorer.
Open the file using some image editor (I use Paint.NET)
Remove the default image and replace with your image maintaining the dimensions.
Save the image and return to Visual Studio.
Rebuild the entire project.
This works seamlessly without any errors. ;)
I have a simple Windows Phone 7 application which is working perfectly when started from Visual Studio. However, if I deactivate the app (press Windows button or back button from the application's MainPage) and then click the app's icon to relaunch, the screen will flash and return to the list/home screen. I assumed this was an issue with the emulator but when I got a developer device I have the same issue.
Note that reactivating without a complete tombstone works (pressing Windows button from the app and then back).
I have no idea what causes this or how to proceed with debugging. Hopefully someone else has experienced this and knows a fix.
Turns out there is a bug, i found the solution here http://forums.create.msdn.com/forums/p/67522/416995.aspx
In short, it turns out that the Microsoft.Xna.Framework.Media.MediaLibrary class (which I am using to display pictures on applications main page) is not properly initialized when the user has not opened a media hub prior to you calling it. So picture collection properties are null or empty. The solution is to add a call to MediaPlayer.Queue.ToString(), it will force the initialization of the native media library allowing you to invoke the MediaLibrary later on.
Sounds like an unhandled error on startup is causing the app to crash.
Trap/log/handle/display any unhandled exceptions. Also check what you're doing on startup.
IF you are saving something (to Isolated Storage) after first run and then opening it on subsequent launches then that's where I'd look first.
If it works when launched from Visual Studio then this will probably be due to the way you are rebuilding/redeploying the app before launching it in that case.