Hi,
This is great tool, but unfortunately on our bigger project is nearly unusable.
We have 1700 resource keys in approximately 100 resource files.
When I open ResxManager, visual studio hang to nearly 10 seconds.
Next action unselect all resources, hang next 10 seconds. Practicaly every change selection do this hang.
When I try scroll resources and some name are too long. The ResXManager change layout to show full name, but hang another 5 seconds before change layout.
I profile this preformance issue and attach results .
Results was measured during this sequention actions:
- unselect ALL resources
- select ALL resources
- Scroll from start to end resources
- Scroll from start to end resources
In attachments are unrolled two biggest method.
Thanks .
Comments: ** Comment from web user: tomenglert **
This is great tool, but unfortunately on our bigger project is nearly unusable.
We have 1700 resource keys in approximately 100 resource files.
When I open ResxManager, visual studio hang to nearly 10 seconds.
Next action unselect all resources, hang next 10 seconds. Practicaly every change selection do this hang.
When I try scroll resources and some name are too long. The ResXManager change layout to show full name, but hang another 5 seconds before change layout.
I profile this preformance issue and attach results .
Results was measured during this sequention actions:
- unselect ALL resources
- select ALL resources
- Scroll from start to end resources
- Scroll from start to end resources
In attachments are unrolled two biggest method.
Thanks .
Comments: ** Comment from web user: tomenglert **
I'm testing large projects with the standalone version, selecting the root of several solutions with gives me about 500 projects with 15,000 entries in 30 language.
This takes about 5sec to populate the whole grid, which seems to be acceptable for such an amount of data.
The ProcessMessages that you see in the profiling actually does nothing, it just yields control to the UI so it will do incremental updates - which makes it feel going faster. If I remove this call, the total time for populating the grid is the same...
Maybe you can get the sources and try to remove this call to see what changes on your system.
Also can you compare the VS Extension to the standalone version?