ClickOnce .Exe runs briefly, then disappears

26 Jan 2006 5:04 PM

ivan.no.spam

My network-drive deployed Clickonce application worked for a while when
deployed onto the machine on which it was developed (it still works
fine on other machines). Now, when run (on the development machine),
the .exe instantiates briefly (I can see it in the task manager process
list), then just disappears (i.e. no longer in the task manager process
list) - no exceptions are raised. The bizarre thing is that if I copy
the entire name-mangled application folder (c:\document and
settings\...\local settings\Apps\2.0\... ) from its deployment
destination, and paste it somewhere else on the hard drive (c:\temp,
for example), the .exe works fine. The application is designated as a
full trust application (My Project -> Security), and I successfully
execute

Dim p As New
System.Security.PermissionSet(Security.Permissions.PermissionState.Unrestricted)
p.Demand()

early on in the code, so it doesn't appear to be a security issue. Any
ideas?

26 Jan 2006 6:50 PM

Naveen

If it is a partially trusted click once application it wont be visible
in the task manager. But you will see a process called Applaunch.exe,
which acts as a shim for the click once application.

You can read more about this here

http://blogs.msdn.com/shawnfa/archive/2005/11/30/498610.aspx

28 Jan 2006 12:39 PM

Nicole Calinoiu

Depending on how where you're executing your unrestricted permission demand,
you may not actually be testing whether your application is fully trusted.
When Demand is called for a standard CAS permission, the stack frame in
which the method is called is not evaluated for the demanded permission.
(i.e.: The method from which you call Demand gets skipped over.) If you're
making the demand from your application's Main method, there won't be any
stack frame evaluated from your application's assembly, and the demand will
pass even if your assembly is not granted unrestricted permissions. To
ensure that at least one method from your assembly is included in the
demand, simply move the Demand call into another method that can be called
from your Main method. e.g.:

Sub Main()

      DemandFullTrust()
      '...

End Sub

Private Sub DemandFullTrust()

      Dim p As New
System.Security.PermissionSet(Security.Permissions.PermissionState.Unrestricted)
      p.Demand()

End Sub

<ivan.no.spam@gmail.com> wrote in message
Show quote

news:1138295054.536959.28120@g47g2000cwa.googlegroups.com...
> My network-drive deployed Clickonce application worked for a while when
> deployed onto the machine on which it was developed (it still works
> fine on other machines). Now, when run (on the development machine),
> the .exe instantiates briefly (I can see it in the task manager process
> list), then just disappears (i.e. no longer in the task manager process
> list) - no exceptions are raised. The bizarre thing is that if I copy
> the entire name-mangled application folder (c:\document and
> settings\...\local settings\Apps\2.0\... ) from its deployment
> destination, and paste it somewhere else on the hard drive (c:\temp,
> for example), the .exe works fine. The application is designated as a
> full trust application (My Project -> Security), and I successfully
> execute
>
> Dim p As New
> System.Security.PermissionSet(Security.Permissions.PermissionState.Unrestricted)
> p.Demand()
>
> early on in the code, so it doesn't appear to be a security issue. Any
> ideas?
>