DebugAsHighRes

  • Thread starter Thread starter Nathan Mellor
  • Start date Start date
N

Nathan Mellor

I've tried using the DebugAsHighRes that is reccommended to debug resolution
aware applications.

http://blogs.msdn.com/windowsmobile/archive/2004/04/03/107203.aspx

It doesn't work for me.

After debugging the macro and fixing a few strings, it does run if I start
it from a keyboard shortcut in an editor window.

It does start debugging, but it is not in HiRes mode. I can only get it to
hires mode if I manually copy the dll to the machine. Not helpful because
there is no "Attache to process" that I know of for

The project is part of a solution with other projects. I don't know if that
makes a difference or not.

The write time changes, indicating the res2exe worked, but the write time
changes again before debugging starts, indicating that visual studio felt
inclined to build it again just in case.

Any suggestions?

Nathan
 
Alex Feinman said:
This any help?
http://groups-beta.google.com/group...=DebugAsHighRes&rnum=2&hl=en#b383a820c0a11fe5
Click to expand...

No.

That's what I'm already doing. Does it work for everyone else? The executable that is copied for debug is most definitely not hires aware.

If I choose cancel on the deploy dialog, then copy the exe manually from obj\debug, it runs as hires. But it is not debugging in that case.

I just tried your experiment of resing the exe while the deploy dialog is waiting. When I choose deploy, it then copies the exe from somewhere else.

I've even tried the method of adding the prebuild step to the custom dll. Same problems.

Latest tidbit:
I had trouble seeing the output window when I've most needed to. I'm seeing this on Deploy:


------ Deploy started: Project: ProgramName, Configuration: Debug Pocket PC ------

Connected to Pocket PC Device (Pocket PC) running on ARMV4.
Copying files from 'C:\ ... ... \src\bin\Debug' to '\Program Files\ ProgramName'
Copying ProgramName.exe.

This shows it copying an executable from bin\Debug, not obj\Debug, while the MSDN blog suggests that obj\Debug is the one you need to modify.

I find myself confused.

Nathan
 
Nathan,

I am actually using the modified macro as described in my post and the hi-res aware binary does get copied to the device and debugged. Have you tried my edition of the macro?

--
Alex Feinman
---
Visit http://www.opennetcf.org

Alex Feinman said:
This any help?
http://groups-beta.google.com/group...=DebugAsHighRes&rnum=2&hl=en#b383a820c0a11fe5
Click to expand...

No.

That's what I'm already doing. Does it work for everyone else? The executable that is copied for debug is most definitely not hires aware.

If I choose cancel on the deploy dialog, then copy the exe manually from obj\debug, it runs as hires. But it is not debugging in that case.

I just tried your experiment of resing the exe while the deploy dialog is waiting. When I choose deploy, it then copies the exe from somewhere else.

I've even tried the method of adding the prebuild step to the custom dll. Same problems.

Latest tidbit:
I had trouble seeing the output window when I've most needed to. I'm seeing this on Deploy:


------ Deploy started: Project: ProgramName, Configuration: Debug Pocket PC ------

Connected to Pocket PC Device (Pocket PC) running on ARMV4.
Copying files from 'C:\ ... ... \src\bin\Debug' to '\Program Files\ ProgramName'
Copying ProgramName.exe.

This shows it copying an executable from bin\Debug, not obj\Debug, while the MSDN blog suggests that obj\Debug is the one you need to modify.

I find myself confused.

Nathan
 
I tried your version just now as well. Same result.

However, if I change things to bin\debug, I can get things to work just fine.

When you use Deploy on a Smart Device Project, does it copy files form obj\debug or from bin\debug? Mine definitely copies from bin\debug. I don't know if my project was setup differently.

Nathan
Nathan,

I am actually using the modified macro as described in my post and the hi-res aware binary does get copied to the device and debugged. Have you tried my edition of the macro?

--
Alex Feinman
---
Visit http://www.opennetcf.org

Alex Feinman said:
This any help?
http://groups-beta.google.com/group...=DebugAsHighRes&rnum=2&hl=en#b383a820c0a11fe5
Click to expand...

No.

That's what I'm already doing. Does it work for everyone else? The executable that is copied for debug is most definitely not hires aware.

If I choose cancel on the deploy dialog, then copy the exe manually from obj\debug, it runs as hires. But it is not debugging in that case.

I just tried your experiment of resing the exe while the deploy dialog is waiting. When I choose deploy, it then copies the exe from somewhere else.

I've even tried the method of adding the prebuild step to the custom dll. Same problems.

Latest tidbit:
I had trouble seeing the output window when I've most needed to. I'm seeing this on Deploy:


------ Deploy started: Project: ProgramName, Configuration: Debug Pocket PC ------

Connected to Pocket PC Device (Pocket PC) running on ARMV4.
Copying files from 'C:\ ... ... \src\bin\Debug' to '\Program Files\ ProgramName'
Copying ProgramName.exe.

This shows it copying an executable from bin\Debug, not obj\Debug, while the MSDN blog suggests that obj\Debug is the one you need to modify.

I find myself confused.

Nathan
 
Back
Top