I'm evaluating Aspose Editor. I'm tried creating the sample project that is listed in the documentation and cotinue to receive the following exception everytime I try to do anything with the editor. I followed the directions on how to set your permissions but I still continue to get this exception. Please advise.

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

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'xc2c477ae06969bcc.x99d36eaeb8e190b8' threw an exception. ---> System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
   at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet)
   at System.Security.CodeAccessPermission.Demand()
   at System.Drawing.Graphics.FromHwnd(IntPtr hwnd)
   at xc2c477ae06969bcc.x99d36eaeb8e190b8..cctor()
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.SecurityPermission
   --- End of inner exception stack trace ---
   at xc2c477ae06969bcc.xcd0f71eac0b8ec87.x7516829ed6513963(Graphics x4b101060f4767186, Int32 x01023a7c5d96848c, Int32 x9528f9664a3881e3, Int32 xf67d0ad06e5256e3, Int32 x58fbd68b6e9d8f70, Int32 x7304b15c2c6eea76, Int32 x5b2cec0df3c4dbd1, Single x9570f4c9d2722802, Single x96a6a0179b30d7b8)
   at x695c6a2fce4e6e02.xbe47ed34daf505bb.x58956ea72b60eca5(PaintEventArgs xfbf34718e704c6bc)
   at x695c6a2fce4e6e02.xbe47ed34daf505bb.OnPaint(PaintEventArgs e)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at x695c6a2fce4e6e02.xbe47ed34daf505bb.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)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Aspose.Editor.Client
    Assembly Version: 2.3.0.1979
    Win32 Version: n/a
    CodeBase: http://localhost/EWAPPM/ClientBin/Aspose.Editor.Client.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.mshtml
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.0.3300.0
    CodeBase: file:///C:/WINNT/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

 

Hi,
Thanks for your interest in Aspose.Editor.

Please, specifiy your system configuration details:

- OS version,
- .NET runtime (all versions installed),
- browser version,
- Web Server version,
- client/server details (what is the network environment, server os, or maybe both server and client are on the same machine)

Does the editor window show normally (with toolbar, scrolls, menu) after loading or it shows as disabled control, red cross or something else?

---

Dmitry Burov
Lead Developer, Aspose Auckland Team

- Windows XP

- .net 2.0 I also have .net 1.1 installed on my machine but i'm running 2.0 on for the site I'm using for testing.

-IE 7

-IIS 5

- I have the sever and client on the same machine.  I'm developing the site in VS 2005.

The editors window show normally but it has a red cross in the top part of the page. I attached a screen shot. I followed all the directions for Step 3 in the Create and ASP.net application doc.

 

 

Hi,
thanks for the information.

This is security exception, access to the handle of the desktop window is not granted to the Ruler control which is part of the editor.

Try the following:
1) Close IE,
2) Go to the .NET 2.0 folder, typically located at C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727,
3) In the command prompt run 'caspol.exe -s off',
4) While prompt is waiting open your page in the IE,

If page is opened successfully then this is security policy which prevents it from running. You'll need to find out why requested rights are not granted to the control.

Run 'caspol -lg' and make sure you have something similar in the list
Url - http://localhost/your_app_name/*: FullTrust

If you are running your app from the VS2005 (not from IIS) then make sure URL statement above includes custom port used by VS2005.

Kind regards,
Michael

After turning the security off the application worked. It doesn't work if its on. Also the site is listed in the fulltrust list.

Hi,
.NET security is a huge topic to discuss in general.

If you are on a corporate domain, please talk to IT people, your computer can be managed by domain policy.

The basic setup is when you have fresh install of Windows, you are local administrator and all settings for IIS, IE, etc. are default. Then you add URL group to the policy and everything works fine.

In your case there is something which makes control run with limited rights. I think this is not purely policy setting but it is something related to how OS decides which policy settings are applicable to the controls running in IE.

Search through the .NET security forums and MSDN. There can be something we can do to the control, or provide with control, which helps resolve security issues. If you know what - tell us and we'll do it.

Kind regards,
Michael

Can you be more specific. We are in a copororate environment with different domains.Can this tool handle this? Is it requrired that every user set his/her permissions.

Hi,
this security issue is not related to only Aspose.Editor. It is related to all .NET controls running on the machine. Each control is granted permissions according to the security policy. Control can't get more permissions from the OS and can't change security policy (unless it has this permission).

Security is part of the .NET runtime and code which runs on the CLR have to obey these rules. That's why it's called managed.

Policy is the hierarchical structure which specifies security rules. It is configured on enterprise, machine and user levels. On each level of the policy code groups can be defined and granted with selected permission sets. This is done by administrator of the machine or domain administrator. Resulting permissions for a particular application are calculated using set of rules which is received by intersecting all rules defined on all levels. This means that domain security policy will affect rights given to the application. Even if machine level grants unlimited permissions, application may not get them because of the rules defined for the enterprise (domain level).

Hope this helps.

P.S. You have to consult with domain administrator about domain security policy.

Kind regards,
Michael

Thanks for the help mf.

So it's required that each user have admin rights on his/her machine?

Thanks

No. It is required to properly configure security policy. Which in your case should be done by domain administrator.

Kind regards,
Michael