Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1032745
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T14:07:36+00:00 2026-05-16T14:07:36+00:00

Is there any way to create a clickonce deployment where certain assemblies or files

  • 0

Is there any way to create a clickonce deployment where certain assemblies or files in the manifest can be designated as not needing to be downloaded unless the user performs some action in the application that requires them?

Currently, we have a fairly monolithic ClickOnce application and are researching ways to refactor it into separate assemblies.

I am trying to find a way to reduce the initial payload size when I publish an update and only download assemblies when they are required by the user. Is this possible within the ClickOnce architecture? Is there an alternative?

Thanks,
-MrB

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T14:07:37+00:00Added an answer on May 16, 2026 at 2:07 pm

    Here’s the walkthrough: Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer

    Update I would suggest publishing by using the Visual Studio .csproj file. I don’t use TFS, but I do use MSBuild. When I need to produce different manifest files for different environments, I have my build script copy and modify the .csproj file as necessary and then build the Publish target on the modified .csproj. If you want to change which files are require/optional during your build, you could do the same thing and modify the .csproj file before building it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.