Cannot fifure out how to fix this exception.

[=?Utf-8?B?RGF2ZQ==?=]

I am unable to execute the following statement in my current project. The
class PosExplorer is in a dll file (created by Microsoft).

PosExplorer explorer = new PosExplorer()

but now I get this dreaded exception below. What I cannot understand, is
that, if I create another small project with a single form and execute the
line above, then it works. But it does not work in my current project.
The innerexception. Message is : "Attempt to access the method failed".

Here is the exception.

System.TypeInit ializationExcep tion was unhandled
Message="The type initializer for
'Microsoft.Poin tOfService.Mana gement.Explorer ' threw an exception."
Source="Microso ft.PointOfServi ce"
TypeName="Micro soft.PointOfSer vice.Management .Explorer"
StackTrace:
at Microsoft.Point OfService.Manag ement.Explorer. CreateExplorer( )
at Microsoft.Point OfService.PosEx plorer.LoadExpl orer()
at Microsoft.Point OfService.PosEx plorer.Initiali ze()
at Microsoft.Point OfService.PosEx plorer..ctor()
at Retail.frmPrint erSetUp.frmPrin terSetUp_Load(O bject sender,
EventArgs e) in C:\Documents and Settings\HP_Own er\My Documents\Visua l Studio
2005\Projects\R etail\Retail\fr mPrinterSetUp.c s:line 21
at System.Windows. Forms.Form.OnLo ad(EventArgs e)
at System.Windows. Forms.Form.OnCr eateControl()
at System.Windows. Forms.Control.C reateControl(Bo olean fIgnoreVisible)
at System.Windows. Forms.Control.C reateControl()
at System.Windows. Forms.Control.W mShowWindow(Mes sage& m)
at System.Windows. Forms.Control.W ndProc(Message& m)
at System.Windows. Forms.Scrollabl eControl.WndPro c(Message& m)
at System.Windows. Forms.Container Control.WndProc (Message& m)
at System.Windows. Forms.Form.WmSh owWindow(Messag e& m)
at System.Windows. Forms.Form.WndP roc(Message& m)
at
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(M essage& m)
at System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(Mes sage& m)
at System.Windows. Forms.NativeWin dow.DebuggableC allback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows. Forms.SafeNativ eMethods.ShowWi ndow(HandleRef hWnd,
Int32 nCmdShow)
at System.Windows. Forms.Control.S etVisibleCore(B oolean value)
at System.Windows. Forms.Form.SetV isibleCore(Bool ean value)
at System.Windows. Forms.Control.s et_Visible(Bool ean value)
at
System.Windows. Forms.Applicati on.ThreadContex t.RunMessageLoo pInner(Int32
reason, ApplicationCont ext context)
at
System.Windows. Forms.Applicati on.ThreadContex t.RunMessageLoo p(Int32 reason,
ApplicationCont ext context)
at System.Windows. Forms.Form.Show Dialog(IWin32Wi ndow owner)
at System.Windows. Forms.Form.Show Dialog()
at Retail.frmMain. frmMain_Load(Ob ject sender, EventArgs e) in
C:\Documents and Settings\HP_Own er\My Documents\Visua l Studio
2005\Projects\R etail\Retail\fr mMain.cs:line 24
at System.Windows. Forms.Form.OnLo ad(EventArgs e)
at System.Windows. Forms.Form.OnCr eateControl()
at System.Windows. Forms.Control.C reateControl(Bo olean fIgnoreVisible)
at System.Windows. Forms.Control.C reateControl()
at System.Windows. Forms.Control.W mShowWindow(Mes sage& m)
at System.Windows. Forms.Control.W ndProc(Message& m)
at System.Windows. Forms.Scrollabl eControl.WndPro c(Message& m)
at System.Windows. Forms.Container Control.WndProc (Message& m)
at System.Windows. Forms.Form.WmSh owWindow(Messag e& m)
at System.Windows. Forms.Form.WndP roc(Message& m)
at
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(M essage& m)
at System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(Mes sage& m)
at System.Windows. Forms.NativeWin dow.DebuggableC allback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows. Forms.UnsafeNat iveMethods.Send Message(HandleR ef
hWnd, Int32 msg, Int32 wParam, Int32 lParam)
at System.Windows. Forms.Form.SetV isibleCore(Bool ean value)
at System.Windows. Forms.Control.s et_Visible(Bool ean value)
at
System.Windows. Forms.Applicati on.ThreadContex t.RunMessageLoo pInner(Int32
reason, ApplicationCont ext context)
at
System.Windows. Forms.Applicati on.ThreadContex t.RunMessageLoo p(Int32 reason,
ApplicationCont ext context)
at System.Windows. Forms.Applicati on.Run(Form mainForm)
at Retail.Program. Main() in C:\Documents and Settings\HP_Own er\My
Documents\Visua l Studio 2005\Projects\R etail\Retail\Pr ogram.cs:line 20
at System.AppDomai n.nExecuteAssem bly(Assembly assembly, String[] args)
at System.Runtime. Hosting.Manifes tRunner.Run(Boo lean checkAptModel)
at System.Runtime. Hosting.Manifes tRunner.Execute AsAssembly()
at
System.Runtime. Hosting.Applica tionActivator.C reateInstance(A ctivationContex t
activationConte xt, String[] activationCusto mData)
at
System.Runtime. Hosting.Applica tionActivator.C reateInstance(A ctivationContex t
activationConte xt)
at
Microsoft.Visua lStudio.Hosting Process.HostPro c.RunUsersAssem blyDebugInZone( )
at System.Threadin g.ThreadHelper. ThreadStart_Con text(Object state)
at System.Threadin g.ExecutionCont ext.Run(Executi onContext
executionContex t, ContextCallback callback, Object state)
at System.Threadin g.ThreadHelper. ThreadStart()

--
L. A. Jones

[Patrick Steele]

In article <D2************ *************** *******@microso ft.com>,
Da**@discussion s.microsoft.com says...

>
I am unable to execute the following statement in my current project. The
class PosExplorer is in a dll file (created by Microsoft).

PosExplorer explorer = new PosExplorer()

but now I get this dreaded exception below. What I cannot understand, is
that, if I create another small project with a single form and execute the
line above, then it works. But it does not work in my current project.
The innerexception. Message is : "Attempt to access the method failed".

Here is the exception.

System.TypeInit ializationExcep tion was unhandled
Message="The type initializer for
'Microsoft.Poin tOfService.Mana gement.Explorer ' threw an exception."
Source="Microso ft.PointOfServi ce"

Whenever you see a TypeInitializat ionException, you really need to look
at it's InnerException to see why the type couldn't be initialized.

--
Patrick Steele
http://weblogs.asp.net/psteele

[sherifffruitfly]

On Mar 5, 7:05 pm, Patrick Steele <patr...@mvps.o rgwrote:

In article <D23F6DE9-A23E-4171-9ED9-6A46528B8...@mi crosoft.com>,
D...@discussion s.microsoft.com says...

Whenever you see a TypeInitializat ionException, you really need to look
at it's InnerException to see why the type couldn't be initialized.

If you don't "just know" that a given exception *has* an
InnerException, do you basically just have to put an if
(ex.InnerExcept ion != null) clause in all of your exception handlers?

[Patrick Steele]

In article <11************ **********@8g20 00cwh.googlegro ups.com>,
sh************* @gmail.com says...

On Mar 5, 7:05 pm, Patrick Steele <patr...@mvps.o rgwrote:

In article <D23F6DE9-A23E-4171-9ED9-6A46528B8...@mi crosoft.com>,
D...@discussion s.microsoft.com says...

Whenever you see a TypeInitializat ionException, you really need to look
at it's InnerException to see why the type couldn't be initialized.

If you don't "just know" that a given exception *has* an
InnerException, do you basically just have to put an if
(ex.InnerExcept ion != null) clause in all of your exception handlers?

I'm not sure what you're asking. The InnerException property helps you
determine why the TypeLoadInitial izationExceptio n occurred.

The base Exception class contains an InnerException property so any
exception in .NET has the potential to have an InnerException.

--
Patrick Steele
http://weblogs.asp.net/psteele

[sherifffruitfly]

On Mar 5, 7:32 pm, Patrick Steele <patr...@mvps.o rgwrote:

In article <1173151420.085 767.309...@8g20 00cwh.googlegro ups.com>,
sherifffruit... @gmail.com says...

On Mar 5, 7:05 pm, Patrick Steele <patr...@mvps.o rgwrote:

In article <D23F6DE9-A23E-4171-9ED9-6A46528B8...@mi crosoft.com>,
D...@discussion s.microsoft.com says...

Whenever you see a TypeInitializat ionException, you really need to look
at it's InnerException to see why the type couldn't be initialized.

If you don't "just know" that a given exception *has* an
InnerException, do you basically just have to put an if
(ex.InnerExcept ion != null) clause in all of your exception handlers?

I'm not sure what you're asking. The InnerException property helps you
determine why the TypeLoadInitial izationExceptio n occurred.

The base Exception class contains an InnerException property so any
exception in .NET has the potential to have an InnerException.

Ah - gotcha. I had the cockamamie idea that there were some types of
exceptions that were guaranteed to have inners, and other types of
exceptions there were guaranteed NOT to have inners. If I understand
you correctly, having an inner exception (or not) isn't decided at the
type level, rather it's decided at the instance level.

So basically, if you care about them in the first place, you would
always have an inner-exception-checker in your exception handler - for
any exception you don't know the instantiation/property-setting
details of ahead of time.

[sherifffruitfly]

On Mar 5, 7:32 pm, Patrick Steele <patr...@mvps.o rgwrote:

In article <1173151420.085 767.309...@8g20 00cwh.googlegro ups.com>,
sherifffruit... @gmail.com says...

On Mar 5, 7:05 pm, Patrick Steele <patr...@mvps.o rgwrote:

In article <D23F6DE9-A23E-4171-9ED9-6A46528B8...@mi crosoft.com>,
D...@discussion s.microsoft.com says...

Whenever you see a TypeInitializat ionException, you really need to look
at it's InnerException to see why the type couldn't be initialized.

If you don't "just know" that a given exception *has* an
InnerException, do you basically just have to put an if
(ex.InnerExcept ion != null) clause in all of your exception handlers?

I'm not sure what you're asking. The InnerException property helps you
determine why the TypeLoadInitial izationExceptio n occurred.

The base Exception class contains an InnerException property so any
exception in .NET has the potential to have an InnerException.

Ah - gotcha. I had the cockamamie idea that there were some types of
exceptions that were guaranteed to have inners, and other types of
exceptions there were guaranteed NOT to have inners. If I understand
you correctly, having an inner exception (or not) isn't decided at the
type level, rather it's decided at the instance level.

So basically, if you care about them in the first place, you would
always have an inner-exception-checker in your exception handler - for
any exception you don't know the instantiation/property-setting
details of ahead of time.