Search Results

Search found 9 results on 1 pages for 'moogs'.

Page 1/1 | 1 

• Avoiding .NET versioning hell

  - by moogs

  So sometimes (oftentimes!) you want to target a specific .NET version (say 3.0), but then due to some .NET service packs you get into problems like: Dispatcher.BeginInvoke(Delegate, Object[]) <-- this was added in 3.0 SP2 (3.0.30618 ) System.Threading.WaitHandle.WaitOne(Int32) <-- this was added in 3.5 SP1, 3.0 SP2, 2.0 SP2 Now, these are detected by the JIT compiler, so building against .NET 3.0 in Visual Studio won't guarante it will run on .NET 3.0 only systems. Short of confirming each and every function you use, or limiting your development environment to .NET 3.0 (which sucks since you have to develop for other projects too) what's the best way to avoid against using extensions? Thanks!

  Read the article

• .NET Debugging - System.Threading.ExecutionContext.runTryCode

  - by moogs

  We have this bug that only appears 30% of the time for the Release build. Opening the crash dump in WinDbg (snipped "!analyze -v" output): FAULTING_IP: +4 00000000`00000004 ?? ??? EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 0000000000000004 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 0000000000000004 Attempt to execute non-executable address 0000000000000004 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. WRITE_ADDRESS: 0000000000000004 MANAGED_STACK: (TransitionMU) 0000000024B9E370 000007FEEDA1DD38 mscorlib_ni!System.Threading.ExecutionContext.runTryCode(System.Object)+0x178 (TransitionUM) (TransitionMU) 0000000024B9DFB0 000007FF00439010 MyLibrary!DocInfo.IsStatusOK()+0x30 Now, IsStatusOK() just calls PrintSystemJobInfo.Get(), but that doesn't seem to even appear in the stack. Any ideas on how to debug this? I'm sure runTryCode() is really not the problem...but..I'm stuck. Thanks! (I'm really groping here).

  Read the article

• SNMP from the browser

  - by moogs

  There"s this idea of having a web app search for devices in the network (with elevated user permissions, of course). Checking the silverlight and flash APIs, there does not seem to be a way to do SNMP ( the UDP APIs are limited to multicasting media ). Anyone know a clever workaround? In windows, a small XBAP utility can do the SNMP stuff, but that leaves out the Mac OS X platform. Thanks for any ideas. ( I do have a SO account but I"m in a not so trustworthy public PC right now so I didn"t log in. )

  Read the article

• Interpreting WPF Dependency properties as a set.

  - by moogs

  So, I have a control. It displays an image based some xml document and an optional parameter "Document" - XML document "RenderingOption" - optional image-rendering ( sharpen, soften ) So: <XMLRenderingWidget Document="xxxxxx"/> The above will render the document once <XMLRenderingWidget Document="xxxxxx" RenderingOption="Sharpen"/> The above will, sometimes render the document once, more oftentimes: Perform the rendering of the document as if no Rendering was set then, re-render the document with the Sharpen option I do the rendering on the PropertyChangedCallback assigned to the property. How do I tell the control to "hey, before doing the rendering, apply the changes on the other properties being set, too" Is this not possible? Should I bundle them up as one property instead?

  Read the article

• Window Size when SizeToContent is not specified

  - by moogs

  When the following XAML used, the window size is not 5000x5000, but some small window where the button is cropped. <Window x:Class="WpfApplication1.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="Window1" > <Button Width="5000" Height="5000">XXX</Button> </Window> From what I can tell, size I did not specify the SizeToContent attribute, the default is "Manual", so it will use *size of a window is determined by other properties, including Width, Height, MaxWidth, MaxHeight, MinWidth, and MinHeight. * From the WPF Windows Overview, it seems those other properties are FrameworkElement::MinHeight/Width, and FrameworkElement::MaxHeight. But since the default for the Mins are 0, the Maxs are Infinity and the Width/Height is Nan....what's going on? Where is WPF getting the window size? Any pointers to the right direction would be appreciated.

  Read the article

• Native.* assemblyIdentity with Registration-free com

  - by moogs

  I set Isolated=true to some COM library that I need to use registration free. Visual studio now created Native.* manifest files for each of my assemblies: Why "Native"? Can I change this? Can someone point me to info I can read? (googling native / assembly / manifest is yield a lot of non-related info ) Is there a way I can embed these manifest files into the assembly DLL? Thanks!

  Read the article

• .NET Application using a native DLL (build management)

  - by moogs

  I have a .NET app that is dependent on a native DLL. I have the .NET app set as AnyCPU. In the post-build step, I plan to copy the correct native DLL from some directory (x86 or AMD64) and place it in the target path. However, this doesn't work. On a 64-bit machine, the environment variable PROCESSOR_ARCHITECTURE is "x86" in Visual Studio. My alternative right now is to create a small tool that outputs the processor architecture. This will be used by the post-build step. Is there a better alternative? (Side Note: when deploying/packaging the app, the right native DLL is copied to the right platform. But this means we have two separate release folders for x86 and AMD64, which is OK since this is for a device driver. The app is a utility tool for the driver).

  Read the article

• Saving WPF WIndow and Position

  - by moogs

  What would be the best way to save the window position and size in a WPF app? Currently, I'm saving the window size and position of a WPF App. Here are the events I handle: SourceInitialized : The saved info is loaded on to the window WindowClosing : The current info is saved to the backing store (I copied this from an example). The problem is, when the window is minimized and restored, the settings from the last WindowClosing is retrieved. Now, the StateChanged event fire AFTER the window has minimized, so it does not seem to be what i need. Thanks

  Read the article

• Warn user of .NET Framework requirements

  - by moogs

  So I have an app (tool) that uses .NET 3.0. When run on a machine that only has .NET 2.0 (like the default Server 2008 R2 install) it crashes miserably. What I've seen so far is that people are using a shunt that will first check the .NET version. Is there a way to build it or add some manifest somehow so that the user is warned of this problem (and hopefully be prompted to install .NET)? I know this can be solved by an installer, but I have requirements that need it to be a standalone executable.

  Read the article

1