I have a windows mobile project in VS2005. Initially I could not get any breakpoints to enable on windows mobile 6 device but they worked on PocketPC2003 Emulator. It's a new computer at work and after a while I realised I had no installed any SDK's beyond 2003. Having now installed SDK's for windows mobile 5.0 6.0 and 6.5.3 I now have SOME of my breakpoints active.
My solution consists of a main application under which there are a few screens and associated code. There are also a series of other classes each of which compiles to a separate DLL. It seems the issue I have is that any breakpoints in these separate classes
work perfectly now. However any breakpoints in the main application class give an error "The breakpoint will not currently be hit. No symbols have been loaded for this document." I've tried a number of things including deleting the bin\debug and obj folders to clear old debug information. The PBD files appear to be created ok for the exe files as well as the class DLL's but only the Dll's work correctly in debug.
Any ideas guys. I really have to get this working as it needs to work on a device not just an emulator. I have an external DLL I need to use as part of testing that is very specific to a brand and model range of hardware. I wont explain why here, just suffice it to say I really need to get this sorted.
I'm still learning VS2005 So please be specific with suggestions as I might not yet know where to locate certain functionality.
I should probably add it works fine in windows mobile 5.0 emulator but I don't have a windows mobile 5 device to test with
Thanks in anticipation.
Well I don't know exactly what I did but it is now working. I read an article on here about enabling the module tab in the debug menu and after doing that it worked however I had done a couple of other things prior to doing that and hadn't tested it so not sure which it was that fixed it.
Related
Currently I am working in a Xamarin native project which is well developed and in between when we introduced the image view with auto scroll with dot indicators the problem arrived.
The actual problem is when we release or debug from one system only the app is working fine or else if we do that from another system the app is unexpectedly stopped, if the testing phone is connected to the system and if that is in debug state it is working when we remove it from debug it is not working correctly.
I don't know the reason why it is happening.
Initially I thought that there is a problem with the SDK versions JDK Versions and all, I checked by almost equalizing the SDK, JDK and Xamarin versions but unable to detect the problem and correct it for reference of what we added into the project please refer the following links.
How to implement ViewPagers with Dot Sliders in Xamarin.Android?
How to Set auto sliders in pageviewers in xamarin.android
I am unable to detect the actual problem causing the problem can any one please let me know the solution of the problem.
When You get this type of issue then follow the steps below
1. Try to make a exact copy of SDk from the working system and copy in some other drive and map the reference in VS.
2.If that does not work then also, make sure all the versions in systems are equal.
If then also it does not work it is an internal issue so uninstall the complete VS and make a fresh installation this should work at any cost.
I'm not sure if this is the right place to ask, seeing as I don't currently have any code to share, but perhaps someone has an insight.
I have a very old Flash MX projection (.exe file) that was written and compiled in flash MX 2004. It's a simple interactive app - a test where a user picks an answer to a question and pushes ENTER to move to the next question.
The projection works fine on WinXP SP3 but doesn't work in win7, failing with a "class not registered" error.
It does work after I install flash player activex (I tried installing the latest, and also legacy version 6 r71), but then it doesn't register any keyboard commands and crashes a short while after a key is pressed.
Any idea what can be causing this?
So far I've tried fiddling with IE security settings, disabling DWM and windows themes, compatibility settings, etc., with no luck.
Also, despite the fact that the compiled projection is supposed to have all necessary components to run inside, it doesn't run if flash.ocx isn't registered. Isn't that weird?
Any help will be appreciated. I know this is old stuff and no one promises compatibility etc. And I don't even have the code as of now (not sure I can find it; assume I can't) - but this app is somewhat important to my company and this really seems like a "small" issue - if I could just find it...
Update - it kinda works if install the latest flash player and run it in compatibility mode - but it hangs after about a minute, regardless of what i do.
if i run it without compatibility mode, it doesn't run with a "library not registered" error.
You might want to repackage it.
Extract SWF from projector executable, for example, using this tool.
Get the newest standalone Flash Player and check if your .swf-file works with it.
Now export new projector file.
If this doesn't work for you, the only other way to do this is to recompile your .swf from source.
I agree with Ale's solution.
Have you tried Window's compatibility options to run the .exe as it would in an older compatibility mode ? This may work.
I'm working on an application developed for Windows XP SP3, using VB6. I'm currently in the process of getting it to work on Windows 7, but am encountering a problem with one of our custom OCX files.
When attempting to load a form that contains an instance of the control contained in the problem OCX, the following error is produced:
Failed to load control 'x' from y.ocx. Your version of y.ocx may be outdated. Make sure you are using the version of the control that was provided with your application.
I've checked the version numbers and they're all correct and referencing the proper version. The OCX registers fine, and all the expected registry entries are present.
Inspection with DependencyWalker shows no missing dependencies.
The software works fine under XP, and this is (seemingly) the only issue when running on Windows 7.
Interestingly, if I run through the VB6 IDE using a VB6 group (with the offending OCX part of the group, and the application the startup project), I don't have the issue. Running the application on it's own through the IDE still presents the error.
Any ideas on what could be missing which would cause the application to throw this error?
Error occurs on both Windows 7 Professional and Home Professional, both 32 bit.
This is almost certainly an interface compatibility problem. COM interfaces are versioned entirely separately from your Major/Minor/Revision numbers, which are little more than comments except as used by Installer.
Somewhere along the line you broke binary compatibility, and you are trying to deploy a library with a newer interface than your application was compiled against.
These version numbers are found in keys such as:
HKEY_CLASSES_ROOT\CLSID\{class Id GUID}\VERSION
Your program needs to have its old reference to the OCX removed, a new one set, and then it must be recompiled. This also means deleting any instances of the control and adding them back one by one.
I doubt this is a Windows 7 issue.
I would suspect this is a UAC problem. Try turning UAC off to see if that solves the immediate issue. If it does then you have to regsiter everything using 'run as administrator' and/or create a manifest for you application.
Sounds like on of the controls included in your OCX is having issues loading, not a general registration error. Look at the constructors for x control, and see if they are doing anything that disagrees with UAC or such. One way you can debug this is put some kind of a break before the control is initialized, and debug the application from Visual Studio (remember to create the PDB's in VB6), and then carry on from the break to see why the control isn't initializing.
I'm adding some functionality to an old admin tool written in VB6. The tool uses a c++ activeX object. I haven't worked on the tool since I upgraded to windows 7 and now the active X object fails to load with the 429 "ActiveX component can't create object" error. I'm not knowledgeable about VB6 but I have registered the activex dll and type library and I can remove and add the object from the project via the project->references window (the program fails to compile when the reference is removed as expected). The VB6 ide is running in administrator mode and I get the same error if I run the exe directly as an administrator.
Has anyone else experienced a similar problem and found a way to sort it out?
Thanks,
Patrick
PS : I have also tried putting the dll in question in the working directory of the exe
EDIT: I've had no luck trying to sort this out and ended up remoting into a windows 2003 server to test the changes.
You might try using Mark Russinovich's regMon and FileMon to see exactly what files or regkeys are being requested during the load of that dll. That can often tell you if you've got a missing dependency.
Also the DEPENDS.EXE that comes with VS6 is sometimes good for that (though it doesn't necessarily get ALL the dependencies of a dll or exe).
COM is going to use the registry to map from the class name to the physical DLL file that has to be loaded.
Check the registry keys pertaining to your COM object... first under HKEY_CLASSES_ROOT, then the class name, which gets you the CLSID, then the HKEY_CLASSES_ROOT/CLSID section for the GUID of the object, and then see where the physical library lives.
A 429 could mean all sorts of different things. Many times, it means that there's a dependency missing, and the easiest way to figure out what dependency is missing is to use procmon to see what files/registry settings the app is trying to access and hopefully, catch where you get ACCESS_DENIED or FILE_NOT_FOUND or what have you.
The problem might also be with your browser. A couple weeks ago I upgraded my IE, since then I've had to make changes by opening IE, click tools, click custom, scroll to the activeX controls and enable, and/or click prompt. The same was needed for scripting and for me to use XMLHttprequest. Now everything is back to working, however the ActiveX warning alert sometimes takes over 2 minutes to pop-up, then when clicked everything works fine.
Do you have UAC enabled on that machine? Have you tried disabling it? I have seen some cases where it let ActiveX controls being registered but didn't let applications using them ran.
I'm sorry if I'm asking the wrong thing in stackoverflow, but I've come to my wits end dealing with Blackberry. Documentation, site organization, general levels of support have all come together to the point that I haven't been able to do a whole lot of actual work in this environment.
I currently have the Eclipse environment downloaded from the blackberry developer's area website. I can run the simulator and everything else without issue. What I'm trying to do now is to move from debugging on the simulator to debugging on the device itself. This is an important step for me, but I haven't found a satisfactory way to do it...
What I've found are some posts saying that I should package an ALX (of which I'm still not sure on how to do), and using the BDM to install it. This, however, means I won't be able to use the debugger...
If someone could direct me to a resource that will give me step by step instructions from coding to release of blackberry development, this would be awfully helpful.
Thanks so much!
Yes, please test your code on a device. Basic stuff works the same between both, but especially when you get into networking, media, etc. the devices are different.
You can debug on your device through Eclipse. I can't provide you with an end-to-end guide on SO, but here's the quick debug guide.
Build (sign if necessary) and load your app onto the device. You can do this with the desktop manager, or with the command-line javaloader tool that comes with the JDE (look in the bin directory), or even OTA (over the air)
After loading, make sure the Desktop Manager is NOT running (it'll interfere with on-device debugging)
From Eclipse, create a new debug configuration, in the Debug Configurations dialog click on BlackBerry Device, and then click on the new configuration icon. Default settings should be fine.
Make sure your device is plugged into your USB port and start your new debug configuration. You'll probably get a lot of prompts about things missing (because actual devices don't have debug info for any built-in stuff, generally) but click through those and you should be fine to debug.
This is something we struggled with a lot at my old company. I don't think it's possible to do with Eclipse, you have to use the BB JDE, creating the necessary project files against the same code base. I could be wrong on that one as we weren't using the RIM Eclipse plugin, just building it all with Ant.
Personally I never managed to get passed "debugger attaching..." on the device, although I believe a colleague got it to connect but found it too slow to be usable (if you think how slow the emulator can be sometimes...). I know our ant build file had a target for building a version specifically for the JDE profiler, although that was only against the emulator.
In the end we resorted to using our own function debugging code that manually logged entries, exits, parameters and run times, sending the result to a special server.
Sorry if that doesn't help much, but that was our experience.
Never needed to debug on the device itself, I've always found that the apps i've written work on the device, same as on the handset.
As for generating an ALX, in eclipse right click on the project inside the Package Explorer and select "Generate ALX File".