Upgrading to .NET pitfalls and Remote Debugging

Upgrading to .NET compiler changes several things including building
with the MFC 7.0 library

Let me preface all this by saying it is VERY easy to set up remote
debugging following Andy's article.

Problem: We have a minlogin custom shell running under XPEmbedded
relatively happily for well over a year. We upgraded to .NET and when
I replaced my old binaries (built with VStudio) with new binaries
(build with .NET) I started getting MFC assertions ( map_pp.cpp) .

When I rebuilt the binaries with the old compiler it worked fine.
Hummmm

Of course I started with Depends.exe making sure I had ALL the
necessary files (which I did). Then I validated I could reproduce
this on other systems (which I did). Then I tried a ton of other
things: page file settings, winlogin vs minlogin, installing the .NET
framework, you name it!

Finally I setup remote debugging. The assertion thrown was on loading
the DAO engine. I reviewed all the DAO components in TD and noticed
there was on I did not have included in my probject.

REMEMBER, I HAVE NEVER HAD THIS COMPONENT INCLUDED. I added it and
the program loaded and ran fine.

The Lesson: Programs built with the .NET compiler may be dependent on
TOTALLY DIFFERENT XP Embedded components than those build with old
Visual Studio. In this case a DAO component was required by MFC 7.0
that was NOT required by MFC 6.0.

AND DEPENDS.EXE and TD Dependency Check will not help you with this!

Conclusion: Upgrading to the .NET compiler is not a half days task and
have Andy's remote debugging article on hand.