1 DocViewerInIE SDK Sample - _ReadMe_.txt
2 Copyright (c) Microsoft Corporation. All rights reserved.
4 -------------------------------------------------------------------------------
5 DocViewerInIE Operating Notes:
7 1. The first time that the project is executed for debug a dialog may appear
8 stating that there is no debug information available for PresentationHost.exe.
9 This dialog can be safely dismissed, simply click OK to continue.
11 2. XAML Browser Applications (XBAPs) must be digitally signed. The DocViewerInIE
12 sample provides a temporary key set with a blank password. If Visual Studio
13 prompts for a password, simply click "OK" to continue.
15 (The temporary key is contained in the file DocViewerInIE_TemporaryKey.pfx)
17 -------------------------------------------------------------------------------
18 XAML Browser Application Notes:
20 1. XAML Browser Applications (XBAPs) run in a protected sandbox with limited
21 "Internet Zone" permissions". Only those .NET Framework 3.0 features
22 validated as safe by the Microsoft.NET security team can run in the sandbox.
24 2. Since XBAP applications execute in the Internet Zone with restricted
25 permissions, normal .NET Framework "Window" operations do not work by design
26 (XBAP applications do not have permissions to "pop-up" new windows).
28 -------------------------------------------------------------------------------
29 XAML Browser Application Debugging - (F5)
31 The "Enable unmanaged code debugging" debug option* must be set to debug a
32 XAML Browser Application in Visual Studio. To do this:
34 1. Start Visual Studio and open the DocViewerInIE.csproj project file.
36 2. On the Visual Studio menu, click "Project", click "DocViewerInIE Properties",
37 and then click the "Debug" tab on the DocViewerInIE properties page.
39 3. On the "Debug" tab under "Enable Debuggers", set the "Enable unmanaged code
42 *Developers using Visual C# and Visual Basic Express do not need to do this.