How to: Debug a Partial Trust Application
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic applies") |
|
.gif "Topic does not apply") |
|
Standard |
|
|
|
|
Pro and Team |
|
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
Applies to Windows and console applications. Does not apply to Smart Devices.
ClickOnce Deployment makes it easy to deploy partial trust applications that take advantage of Code Access Security to limit access to resources on a machine.
Debugging a partial-trust application can be a challenge, because partial trust applications have different security permissions (and therefore behave differently) depending on where they are installed from. If installed from the internet, a partial trust application will have few permissions. If installed from a local intranet, it will have more permissions, and if installed from the local computer, it will have full permissions. You may also have custom zones, with custom permissions. You may need to debug a partial trust application under any or all of these conditions. Fortunately, Visual Studio makes this easy as well.
Before you start a debug session in Visual Studio, you can choose the zone you want to simulate an application installed from. When you start debugging, the application will have permissions appropriate to a partial trust application installed from that zone. This enables you to see the behavior of the application as it would appear to a user who downloaded it from that zone.
If the application attempts to perform an action it does not have permission for, an exception occurs. At that point, the Exception Assistant gives you the chance to add an extra permission, which allows you to restart the debugging session with sufficient permissions to avoid the problem.
Later, you can go back and see which permissions you added during debugging. If you had to add a permission while debugging, it probably indicates that you need to add a User Consent Prompt at that point in your code.
Note
Debugger visualizers require greater privileges than are allowed by a partial trust application. Visualizers will not load when you are stopped in code with partial trust. To debug using a visualizer, you must run the code with full trust.
To choose a zone for your partial-trust application
From the Project menu, choose ProjectnameProperties.
In the Projectname property pages, click the Security page.
Select Enable ClickOnce Security Settings.
Under Zone your application will be installed from, click the drop-down listbox and choose the zone you want to simulate the application being installed from.
The Permissions required by the application grid shows all available permissions. The check mark indicates permissions granted to your application
If the zone you choose was (Custom), select the correct custom settings in the Setting column of the Permissions grid.
Click OK to close the property pages.
To add an extra permission when a security exception occurs
The Exception Assistant dialog box appears with the message: SecurityException was unhandled.
In the Exception Assistant dialog box, under Actions, click Add Permission to the Project.
The Restart Debug dialog box appears.
If you want to restart the debugging session with the new permission, click Yes.
If you don't want to restart yet, click No.
To view extra permissions added while debugging
From the Project menu, choose ProjectnameProperties.
In the Projectname property pages, click the Security page.
Look at the Permissions required by the application grid. Any extra permission you added has two icons in the Included column: the normal checkmark, which all included permissions have, and an additional icon, which looks like a balloon containing the letter "i".
Use the vertical scrollbar to view the entire Permissions required by the application grid.