Run wpf application on write protected disk problem

Question

0.00/5 (No votes)

See more:

Hello,
I try to run wpf application on write proteced disk and i got error The disk cannot be written to because it is write protected. Please remove the write protection from the volume ....
As I notice there is no problem with run console application or win form application on write proteced disk - only wpf makes some troubles.
Notice: I cannot remove wire protection, so I'm looking for other solution.
Do anyone has any idea how to run it ?

Posted 17-May-11 2:55am

tklimczak

Updated 18-May-11 4:05am

v5

Add a Solution

Comments

Dave Kreskowiak 17-May-11 9:21am

Since WPF doesn't have anything to do with writing to the disk, what is your app doing that's causing this error to show? Copy your Debug build to a write protected disk, launch it, then attach the Debugger to that process to find out where the problem is.

tklimczak 18-May-11 7:59am

For test I create simple wpf project with empty screen, and I move it into pendrive. I change pendrive settings to "write proteced" mode. When I run this application I stll get this error - so wpf framework try to make some write operration.

EscKey2004 18-May-11 10:23am

You Could Try Monitoring The Application And See What It Is Trying To Access By Using Process Monitor[^]

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

tklimczak · Accepted Answer · 2011-05-18T21:19:00

I found the solution for this problem :

C#

protected override void OnStartup(StartupEventArgs e)
{
    // SEM_FAILCRITICALERRORS = 0x0001
    // The system does not display the critical-error-handler message box. Instead, the system sends the error to the calling process.
    // Best practice is that all applications call the process-wide SetErrorMode function with a parameter of SEM_FAILCRITICALERRORS at startup. This is to prevent error mode dialogs from hanging the application.
    SetErrorMode(0x0001);
}

[DllImport("Kernel32.dll", CharSet = CharSet.Auto)]
private static extern uint SetErrorMode(uint uMode);