Number of components with SP2

  • Thread starter Thread starter Thomas Johansen
  • Start date Start date
T

Thomas Johansen

Hi

Now we have installed SP2 and try to use it with out current configuration.
But SP2 add just enough components to make the TD be unable to safe the file
and ultimate corrupts the SLX file !!!!
Target Designer say that there is not enough space for saving the file
etc...

I remember some issues when there is added to many componets to the
configuration, that it could provoke these type of errors ??

Anyone have the same problem ??

Any solution ?

When is this issue gonna be solved with Target Designer ???

Thomas
 
Thomas,

It is really painful bug. I don't think it has been fixed, though :-(
Except the INF importer and SDI automation Dlls no other changes were made to the XPe tools.

Since you don't have much control over TD script and that buggy behavior is unpredictable (hard to say when you get that misleading
"not enough space" error message) you don't have much of the choice but just adding component by component and saving a new copy of
the SLX each time you add a component.

Another idea is if you switch to CMIExplorer rather then using TD. It is not a big deal to create a simple script that will:
- create new or load existing SLX
- upgrade all components of the configuration to new SP
- add any specified components to the configuration
- auto-resolve all dependencies
- save the project file
- build (you can actually use TD here)

You may want to search NG archive where we posted a few CMIExplorer sample scripts.

And the last hope is CMI. You can definitely create a custom CMI app (VBS, JScript or any other script based, or use CMI object
model from VB, C++, etc.) that will operate on your project.

Don't know if this much of help to you,
KM
 
Hi Konstantin,

I really don't know whether to laugh or cry on such simple request and difficult work-around for very serious problem.
Do you know MS opinion on this problem, any plans for fixing this basic error?

Thomas,
Please send MS bug complaint, maybe this will give it higher priority.
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

Sorry that I can't you with this, you should follow Konstanins suggestions they will probably help you solve your problem with some
efforts.

Regards,
Slobodan
 
Slobodan,
Hi Konstantin,

I really don't know whether to laugh or cry on such simple request and difficult work-around for very serious problem.
Do you know MS opinion on this problem, any plans for fixing this basic error?
Click to expand...

No, I don't (anybody does? :-) )

Well.. I can imagine why it may be hard to fix. Basically, all comes to VB script the TD is implemented with. VB sctructures eat
much on memory and when you deal with a bunch of components there are probably not enough memory for some internal stuctures being
created while Saving and the operation fails. Not good error handling.

With VB you often don't get much of control on how much RAM an app consumes.

I think the best would be to re-write everything in C++ so that IDE does not even use VBS for instantiating, checking and building
components. But then it will take a lot of efforts and also MS will have to invent some 'simple' scripting to allow customizations
per component (custom properties, events, a custom script).

In any case it is not going to be easy to implement that properly to work fine with small projects and huge projects.

I always switch to CMIExplorer or CMI directly whenever I have to deal with huge projects. At least IDE does not eat much of memory
there.

Konstantin
 
Thomas,
Please send MS bug complaint, maybe this will give it higher priority.
Click to expand...
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

Bug report send... So now they know what to do this Christmas :-)


Sorry that I can't you with this, you should follow Konstanins suggestions
Click to expand...
they will probably help you solve your problem with some
efforts.

Regards,
Slobodan
Click to expand...
is unpredictable (hard to say when you get that
misleading
Click to expand...
just adding component by component and saving a new copy
 
Hi Thomas Johansen,

When SP2 is Installed,I also got the same problem I was using 256 MB at
that time

It is right time for upgrading the RAM at least to 512

Now I have (256 + 512)MB Till now, i do not have a single problem.
Thanks
Srivathsan.A
 
Back
Top