I use Visual Studio 2008 and it really makes me crazy how it shows error messages (in Error List window, Output window - especially exceptions) partially in English and partially in my native language. Interestingly, it is worse in WPF than in WinForms project. I've read here that it is about Culture of the running thread (so that the problem is in a settings for .NET).
Why am I solving it? It's simple because if I run into an error message and I don't know what it exactly mean or how to fix the problem then trying to google the problem in any other language than in English is very problematic. For example, it would be useful to set English for debugging purposes.
How to solve the problem?
Thanks for any suggestion!
Have you checked what your VS language settings are & compiler messages are controlled by your OS language settings & what language packs you have installed for the .Net framework...
See this link for some more information.
http://finderr.net/search -- Not entirely an answer but it really helped me a lot.
Related
I'm currently migranting an VBA powerpoint add-in to VSTO.
For weeks I've been struggling with Visual studio degug for COM objescts. AS you can see on the image below, the object types show {system._ComObject} and object inspection becomes a challenge since one must use the dynamic view, which is quite inconvenient in my opinion.
Looking around I've found a recommendation to activate the option "use managed code compatibility mode" in the general debugging settings, as you can see on Debugging setting
I also followed another the recommendation to set the property "Embed interop Types" on all my office related references to false.
After applying these changes. Voilà! The inspection began do work just as I wished to and as you can see here: Debug working properly
I was almost in heaven. My ecstasy lasted till I tried to change some code during debug and was informed by visual studio that
"managed compatibility mode does not support edit and continue".
Now I'm back in hell. With edit and continue I miss a decent COM object inspection. With COM inspection I cannot change code during debug.
This situation looks awkward and I would expect more from VS 2017.
Does anybody know how can I get decent COM inspection and edit and continue at the same time?
Does anybody know how can I get decent COM inspection and edit and
continue at the same time?
I am afraid that you cannnot get what you want.
Since you just debug a com object which is more like optimized, mixed, or SQL Server common language runtime (CLR) integration code(use ), as the official document said, Edit and Continue function does not support it.
Usually, to debug those mixed codes in VS, you should enable Use Managed Compatibility Mode or enable native code debugging, but those options cannot work well with Edit and Continue as the official document said.
You can check this document to know unsupported changes or supported changes to code.
So for your issue, there is no such option to use both of them.
As a suggestion, you should break the debugging process first, make some changes to your code. Then start Debugging to debug the new changes.
Besides, if you still want this feature, you could suggest a feature on our User Voice Forum. The Team will check your request carefully and hope they will give you a satisfactory reply.
Good Morning,
I wanted to know if there is any program that can identify which component is causing a run-time error 430. I know enough to debug using VB6 IDE however its a strange case since the error does not occur when in the IDE. I have checked the references and components but they're all intact. So I'm looking for any debugging program that can attached itself to a compiled program and give me an idea of what .DLL component or .OCX component is causing the error more information.
Thanks in advance,
Jorgen
UPDATE: I have read all your responses thanks for all the help. Besides from spy++ and Process Monitor I was considering using OllyDbg it has a view called "Executable Modules" that basically show which DLLs are being called. However when I run my program in it, it freezes and doesn't continue loading the GUI. Anyone familiar with OllyDbg and know why this is occurring?
Thanks
Jorgen
Assuming you have all the source code, you can compile your VB6 EXE and the DLLs and OCXs into native code including symbolic debug info so that the PDB files are created (tick the checkbox on the Project > Properties > Compile tab). Then you can either use WindDbg or Visual Studio .NET to trace the problem.
WinDbg (http://msdn.microsoft.com/en-us/windows/hardware/hh852365) Please see the following:
"A word for WinDbg" by Mike Taulty (http://mtaulty.com/communityserver/blogs/mike_taultys_blog/archive/2004/08/03/4656.aspx)
"Old school debugging - VB6 middleware applications" by Mark Long (http://blogs.msdn.com/b/marklon/archive/2006/01/28/518616.aspx)
or
Visual Studio 2008 C++ Express or Professional with your PDBs.
Both ways need to have the source code in exactly the same path on the debug machine as on the build machine. The easiest way then, is to build and debug on the same machine.
It's probably easier to add logging to the application.
It is possible to debug without using the VB6 IDE, but its not easy - I recommend logging.
Logging is good and fine but it can be fustrating experience throwing logging all over the place before you have an idea where to start.
spy ++ is the stuff I use when debugging old vb code along with PView will give me a rough idea where the code is failing. And then add logging to those areas.
And check Hans Passands comment. It might save you some greef.
You can download "Process Monitor" from sysinternals: www.sysinternals.com, set the filters to not appear useless information and investigate for unsuccessful results, quite painful work but with good chances.
What reasons to use localized version of Visual Studio 2010? What problems / benefits can you list while using localized versions? Are localized versions really useful?
I can only see problems and very few benefits. Any problems you are likely to experience you will will get them in language other then English, which means searching how to resolve problem in that language is limited on start. Although it may be not directly related but I've been managing servers in polish language for a long time and man I was so many times wishing the errors by polish system was in English. Finding resolution to problems in English is 50x easier then in my native tongue. If you even try to translate error message yourself you will have to be very careful because one translation isn't equal to another, especially when it comes to Microsoft programs (although not only). Many times error in my language given by SharePoint or Windows is so meaningless that you don't even know where to start looking for answers and if you see that error in English you just do "Oh.. it's about this.. simple stuff. Lets fix it".
Back to development.. Visual Studio in English gives you no problems to develop programs for any language you want. And most likely any addons will be in English so you will have mixed environment at some point having one Menu in English and other one in German. Also asking for help and following some tutorials/tips etc will be far easier in English so you won't have to translate stuff On-The-Fly yourself but will just follow the steps.
What is the most important or awaited feature in Visual Studio 2010??
The Historical Debugger. This records what happens during a run, and lets you step backwards and forwards through time in the debugger.
As far as the IDE goes, proper, well-thought-out multi-monitor support is a big one..
Support for parallel development.
It is running on top of WPF.
F# :)
The new text editor written in WPF is very interesting. There is also a new extensibility framework that will make writing add-on for VS much easier (in my opinion the most important new feature). The tools for SharePoint development are nice additions. There is a new debugger that records the debugging process and has greater support for parallel programming.
Usable SharePoint integration...bring it on!
The dynamic language runtime will lead to much more readable code when dealing with COM application and will be interesting to see where it takes staticaly typed languages.
Afair, they promised to include WiX 3.0. Although not perfect tool (built on top of ugly MSI plus some xml hell) but we don't have alternatives (at least from Microsoft), do we (tried their Setup projects)?
Architectural View(Designer) of the Application
This enables the new developers to understand the application flow more quickly.
Improvment of the TDD Good Channel 9 example. It way simpler now with an awesome intelli-sense.
I'm writing in C# the next generation of an old app originally written in Delphi. I often have to look in the old code and wondered if there's anyway to install Pascal syntax highlighting in the Visual Studio 2008 editor.
TIA.
I'm not an expert but you might want to look at Delphi Prism which seems to combine a Delphi compiler into Visual Studio. It might be overkill however.
http://blog.cumps.be/visual-studio-2008-and-php-coloring/ - maybe this could be adjusted from PHP for delphi/pascal
Planned project:
http://www.codeplex.com/Delphi4VisualStudio - this (one day) will support syntax highlighting (but it seems to be overkill too)
I know the guy working on Delphi4VisualStudio. The project doesn't seem to be active any more, but I know he had syntax highlighting working in the editor. You could always ask him for just that piece.
I could do it in about 1-2 day's work, but I'm busy trying to make ends meet (seriously). Let me know if you want me to do it.
Prior work (showing [almost] only the syntax highlighting):
Edit: Don't mark me down if this isn't allowed - just let me know. I'd seriously do it for free if I had any spare time at all, I just don't right now.
UnrealScript
INI Files
ANTLR grammars
StringTemplate templating language
Chapel