number of components limited in td SP2 ?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hello everybody,

is there any limitiation (by bug or by design) about the number of componts
used in a single slx file?

i am facing problems with my configuration.
Currently my config has about 1400 components (a xppro emulation).
If a import about 1600 additional components in my configuration i cannot
save the slx files, error message is "not enough storage to complete the
operation"
if i crate a macro with approx 2000 of components and import the macro in my
configuration dependency check fails with error message "out of memory".

on my hdd is > 6G free, i have 2GB Ram. I applied MSDE SP4 and limited the
MSDE Ram Usage to 500M.

i know it is worth discussing the usage of so many components, but i just
want to know if there is a known limitation or a problem with my setup.

kind regards
bernhard
 
Bernhard,

The TD's "not enough storage to complete the operation" fatal error message
is an old known issue which is extremely annoying when you play with huge
projects.
The issue is not about how much free space or RAM you have availalble on the
dev machine. It rather has to do with VBScript, # of component in Config and
database load.
AFAIK, there is no fix, no stable workaround for the problem.

Please feel free to add your voice and request a bug fix from the Product
Team:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx.

With regards to the XPProEmulation (component or Config?), you may want to
start *removing" components from the XPProEmulation.slx, rather than
*adding* to your own small project. At least it will save you from the "not
enough storage" error.

KM
 
The workaround I always use is to only add a few components at a time.
Adding 1600 at once is too many. Try to keep it to a couple of hundred
between saves and you should be alright.
 
I agre.

Actually, the XPProEmulation automated script allows to automaticallysave
SLX by some interval. In case you use the XPProEmulation component to add
some # of components (1600 or whatever), set up auto-saving on the Settings
page of the component. (this feature was done specifically to work around
the "not enough storage" bug but still doesn't work stable).

KM
 
thank you all for your quick responses.

in the first step i wil reduce the number of components but it's a good
feeling to have some workarrounds in my toolbox.
i wrote an email to ms. The issue is known but they cannot say if it is
fixed in the next version.

kind regards
Bernhard
 
Back
Top