.Net Application Problems on XPe

[Mark Hampson]

Hi,

I am new to XPe, so please bear with me!

We are running XPe on CompactFlash that already has .Net 1.0
installed. I am having problems getting my .Net application to run and
get the error: Common Language Runtime Debugging Services: Application
has generated an exception that could not be handled. Please note that
I am sure that the application is compiled to run with 1.0, not 1.1.

I have seen in previos posts that .Net applications require WinLogin,
but I'm not sure if this is the problem or not? Can the MinLogin and
WinLogin be installed at the same time on the OS? If so, is there an
easy way to switch between the (2)? Is there a way to tell if WinLogin
is present?

Any other suggestions are greatly appreciated.

Thanks,
Mark

 

[KM]

Mark,

Don't know about you .Net issue.

You can't have Minlogon and Winlogon components at one image. However, you
may have Minlogon and all Winlogon dependecies.
One way to tell if you have Winlogon is whether you have multiuser
environment (do you see logon/welcome window when windows boots up?).
Minlogon supports only local system account. Do you have Explorer Shell in
your image? If you do, most likely Winlogon has been included.

Btw, have you tried your .Net app on XP Pro with .Net Framework 1.0
installed? If you have and it worked, you need to debug you XPe image. If
not, give it a try first.

KM

 

[Mark]

Thanks for the reply.

During my bootup I do not see options for multiple users, but I have been
told that WinLogin was included with my build of XPe. Can you tell me how
to check for the Explorer Shell? Again, sorry for the simple questions!

I did try our .Net application on XP Pro and it works just fine. Our
developers actually created a 'Hello World' app to make things even easier.
I did notice that I am unable to setup page files for Virtual Memory. It
allows me to setup a range, but it will always say that there is 0mb
allocated and it will give me errors upon bootup. Would this keep .Net from
running? Let me know if you might have any other ideas as to why I can't get
..Net running.

Thanks for all your help.

Mark

 

[Slobodan Brcin]

Hi,

There is an easy way to test if it is milogon or winlogon.

Got to windows\system32 folder.
Check winlogon.exe file size.

If it is ~15KB then obviously you are dealing with minlogon.
If it is >500KB then it is (normal) winlogon.

Since file is called winlogon.exe in both cases, then answer to if there can
be installed both minlogon and winlogon is negative.

You will need to use debugger or some filemonitor, regmonitor utility to see
what is missing in your build that is preventing your .Net app to work.


Regards,
Slobodan

 

[KM]

Mark,

Another way to check for Winlogon is to verify whether msgina.dll is under
your image \system32 directory.
For Explorer Shell I'd first check
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\"Shell"] registry value. If it is set to
"Explorer.exe" - you're running Explorer app as a shell on the device.

As Slobodan mentioned, to find out why your app is failing, you may want to
use monitoring tools - FileMon, RegMon (www.sysinternals.com), or latest
Dependency Walker (>2.0). However, Dependency Walker may be useless for .Net
app. You may be also running out of memory. Then either add aditional RAM to
your device or turn on paging file. You may debug your app remotely with VS.
Although, I used that with VS 6.0, VS.Net has most likely got this feature.

KM