How to configure XsltDb Rich Editor?

Sep 12, 2010 at 6:48 PM

I just downloaded XsltDb (for DNN 5). After installation and entering domain/username/password, it displays the two instances where I have modules that use this on my site. (Issue 1: Note that Tab Name - i.e., page name) does NOT show up.)

Then then I double clicked on either of the two lines, rather than have the XSLT come up in Visual Studio 2010 as expected, I got the following error dialog, the the full contents listed below.

Is it one of the following?

- Do I need to have the DotnetNuke site on the same system as Visual Studio? (I thought this requirement was only if one wanted to step through the code during debugging, as noted at http://xsltdb.codeplex.com/wikipage?title=XsltDb%20Developer%20Tools?)

- Is Visual Studio not setup normally (I'm not aware of anything unusual with my install on Win 7 x64)?

- Do I need to explicitly configure Visual Studio to handle these JIT exceptions, as it sounds like from the following error message? If so, it sounds like I need to edit the machine.config file (but which one? On my local machine, I have many, e.g., at C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config or on the remote server, or what?) to edit the jitDebugging value in the system.windows.forms section as follows:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

error1

After ignoring the error, the following dialog popped up.

error2

Full error message follows:

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

************** Exception Text **************
System.ComponentModel.Win32Exception: No application is associated with the specified file for this operation
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at XsltDbClient.Form1.lstModules_ItemActivate(Object sender, EventArgs e)
   at System.Windows.Forms.ListView.OnItemActivate(EventArgs e)
   at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
   at System.Windows.Forms.ListView.WndProc(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)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
XsltDbClient
    Assembly Version: 1.1.0.8
    Win32 Version: 1.1.0.8
    CodeBase: file:///C:/Program%20Files%20(x86)/Findy/XsltDb%20Rich%20Client/XsltDbClient.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.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.

Coordinator
Sep 13, 2010 at 5:26 AM

Thank you very much for detailed explanations.

  • Tab title is not shown after DNN5 introduced a new localization architecture. I'll fix it in next relese. It will take me about couple of days to prepare new release. I'll notify you in this thread.
  • Exception is telling you that you have no XSLT editor on your computer. You must have an application associated with .xslt extension to use Rich Client. So you must run Rich Client on the computer where VS is installed. Or install any othe xslt editor.
  • Yes, it doesn't matter where DNN is running to use Rich Client.
  • Message "the following modules are under control" just informs you that you edited (or at least tried to) particular modules and maybe they must be saved before exiting. As far as I can't access xslt editor (as far as it is external application) I can't create a message like "module ... in not saved." So I just remind that you maybe have to save your work before exiting Ric Client.

 

 

 

 

Coordinator
Sep 15, 2010 at 10:11 AM

TabTitle is fixed in 02.00.09

You need only XsltDb module. Rich Client is not changed.