Difference between runtime and debug - c#

I have a very odd problem. I've written a little inhouse app which scrapes a load of URLs, performs HEAD requests to get the size and populate a ListView control. Everything works fine when I am running it inside Visual Studio when debugging, but when I deploy the listview does not populate. The 2 are making exactly the same calls consistently. Does anyone have any idea what may cause this to happen?

Thanks I was able to find the solution by attaching the debugger to the process... many thanks to all for answering. I know this is a trivial question...
Many thanks
JT

Related

Is there a way to debug the usage of polyfill scripts?

I am using WPF to display a Openlayers map in a program. But when starting it, i get this error, which doesn't really tell me anything at all:
The Error-Popup
Interestingly enough i can still load it in Internet Explorer (which is used internally by WPF).
If anyone could tell me how to properly debug this problem i would be quite thrilled.
Thanks in advance!

Slow UWP performance

I have a problem with slow UWP performance. I know that this topic was discussed a lot of times, but everything is from 2017 or older, and nothing was useful for me. In short, the more times I change application's pages, the more lagging I have.
I tried all combinations: disabling and enabling option Compile with .NET Native tool chain, switching between Debug and Release mode, I wrote application native way and in Xamarin.Forms (Android works good what's interesting) but every time I had problem with UWP. The method I use to going to other page:
this.Frame.Navigate(typeof(Page2));
So my question is, if anyone solved problem with lagging, or is maybe other method for switching pages?
Finally I found the solution. In my case the problem was in handling my UserControl toolbar - too often refreshing data. I added longer Task.Delay to my infinite loop that was refreshing data on toolbar and now everything works fine.

Visual Studio 2015 C# when typing it keeps going gray?

Whenever I attempt to write in VisualStudio2015 this occurs, where when I try to write, it works out fine for 1-3seconds, then the line I write on goes gray. It does not matter where I position my mouse, I tried with another keyboard to check if any keys were stuck, did not help.
This issue started to occur when I upgraded my PC to Windows 10. Tried several restarts etc.
Please help. This really gets annoying when trying to code :/
I am very bad at explaining my issue here, so please watch this gif to understand. Basically whenever I try to write, that line I am on grays out, leaving me unable to do so: https://gyazo.com/688a5660b29a3d93c0bb426715bcf038
Issue shown
After almost a month I found out the issue was that my CS:GO was opened meanwhile, and it somehow interferes with my Visual Studio and other programs. Thanks for your help though.

Is there a way to use Edit And Continue when debugging a Prism application?

we are developing a Prism application and as all modules are loaded using Reflection thru the Bootstrapper we cannot use the "Edit & Continue" feature which certainly increases productivity.
Is there a way to overcome this problem?
Thanks.
I could manage to get Edit and Continue working with Prism! A few days ago i tried Edit and Continue with an Prism-Module and failed. Today i tried it again and what makes the difference is that i first test Edit and Continue with the Main-Project. I debugged the shell-view model and made than some changes in the source and Edit and Continue works as expected. After that i go to a module and surprise Edit and Continue starts working in the prism-modules. Maybe you can reproduce this behavior and report if it works. If not, we can go on and compare our projects to find the difference.
Regards
Christoph

.Net Custom Components "disappear" after file save

I might have a hard time explaining this because I am at a total loss for what is happening so I am just looking for some guidance. I might be a bit wordy because I don't know exactly what is the relevant information.
I am developing a GUI for a project that I am working on in using .Net (C#)
Part of the interface mimics, exactly, what we do in another product. For consistency reasons, my boss wants me to make it look the same way. So I got the other software and basically copied and pasted the components into my new GUI.
This required me to introduce a component library (the now defunct Graphics Server GSNet, so I can't go to them for help) so I could implement some simple graphs and temperature/pressure "widgets."
The components show up fine, and when I compile, everything seems to work fine. However, at some point during my programming it just breaks. Sometimes the tab that these components are on starts throwing exceptions when I view the designer page (A missing method exception) so it won't display. Sometimes JUST those components from the GSNet library don't show up. Sometimes, if I try to run it, I get a not-instantiated exception on one of their lines of code in the designer code file. Sometimes I can't view the designer at all.
No matter what I do I can't reverse it. Even if I undo what I just did it won't fix it. If it happens, I have to revert to a backup and start over again.
So I started to backup pretty much every step. I compile it and it works. I comment out a line of code, save it, and then uncomment that same line of code (so I am working with the same exact code) and the components all disappear. It doesn't matter what line of code I actually comment out, as long as it is in the same project that these components are being used.
I pretty much have to use the components. . . so does anyone have any suggestion or where I can look to debug this?
The only thing that comes to mind is a read-only bin directory. I've found that .NET has trouble if the interop libraries in the bin directory are read-only. Read-only interops generally prevent controls using those interops from displaying in the form designer and thus mess up compilation (if you do a full build anyway). A rebuild might let you get the app running and then fail when it reaches the part using the read-only interop.
This may or may not be your problem but it's all that comes to mind.
I know this is very late to the game, but I just ran into this same problem.
I'd pulled down one of our applications from SVN, and when I first tried to open the main form for editing, I was prompted with the custom component not being defined in the software, even though I could plainly see it as a class. I was given a choice to ignore it, which I did, and the custom control promptly disappeared from the form (still showed up in the project).
So at the suggestion of my colleague, I deleted the instance from my hard drive, and re-checked it out from SVN. Before i did anything else, I built the project for both release & debug, and that fixed the problem.
Maybe this'll help someone else who finds this SO question when they run into this.

Categories

Resources