Upgrade user settings of an external DLL

Question

0.00/5 (No votes)

See more:

Hi!

I've one main app (launcher) and a library containing all ui controls.

When I launch main app (.exe) I try to upgrade dll's user settings calling this method:

public static void CheckForUpgrade()
{
if (Settings1.Default.UpdateSettings)
{
Settings1.Default.Upgrade();
Settings1.Default.UpdateSettings = false;
Settings1.Default.Save();
}
}

When I review logs, i can see upgrade is called, but settings are reset to default values.

There is anyway to upgrade dll settings that it's not in the main (executing) assembly?

What I have tried:

Tried to call this method from the main app. It's defined in the external dll under an static class (SettingsManager)

public static void CheckForUpgrade()
{
  if (Settings1.Default.UpdateSettings)
  {
    Settings1.Default.Upgrade();
    Settings1.Default.UpdateSettings = false;
    Settings1.Default.Save();                    
  }
}

Posted 11-Dec-18 1:11am

sortgnz

Updated 11-Dec-18 1:56am

v2

Add a Solution

2 solutions

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)

OriginalGriff · Answer 1 · 2018-12-11T01:21:00

Solution 1

You need to start by doing two things:
1) Look at the code you are calling, not the code that calls it. The code you show is trivial - you need to look at what the Upgrade method actually does.
2) Use the debugger to check that the CheckForUpgrade method is called, and step through into the Upgrade and Save methods to find out exactly what they are doing. While they do it, check the files you think they should be updating (or the databases if they use them) and make sure that changes go where you expect.

Sorry, but we can't do any of that for you!

Posted 11-Dec-18 1:21am

OriginalGriff

Comments

sortgnz 11-Dec-18 10:20am

Hi OriginalGriff:

As I said, logs tell me that Settings1.Default.Upgrade() is called.
But upgrade() is .net framework and not custom code implemented by myself. (System.Configuration.ApplicationSettingsBase)

I read that settings upgrade is one of the first things to do when release a new assembly.
If another piece of code looks for settings1 before you try to upgrade, the upgrade fails. But is the first line of the main routine.

Thanks for your reply. Sorry my english. First time posting a question as you can see..

sortgnz 12-Dec-18 4:10am

Overriding Upgrade() I can see the problem.
Iterating all SettingspropertyValues and getting previosversion always returns null.

public override void Upgrade()
{

foreach (System.Configuration.SettingsPropertyValue property in this.PropertyValues)
{
try
{
object PreviousValue = this.GetPreviousVersion(property.Name);

if (this.PropertyValues[property.Name] != null)
{
this.PropertyValues[property.Name].PropertyValue = PreviousValue;

}
}
catch (System.Exception ex)
{
LogManager.LogManager.Log.Error(string.Format("Error upgradding setting : {0}", property.Name), ex);
}
}

//base.Upgrade();
}
}

sortgnz · Answer 2 · 2018-12-12T01:21:00

Found workaround here:

c# - ApplicationSettingsBase.Upgrade() Not Upgrading User Settings after Recompiling with .NET 4.0 - Stack Overflow[^]

I think the problem is user settings concurrence related to diferent release/debug versions. (version numbers not correlated, and upgrade doesn't know how to resolve)

Cleaning before testing this feature may solve it.