I wonder if we are approaching a limit to the size of the comment file (.DXC file). For our larger .NET component, we have a comment file that has 35,900+ lines (mostly comments) and is over 6 MB. It takes about 30 minutes to open on our standard Windows XP machine, which seems quite bothersome. Also, it is fairly easy to get it to crash by clicking on several hierarchy expand and collapse operations in quick succession. Is there anything we can do about getting it to open quicker? Is there anything we can do about minimizing the crashing (other than slowing down)?
4 comments
-
Permanently deleted user There are a couple of things you can do in this situation. Firstly, you can enable the Load on Demand option in .NET Content Files. To do this, open the Content File Properties dialog by clicking on the Properties toolbar immediately above the tree with your Content File open for edit. Then tick the Load on Demand box. If you haven't currently got this option enabled, it will dramatically improve the Content File load time in the editor.
What you can also do is to split your really large Content File into multiple files. Document! X can use any number of Content Files for the same assembly, so you don't need to keep all your content in just one. You might decide to have one per namespace, or divided up in some other logical way. I would be happy to assist you in dividing your existing Content File into 2 or more files - just email them over to support@innovasys.com FAO Richard Sloggett.
Regarding the crashes you are seeing - next time you see one of those can you click the Send or Refresh button and then follow up with an email to support@innovasys.com so we can investigate that - it's not a problem we are aware of, even with very large content files.
-
FarPointDoc Thanks. I'll try the load on demand setting. I'll also try splitting our biggest. I'll report back with results.
-
FarPointDoc When I set the property for Load on Demand, then I can't see the content from the source code comments, which is usually pretty handy. That's a bummer. Well, I'll play with it and see what the trade-offs are.
And I'll let you know if/when the next time it crashes, which, admittedly, is very rare.
-
Permanently deleted user For the benefit of anyone coming across this post, our 2012.1 version loads on demand by default and includes considerable load performance improvements over the 2008 version.