I'm having a little issue with ProjectDefinition.MarkProjectAsChanged(). I'm adding some properties to the projectdefintion duing a custom task and callling the above function (though NoChangeEvent must be set to true first).

The project in the Project Explorer gets marked as expected, however if I try to close the project I do not get a "save?" dialog. It's a minor thing but could cause users to loose their data. Any ideas?

What do you mean by The project in the Project Explorer gets marked as expected?

It should give you the 'do you want to save lalala' message because the project is changed. Though you shouldn't set NoChangeEvent to true, as that would make the project not signal it was changed to observers.

Though if I were you, I'd move the tasks you want to do to a plugin and leave the tasks for code generation / output purposes.

Otis wrote:

It should give you the 'do you want to save lalala' message because the project is changed. Though you shouldn't set NoChangeEvent to true, as that would make the project not signal it was changed to observers.

Though if I were you, I'd move the tasks you want to do to a plugin and leave the tasks for code generation / output purposes.

Sorry, I meant I set the NoChangeEvent to false.... well specifically I save what it is in a tmp variable, set it to false, then set it back to whatever it was (which I beleive is true at that point).

I'm avoiding using a plugin because I'm looking for a specific behavior that popups up a configuration dialog when the user does a regen. Unless I'm missing something a plugin can't popup a dialog during that time?

Cadmium wrote:

Otis wrote:

It should give you the 'do you want to save lalala' message because the project is changed. Though you shouldn't set NoChangeEvent to true, as that would make the project not signal it was changed to observers.

Though if I were you, I'd move the tasks you want to do to a plugin and leave the tasks for code generation / output purposes.

Sorry, I meant I set the NoChangeEvent to false.... well specifically I save what it is in a tmp variable, set it to false, then set it back to whatever it was (which I beleive is true at that point).

I'm avoiding using a plugin because I'm looking for a specific behavior that popups up a configuration dialog when the user does a regen. Unless I'm missing something a plugin can't popup a dialog during that time?

I think I know what's the cause. The code generation start routine preserves the project change state till after the generation cycle has been completed, then it stores the data used for the generation process like rootnamespace etc. which then will mark a project as changed if it's different. So your change marking doesn't have any effect.

You can't run a plugin at generation time indeed...

Otis wrote:

You can't run a plugin at generation time indeed...

What am I doing to your baby?