Changes in project file without model changes

0
Hello Mendix community, Recently I have been getting a fairly odd massages from the modeler from time to time. It says the following: "The project file is modified even though there are no model changes. This can happen because of the file format used for modeler projects." I can't reverse the change(s) for some reason. Which seems odd to me. I'm now committing changes which I can't see properly and thus don't know which changes are being committed exactly.  It doesn't seem to cause any issues but I'm still curious what this means. Is my laptop changing the project file slightly? Can anybody tell me more about this message? Thanks in advance! Cheers, Hessel
asked
5 answers
1

Hi Hessel,

I have seen something similar before as well. If you open the .project file in an editor there is a <name>-tag which reflects your folder name(?).

If you have main line or any other branch in different folders I think that it will create the modification.

If you have turtoise svn installed you can look at the difference between the base and your changed file to see what differs.

 

/Johan

answered
1

I have also seen this happen. It can easily be reproduced using the following steps (although this might not be the cause of the behavior in this specific case)

 

1) Open a project with no changes (fresh from teamserver, or right after a successful commit)

2) Make a change in the modeler (e.g. move a microflow step or add a widget to a page) and perform a save 

3) Revert the change you just made

 

I suspect that it has to do with the fact that the last changed date of the project file is updated, which register as a change for svn although nothing has actually changed..

 

 

answered
0

The way the model is stored means that after certain operations the bytes of the mpr file can be different although they represent the same thing. This is nothing to worry about but we need to show a change because SVN sees a different file.

answered
0

Hi all,

I would like to add to this discussion that this issue does prevent you from pulling from the Team server.

You have to commit this non-change before pulling. So it is harmless but a bit annoying...

answered
0

Hi,


This message is expected behavior and is related to how Mendix Studio Pro stores project metadata internally. It does not necessarily indicate actual model changes.

Let me clarify what is happening.

Why This Message Appears

Mendix projects are not stored as a single file. Instead, they consist of:

  • Model files
  • Metadata files
  • Project configuration files
  • Internal index and cache information

The message:

“The project file is modified even though there are no model changes. This can happen because of the file format used for modeler projects.”

means that non-functional metadata inside the project file has changed, even though no domain model, microflow, or page logic has changed.

This typically happens because:

  • Studio Pro updates internal timestamps
  • Project format normalization occurs
  • Internal ordering of XML elements changes
  • A different Studio Pro version rewrites metadata
  • File encoding or line-ending normalization occurs
  • Local environment differences trigger reformatting

These are structural or formatting-level changes, not logical model changes.

Why You Cannot See the Changes

In version control, these differences often:

  • Do not appear clearly in the changes viewer
  • Are too small (e.g., whitespace, ordering)
  • Occur inside binary or structured metadata files

That is why you cannot identify visible changes in Studio Pro.

Is Your Laptop Changing the File?

Indirectly, yes — but not in a problematic way.

Possible triggers:

  • Opening the project in a slightly different Studio Pro patch version
  • Switching between machines
  • Updating Studio Pro
  • Automatic migration of internal project format

Studio Pro sometimes rewrites project files to align with the current internal format.

Does This Cause Issues?

In most cases:

  • No functional impact
  • No runtime impact
  • No risk to application logic

It is generally safe to commit these changes.

Best Practices to Reduce Noise in Version Control

  1. Ensure the team uses the exact same Studio Pro version (including patch version).
  2. Avoid switching frequently between different Studio Pro versions.
  3. Do not manually modify project files outside Studio Pro.
  4. Keep consistent OS line-ending settings if using Git.

When Should You Be Concerned?

You should investigate further only if:

  • The project fails to start
  • You see unexplained merge conflicts
  • The changes occur repeatedly without opening the project
  • You observe corruption or deployment issues

Otherwise, this message is informational and not an error.


Conclusion

This message indicates internal project file metadata changes, not actual model changes. It is normal behavior related to the file format and Studio Pro’s internal structure management.

It is safe to commit these changes if no functional modifications were made.

This explanation aligns with Mendix project structure behavior and common version control experiences in team environments.


answered