.NET application Shell Componentization problem.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Dear all,
I try to make my application as a shell component in my
configuration instead of Explorer Shell. When i include VC++ application, it
is successfully working. But .NET Framework 1.1 and 1.0 applications are not
working. That means, it does not say any error messages and the application
is not displayed. How can I recover this problem? Kindly hep me.

Thanks & Regards,
Veerasivakumar. V
--
V.Veerasivakumar
InLott Technologies Pvt Ltd,
Chennai,
India.

E-Mail: (e-mail address removed)
 
Veerasivakumar,

Is you custom shell image Minlogon or Winlogon based?
..Net stuff will require WinLogon.
 
Dear KM,
Thanks for ur reply. My configuration is using Winlogon Macro
component. But the .net application is not worked. Any suggestions for me?
kindly advice me.


--
V.Veerasivakumar
InLott Technologies Pvt Ltd,
Chennai,
India.

E-Mail: (e-mail address removed)
 
Veerasivakumar,

You'd probably need to debug the application.

Start with simple steps like:
- Make CMD as the shell. Try to launch your application from there. Then you will know whether you got all application
dependencies and settings in your image.

- Add simple message boxes (or debug messages if serial debug output is enabled ion your image and you can watch it on another
computer). Then you will know whether the app is even getting started properly or not.

- Make a simple Win32 app as your shell. From the app launch your .Net app through CreateProcess. Make sure to properly set new
process working directory.

- Create a new image with Explorer shell and see if you can work with your app there.


Also, please check FBALog.txt and SetupApi.log files to see if any error happened druing .Net installation.
 
Dear KM,
I did it like ur suggestions. But it is facing the error "JIT
Debugger is not Available.". How can i resolve this problem? Thanks in
advance.


--
V.Veerasivakumar
InLott Technologies Pvt Ltd,
Chennai,
India.

E-Mail: (e-mail address removed)
 
Veerasivakumar,

In fact I suggested a few things. I guess you only tried debugging the app?
Since we are talking about managed code debugging, please read "Studio 2003 debugging C# on Windows XP Embedded Target" recent
thread in this NG.
 
Back
Top