I have just a form in my VB.Net project and even when I try debugging that - there is nothing going on besides the form being loaded - I get the error:
No symbols are loaded for any call stack frame. The source code cannot be displayed.
I've tried using this solution from StackOverflow, but this is either oudated or pertains only to C++. I've also tried using this article from the MSDN Forum, however, this also did not seem to help as I wasn't quite sure what the answer was telling me to do.
Has anybody else came across this problem and found a solution? It's very frustrating that I'm receiving this error and I only have a form showing up.
Edit: I found another solution here but I don't quite know what that means ... yet. I was going to look into this but I'd really like to know why this doesn't work when Application Framework is enabled.
Make sure you are running in debug and not release. Build>Configuration Manager>Active Solution Configuration = Debug
Get rid of all compiler warnings/errors and rebuild. Look at your Sub New() and form_load events closely. Dodgy form inheritance can cause this. Dodgy module level vars also. From memory even when you fix the problem you need to rebuild to get the designer back. Might be a my.Settings issue.
Sorry for imprecise advice, I have had this problem before but I cannot remember the details.
A quick workaround is to just uncheck "Enable unmanaged code debugging" and "Enable the Visual Studio hosting process" in the Debug section of the Project Properties.
Related
I just downloaded the trial for this application and it doesn't seem to work. I went through the Quick Setup guide and it all looked great. Now when I place my cursor on a member of any type and press Ctrl+Shift+D it does nothing. I placed it on top, inside, etc... Nothing. If I press Ctrl+Shift+A (twice) on top of the member it tells me to place it "in the line of the form MyType myVariable;". I'm not quite sure what this means unless it's referring to C# but this project is VB.NET which it doesn't seem to recognize. Anyone else have this issue? I was hoping it would make things easier since I've read that it can document an entire document rather than having to member by member.
Using VS 2010 Premium.
Drop me an email to support (at) atomineerutils.com with a bit of example code that exhibits the problem, and I'll help you sort it out.
(edit)
Please note that AtomineerUtils only officially supports VB 9 onwards, although where the syntax of earlier versions is compatible (i.e. in most cases), it will still work perfectly well.
I've now investigated this, and I can't repeat the documentation behaviour you have mentioned - it works as expected for me. (However, I did find and fix a regression introduced to the Visual Basic handling in a recent version - a small coding glitch that meant some methods could be incorrectly documented as constructors, so thanks for indirectly helping me find this issue!)
All I can suggest is that if you see a problem in any application, the best (and often only) way to get it fixed is to let the author know!
I have a program in VB.NET that has a webbrowser contorl. I wanted to zoom on a page and i found a tutorial online that involved something like this
webbrowser1.ActiveXInstance.ExecWB(OLECMD...
When i went on and typed it on, there's nothing called ExecWB.
Why is that? Is it because i'm using IE9?
I'm using Visual Studio 2010.
I think the problems with IE9. When i tried the same thing in VB6 (with a different code that is), i get an error "Method ExecWB failed to initialize" or something like that.
So, how can i fix this?
Security setup.
Initialization and script execution of an ActiveX control which are not marked if safe even if it performs a script.
It operated, when it was except invalidity.
I have a project in which I'm taking reference of another library. I have changed something in the classes of reference project. How do i find that crash is occurring because of the changes. Gdb shows nothing when application crashes.
The simpliest way i see is testing without the changes you made, and see if the app is still crashing...
If you find out the modifications are not the source of crash, post some code, it will be better to solve your problem.
Is there anyway to disable the vb.net (2008) express popup for converting older projects as well as the security warning to browse the project? I'm fairly new to vb.net so of course I download lots of examples to learn off of and it is BEYOND annoying to have to convert every demo and then click ok to browse the code.
Is there no way to set defaults for this?
I don't know if it's possible, but I don't recommend it anyway. The conversion process is there to make sure that your code works as expected in newer versions.
VB does a lot behind the scenes to make the project work. Stuff we never see unless we go looking for it. These things can change between versions (namespaces and classes get added or removed, renamed or restructured), and if you don't convert, you could find yourself with an application that does nothing useful...
We have 3 developers all using the same version (VS 2008 SP1) and we all use large VB projects (windows forms). From time to time, the IDE will have all sorts of issues such as locking up, crashing, and even not being able to drag a form object around or it will just instantly disappear.
On the largest of our projects (which is actually 5 projects in one solution file), a couple people here can only rebuild the project for testing 2 - 3 times before they have to close the studio and reopen it.
Has anyone else experienced this? Does this happen with large C# projects?
Yes, I experience this all the time! It has gotten better in 2008, if you can believe it.
I usually find that the reason has to do with an exception in my own code. The UI might bring in a custom control that does not behave well in design mode, causing the problem.
Sometimes, I will bring up a second execution of VS2008 and attach the debugger to the first execution of VS. Then, I can debug my own code as it is being run in the designer of the first instance. Often, an exception is thrown and I can fix my code to play better in the designer.
In other circumstances, I have no idea why it happens.
I have heard of people having this issue, however, I have never had an issue at all myself.
I have heard that a number of people trace the issues back to the use of ReSharper as the primary cause.
The most common problem I've had that causes the designer to crash is when I create a form where the only constructors require parameters.
To alleviate that, when I need the form only to be instantiated with parameters, I create a private parameterless constructor that the designer can use but which the form's consumers won't see.
I have personally experienced all sorts of designer wickedness with VS2008 sp1. I uninstalled the service pack to return stability to my dev environment. This is an unfortunate answer, but give it a try.
Only thing I've had close to this is the design view crashing and bringing up an error, formerly causing me to have to recreate the form and copy and paste the code across until I learnt how to fix it.
My problem was occurring because of me using ctrl+f a lot though. If you are using big files, this might be what's happening.