ASP.NET, SQL Server, WPF, C#, VB.NET

I've read this post and am having the same problems:  
  
http://groups.google.com/group/microsoft.public.windowsce.testtools/browse_frm/thread/a4d1abfaed7774ce/5bd0c40fb643a950?lnk=st&q=appverifce.exe+hang+group%3Amicrosoft.public.windowsce.testtools&rnum=1&hl=en#5bd0c40fb643a950  
  
I am having problems getting the appVerifier to run on my WM 5.0  
  
device.  
  
I've tried creating a link file on the device like so:  
  
62#appverif.exe -m "\Program Files\MyApp\My.exe" -s shim_heap.dll  
  
....but after running it via FileManager it says it cannot load the shim  
  
engine.  The shim engine DLL in the root directory on the device  
  
matches the one from the "C:\Program Files\Windows CE Platform  
  
Builder\5.00\cepb\wcetk\DDTK\ARMV4I" directory on my machine, so I  
  
think it's correct.  
  
I've run appverifce.exe directly from my PC and upon connecting to  
  
the device, it just hangs and never responds.  
  
I've tried running CETK from the PC, which connects successfully to  
  
the device using ActiveSync transport/start up server, but then when I  
  
run appVerifierCE from within CETK, it does the same-hangs and never  
  
responds after attempting to connect.  
  
I've read this article:  
  
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnce50/html/appverifier_wince.asp  
  
I am currently at a loss as to what to try next.  Does anyone have any  
  
detailed resources you can point me to that properly explain how to get  
  
this running???  
  
Thanks,  
  
Rob

rf- [1 Jun 2006 10:22:02 -0700]:  
  
There is a ce5 appver and there is a later,  
  
wm5 appver.  Both need platform manager  
  
installed.  I suspect PM is not your problem,  
  
but maybe you do have the ce5 appver, which  
  
won't work on wm5.  
  
--  
  
40th Floor - Software  @  http://40th.com/  
  
iPlay : the ultimate audio player for mobiles  
  
parametric eq, xfeed, reverb; all on a mobile

The Application Verifier Tool for Windows Mobile« 5.0 can be downloaded  
  
here:  
  
http://www.microsoft.com/downloads/details.aspx?FamilyId=D275348A-D937-4D88-AE25-28702C78748D&displaylang=en  
  
Make sure you sign the bits with a privileged certificate, and reset your  
  
device to clear out any settings and bits from the incorrect version.  
  
--  
  
Marty Larson [MS]  
  
--  
  
This posting is provided "AS IS" with no warranties, and confers no rights.  
  
Use of included script samples are subject to the terms specified at  
  
http://www.microsoft.com/info/cpyright.htm  
  
<hel@40th.com> wrote in message  
  
news:OEKNE8ghGHA.4896@TK2MSFTNGP05.phx.gbl...

I have downloaded that link and it is installed already, but I am not  
  
sure what version of those files are on my device now.  
  
When you say "reset the device", do you mean soft or hard reset?  
  
I've disabled all security using Device Security Manager, so do I still  
  
need things to be signed?  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:  
  
4D88-AE25-28702C78748D&displaylang=3Den  
  
s=2E

OK, I hard reset the device and ran the version of AppVerifier located  
  
here:  
  
C:\Program Files\Application Verifier for Mobile  
  
5=2E0\Desktop\AppVerifCE.exe  
  
It still locked up, pegging the CPU.  Thoughts?  
  
Thanks,  
  
Rob  
  
robf@mageware.com wrote:  
  
ed  
  
7-4D88-AE25-28702C78748D&displaylang=3Den  
  
ur  
  
hts.

I got further than I was before.  Now AppVerifier is succesfully  
  
connecting to the device and allowing me to browse/add my EXE to the  
  
list on the left.  However, when I run the app, I get:  
  
Unable to create process 'myexe.exe' : Error 2  
  
What does this mean?  
  
Thanks,  
  
Rob  
  
robf@mageware.com wrote:  
  
aded  
  
937-4D88-AE25-28702C78748D&displaylang=3Den  
  
your  
  
ights.

OK, I hard reset the device and made sure to launch from here:  
  
C:\Program Files\Application Verifier for Mobile 5.0\Desktop  
  
It didn't work at first and exhibited the same lock up behavior, but  
  
once I removed the security using Device Security Manager, and tried a  
  
few more times--eventually it worked.  
  
My applications are .NET applications.  The Log Viewer wants .MAP files  
  
to resolve the call stacks--but .NET doesn't generate these.  How can I  
  
make sense of the unresolved stack information contained within the  
  
generated log files?  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:  
  
4D88-AE25-28702C78748D&displaylang=3Den  
  
s=2E

App Verifier only works on native code (this is true for the desktop's  
  
version as well). So, if your code is purely managed, this means that you'll  
  
only end up testing the framework, not your code.  
  
Sorry about that.  
  
--  
  
Marty Larson [MS]  
  
--  
  
This posting is provided "AS IS" with no warranties, and confers no rights.  
  
Use of included script samples are subject to the terms specified at  
  
http://www.microsoft.com/info/cpyright.htm  
  
<robf@mageware.com> wrote in message  
  
news:1149286500.041670.21550@g10g2000cwb.googlegroups.com...  
  
OK, I hard reset the device and made sure to launch from here:  
  
C:\Program Files\Application Verifier for Mobile 5.0\Desktop  
  
It didn't work at first and exhibited the same lock up behavior, but  
  
once I removed the security using Device Security Manager, and tried a  
  
few more times--eventually it worked.  
  
My applications are .NET applications.  The Log Viewer wants .MAP files  
  
to resolve the call stacks--but .NET doesn't generate these.  How can I  
  
make sense of the unresolved stack information contained within the  
  
generated log files?  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:

Marty,  
  
Is there any way to get any call stack information for .NET code?  This  
  
is kind of a problem for certification/Windows Logo compliance since we  
  
have no way to diagnose the issues found by AppVerifier and  
  
certification requires that we pass AppVerifier.  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:  
  
'll  
  
s=2E  
  
ed  
  
7-4D88-AE25-28702C78748D&displaylang=3Den  
  
ur

No, app verifier is for native code only. If you have some native code in  
  
your process, you should test it. But if your app is purely managed, you  
  
won't get any relevant information.  
  
--  
  
Marty Larson [MS]  
  
--  
  
This posting is provided "AS IS" with no warranties, and confers no rights.  
  
Use of included script samples are subject to the terms specified at  
  
http://www.microsoft.com/info/cpyright.htm  
  
<robf@mageware.com> wrote in message  
  
news:1149515310.106724.156240@c74g2000cwc.googlegroups.com...  
  
Marty,  
  
Is there any way to get any call stack information for .NET code?  This  
  
is kind of a problem for certification/Windows Logo compliance since we  
  
have no way to diagnose the issues found by AppVerifier and  
  
certification requires that we pass AppVerifier.  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:

Marty,  
  
We do make calls to Windows APIs through PInvoke using DllImport, i.e.,  
  
things like Point to Point Message Queues, etc.  And we also have  
  
custom drawing/painting code in .NET.  However, without stack name  
  
resolution in an AppVerifier log file, how am I to diagnose any  
  
information contained therein?  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:  
  
s=2E  
  
aded  
  
937-4D88-AE25-28702C78748D&displaylang=3Den

In Visual Studio, the setting can be found at:  
  
Project --> Properties --> Configuration Properties --> Linker --> Debugging  
  
--  
  
Marty Larson [MS]  
  
--  
  
This posting is provided "AS IS" with no warranties, and confers no rights.  
  
Use of included script samples are subject to the terms specified at  
  
http://www.microsoft.com/info/cpyright.htm  
  
<robf@mageware.com> wrote in message  
  
news:1149688014.664844.211920@i39g2000cwa.googlegroups.com...  
  
Marty,  
  
We do make calls to Windows APIs through PInvoke using DllImport, i.e.,  
  
things like Point to Point Message Queues, etc.  And we also have  
  
custom drawing/painting code in .NET.  However, without stack name  
  
resolution in an AppVerifier log file, how am I to diagnose any  
  
information contained therein?  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:

Sorry, I may not have been clear.  That setting only exists for VC++  
  
projects.  We're doing this in C# .NET v2.0.  
  
What options exist for diagnosting an AppVerifier log file that was  
  
generated from testing an EXE written in C# .NET?  
  
Thanks,  
  
Rob  
  
Marty Larson [MS] wrote:  
  
ing  
  
s=2E  
  
in  
  
es  
  
I  
  
-D937-4D88-AE25-28702C78748D&displaylang=3Den  
  
n=2E