You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No Support for ApplicationDeployment.CurrentDeployment.ActivationUri.Query #1
Is there a support for retrieving the query string parameters for a web deployed clickOnce application in netcore3.1 using
ApplicationDeployment.CurrentDeployment.ActivationUri.Query?
I see the ClickOnceApplicationDeployment.CurrentDeployment_DotNet object does not have ActivationUri or something similar.
If you would like to submit a PR, I would happily add it.
My applications are all updated from an internal network drive, so I wouldn't know about what that your particular setup needs, and haven't used that function so wouldn't know where to begin validating it's results.
I basically created this since I couldn't find one that made it a (mostly) seamless transition from NetFramework over to Net5 while i am migrating my app. As such, it's essentially just a wrapper for both assemblies to normalize accessing the core methods/properties each assembly was providing. ( my use case is primarily retrieving info about the assembly itself, the updating functions are out of my scope, but I wrapped them and since both assemblies this wraps work, that should work as well)
Activity
RFBomb commentedon Jun 28, 2022
If you would like to submit a PR, I would happily add it.
My applications are all updated from an internal network drive, so I wouldn't know about what that your particular setup needs, and haven't used that function so wouldn't know where to begin validating it's results.
I basically created this since I couldn't find one that made it a (mostly) seamless transition from NetFramework over to Net5 while i am migrating my app. As such, it's essentially just a wrapper for both assemblies to normalize accessing the core methods/properties each assembly was providing. ( my use case is primarily retrieving info about the assembly itself, the updating functions are out of my scope, but I wrapped them and since both assemblies this wraps work, that should work as well)