by: Miha MarkičPosted on:

Righthand DataSet Visualizer now supports Visual Studio 2010

New in 0.9.16: added support for Visual Studio 2010 and updated user interface a bit. As before, everything is merged into a single dll file which is also digitally signed now.

Thanks RedGate {smartassembly} obfuscator tool for merging everything into a single DLL (ILMerge and another 3rd tool failed in this task). So far, I can only praise {smartassembly}.

Read more about Righthand DataSet Visualizer here.

Download the newest and older versions from download section.

Enjoy, and let me know whether you miss features or if you have any other feedback, good or bad.

15 thoughts on “Righthand DataSet Visualizer now supports Visual Studio 2010”

  1. Does the new version still assume that a column of bytes[] type contains an image? Not every byte array is an image. 🙂

    It used to bomb out ungracefully when presented with values of the rowversion ([var]binary(8)) SQL Server Data Type.

  2. You SQL guys, you always want use some odd form of data just to make the life hard for us, don’t you? 🙂
    Seriously, it assumes a picture, yes, but it should just write "no image data" when there is no image or there is a null value.
    Or it (still?) bombs out?

  4. Hi,
    I get the following error when trying to view a DataSet:
    File not found: ‘DevExpress.Skins.GridSkin.OptShowTreeLine’.

    I’ve copied Righthand.DebuggerVisualizer.Dataset.2010.dll to C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\Visualizers

    Any ideas?

      1. Hi Henk,

        Can you tell me what OS are you running and if/what Devexpress components do you have installed?
        And no, everything you need should be packed within the dll.
        BTW, I couldn’t send you an e-mail.

    1. I’m glad you released a new version, i love this sooo much more than the standard one.

      I don’t have the issue like Stanislav on Win7 32bit, with DevExpress DXperience 9.1.10 installed.

      One thing that slightly annoys me though is when selecting tables on the left, it creates a new window instead of just focusing the existing one, i know i can go back to a previous one via the window menu but i never think of it when i’m using it because its out of sight.

      I think that it would be great if single click opened/focused an open table and double click open a new one if for some reason someone wanted it. Any chance of that ?

  6. Hello, thanks for your great tool.
    Would it be possible to add a function "export to excel", which would export the current data table to excel? This functionality is supported by the DevExpress DataGrid, so it shouldn’t be much work on your side 🙂

    Thanks & best regards,
    Urs

  8. Hi Miha ,

    I downloaded the dll but I don’t know how to install it , could you give us a step by step instruction about "How to install it " please?

    Many thanks,
    Farzad

  9. Hi again,

    to be honest, I did follow your guide in this page but I got the below error:

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

    ************** Exception Text **************
    System.IO.FileLoadException: Could not load file or assembly ‘file:///C:\Users\fjalali\Documents\Visual Studio 2010\Visualizers\Righthand.DebuggerVisualizer.Dataset.2010.dll’ or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
    File name: ‘file:///C:\Users\fjalali\Documents\Visual Studio 2010\Visualizers\Righthand.DebuggerVisualizer.Dataset.2010.dll’ —> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
    at System.Reflection.Assembly.LoadFrom(String assemblyFile)
    at Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.ClassAndAssemblySpec.CreateAssembly(Dictionary`2 dictionary, AbstractAssemblyResolver resolver)
    at Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.ClassAndAssemblySpec.CreateInstanceOrType(Dictionary`2 dictionary, AbstractAssemblyResolver resolver, InstanceOrType instOrType)
    at Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.ClassAndAssemblySpec.CreateInstance(AssemblyResolver resolver)
    at Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.ManagedShim.DelegatedHost.CreateViewer(IntPtr hwnd, HostServicesHelper hsh, SafeProxyWrapper proxy)

    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.225 (RTMGDR.030319-2200)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    —————————————-
    Microsoft.VisualStudio.Platform.AppDomainManager
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Platform.AppDomainManager/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Platform.AppDomainManager.dll
    —————————————-
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.225 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    —————————————-
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    —————————————-
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.225 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    —————————————-
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    —————————————-
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    —————————————-
    Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    —————————————-
    Microsoft.VisualStudio.DebuggerVisualizers
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.DebuggerVisualizers/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.DebuggerVisualizers.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.

Leave a Reply