PythEch

I have Windows 7 x64 normally. I installed VirtualBox newly and installed WinXP Sp3 x86 to test how it's works. I built the app in VS2008 with .NET 2.0. So I quickly installed .net 2.0 framework to virtual winxp. In win7 works quite good, but in XP, it is very very annoying Most of users won't trust me. And the most annoying thing is this thing happens at the main process in the timer. User can't pass clicking continue because timer comes round. I tested which codes are doing this. First one is "static AutoItX3Lib.AutoItX3Class au3;",second one is "au3 = new AutoItX3Lib.AutoItX3Class();", third one is "if (au3.WinActive(title, "") == 1)" and last one is "au3.Send(PressKey(), 0);". third and last one is main process with timer. PressKey() sets which key will be pressed. (Made a combobox to gui. For example, if the combobox is ctrl+x returns "^X"). Is disabling JIT possible or will it solve my problem? The full message of Details in here: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Security.SecurityException: System.Security.Permissions.SecurityPermission at MountBlade.Form1.Form1_Load(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) The type of the first permission that failed was: System.Security.Permissions.SecurityPermission The Zone of the assembly that failed was: MyComputer ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- MountBlade Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///X:/Users/Hakan/Documents/Visual%20Studio%202008/Projects/MountBlade/MountBlade/bin/Debug/MountBlade.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Interop.AutoItX3Lib Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///X:/Users/Hakan/Documents/Visual%20Studio%202008/Projects/MountBlade/MountBlade/bin/Debug/Interop.AutoItX3Lib.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

I added the DLL by browsing, not COM. It readed the all classes. It can be seen by classes table But can't seen when press Ctrl+Space. And can't use the DLL. Debugger shows to me errors when that code being processed. I don't really know SharpDevelop more than you. But, it's not Boo's problem really. Same problem happens in C# too. Boo uses C# compiler and written C# btw. Maybe because of 3.1 version is beta yet. I use the beta because, in stable release, Boo has x64 OS problems. Compiler says can't compile x64 but can't set it to x86. In the new beta version, it can be done. Dynamic languages has advantages, when they are not commercial, more advantages. Same thing happens in static languages. But, when you have dynamic and static lang, you have advantages twice.

Edit on post for Step 3c:

Hi, everyone. First, you can use functions but can't see them on function explorer (Ctrl + Space) and I did this in SharpDevelop 3.1. 1-You need to register the Dll if you can't it see on COM. 1a-To check it, open SharpDevelop, go to Project>Add Reference>COM: Figure-1: 1b-If you can't see it, you must register it. To register it, go to Start>Run then type "cmd.exe" without quotes. Type "cd <AutoItX3.dll's folder's path>" without quotes. And finally, type "regsvr32 AutoItX3.dll" without quotes. Figure-2: 2-Now, you have it on COM. Add it as reference like on Step 1a and Figure-1. When you finish it, you can see it on Projects tab: Figure-3: 3a-Add "import AutoItX3Lib" to your project. (Figure-4). 3b-Add "au3 = AutoItX3Lib.AutoItX3Class()" to use AutoIt functions. An example of using the code: "au3.WinActivate("Untitled - Notepad","")" But you can't see the functions on class explorer. (Figure-5) 3c-(Optional) Add "private static au3 as AutoItX3Lib.AutoItX3Class" to your codes. If you will use "au3" in more than one function etc., add this code. You won't need to set au3 per function. Once you set au3, it can be used by other functions. Seting 3b on form load can be a good idea. (Figure-6) Figure-4: Figure-5: Figure-6: Note: If you want to get function detials/help, click here.

http://www.integralwebsolutions.co.za/Blog/EntryId/364/Optional-Parameters-in-c-4-0.aspx Whatever I solved my problem. I'm waiting for vs2010 full release. Tnx...

Thanks but I want to know a thing. Is there a way to pass optional arguments? Type.Missing is not working. I need it for ControlClick. Thanks...