[RESOLVED] EXE blowing up on customer server

Odd - my app runs in the IDE - and the .EXE runs on my laptop. The .exe runs on my laptop connected to their database over VPN.

But that same .exe blows up with this when I run it on their server

Code:

---

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details.  The error is: Could not load file or assembly 'Microsoft.VisualBasic.PowerPacks.Vs, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualBasic.PowerPacks.Vs, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualBasic.PowerPacks.Vs, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
  at CMC.AddCase.InitializeComponent()
  at CMC.AddCase..ctor()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

  --- End of inner exception stack trace ---
  at CMC.My.MyProject.MyForms.Create__Instance__[T](T Instance)
  at CMC.My.MyProject.MyForms.get_AddCase()
  at CMC.CMCConsole.vendorLoad()
  at CMC.CMCConsole.CMCConsole_Load(Object sender, EventArgs e)
  at System.EventHandler.Invoke(Object sender, EventArgs e)
  at System.Windows.Forms.Form.OnLoad(EventArgs e)
  at System.Windows.Forms.Form.OnCreateControl()
  at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
  at System.Windows.Forms.Control.CreateControl()
  at System.Windows.Forms.Control.WmShowWindow(Message& m)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
  at System.Windows.Forms.ContainerControl.WndProc(Message& m)
  at System.Windows.Forms.Form.WmShowWindow(Message& m)
  at System.Windows.Forms.Form.WndProc(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

---

How can I debug this??

I guess I'll ask the obvious... have you ensured they have Microsoft.VisualBasic.PowerPacks.Vs ?

Further to what FA said, the VB PowerPacks, which are installed with VS 2008 SP1, are NOT a standard part of the .NET Framework. If you use a component from the VB PowerPacks then you must make sure that the appropriate library is available on the target machine. That can happen in three ways:

1. You check the VB PowerPacks item in the Prerequisites dialogue of your ClickOnce publishing page or your Setup project.

2. You install manually on the target machine using the redistributable package downloadable from MSDN.

3. You change the reference's Copy Local property to True in your project.

Thanks for asking the obvious...

Found out that I added a LINE SHAPING type of control to a form over the weekend - and that required the powerpack to be downloaded and installed...

Arrgghh....

I removed the line

http://social.msdn.microsoft.com/For...f-cda95575a6be