index > ClickOnce and Setup & Deployment Projects > Click Once Vista disable Virtualization

Click Once Vista disable Virtualization

Hello,

I've added the following trust info into my generate application manifest task.

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">



    <security>



      <requestedPrivileges>



        <requestedExecutionLevel level="asInvoker"/>



      </requestedPrivileges>



    </security>



  </trustInfo>

And the resulting app manifest has this section.

<trustInfo>



    <security>



      <applicationRequestMinimum>



        <PermissionSet Unrestricted="true" ID="Custom" SameSite="site" />



        <defaultAssemblyRequest permissionSetReference="Custom" />



      </applicationRequestMinimum>



    </security>



  </trustInfo>

I must confess, I dont have a complete handle over the security bits in the app manifest. What I need help with is, when the click once app is installed in Vista 32 with UAC enabled, I find in the windows task manager that the process has virtualization enabled. I have other apps that are installed via MSI and carry the trust info in snippet one as a part of the app manifest and those apps have their virtualization disabled.

Why is it that the click once app has virtiualization enabled. The click once app is fully installed on the client(available offline) and runs under full trust. How can I disable virtualization. Am I missing something ?

Any ideas/pointers/or even info that can help will be much appreciated.
Regards,
Avinash

PS: I'm on .Net 3.5 SP1

Edited byavinashraj Wednesday, July 15, 2009 10:34 AM

avinashraj Wednesday, July 15, 2009 10:19 AM

Hi Avinashraj,

The Task Manager Virtualization column represents file and registry virtualization in Windows Vista and this isa compatibility feature. See the following article for more information on file and registry virtualization:
http://windowsconnected.com/blogs/jerry/archive/2005/12/19/file-and-registry-virtualization-the-good-the-bad-and-the-ugly.aspx

The following article explains when file and registry virtualization for processes will be enabled:
http://blogs.msdn.com/uac/archive/2006/02/22/537129.aspx#549260

If you delete the <requestedExecutionLevel> node from the app.manifest, the ClickOnce application will run with virtualizationenabled after it is installed on the client machine.

BTW, the applicationRequestMinimum element represents the code access permissions that the ClickOnceapplication requests. This is not relevant to the virtualization.

Hope this helps.

Sincerely,
Linda Liu

Please remember to mark the replies as answers if they help and unmark them if they provide no help. end us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.

Marked As Answer byLinda LiuMSFT, ModeratorFriday, July 17, 2009 8:03 AM

Linda Liu Thursday, July 16, 2009 6:56 AM

Please remember to mark the replies as answers if they help and unmark them if they provide no help. end us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.

Marked As Answer byLinda LiuMSFT, ModeratorFriday, July 17, 2009 8:03 AM

Linda Liu Thursday, July 16, 2009 6:56 AM

Hello Linda,

Thanks for taking the time to help me out. You're pointing out to CAS gave it away. It turned out to be a bug with how we were generating the deployment manifest. The bug slipped past my initial investigation/code review. Sorry for the bother.

Regards,
Avinash

avinashraj Friday, July 17, 2009 5:52 AM

You can use google to search for other answers

Custom Search

More Threads

• Change Update Location at Client Side

• Deploy web app on Win 2003 Server

• Problem Setting up Prerequisite batch file

• installutil.exe fails w/ release compile; successful w/ debug compile

• Publish ClickOnce with coding signature VERY SLOW

• Default value in a Custom Dialog

• Deployment Windows Application over Domain Controlled Restricted User

• Can ClickOnce deploy resource directories and update files inside them ?

• Installing 2 apps in a single setup process

• Visual studio 2005 distribution - problem with .net framework 2.0 prerequisite