Debug vs. Release

  • Thread starter Thread starter Larry Waibel
  • Start date Start date
L

Larry Waibel

Is there a way to have a .slx file that includes some components when built
in debug mode and others when in release (and some in either)? Maybe I'm
missing something very obvious but I sure can't find it. Thanks!
 
Larry,

A couple of facts:
- There is no Debug Repository provided by Microsoft for XPe (any SP). This is really, really sad but it is true :-(
- There is no Tool supported way to have Debug and Release component configurations in one build.

However you can:
- Have two similar configurations - Debug and Release (obvious way)
- In one configuration have two instances (Debug and Release instances) of a component and have one of them disabled/enabled at
one time.
- Create a CMI script that will go with the Configuration and/or some component (like "Debug support in the build" component).
The script will take care of the switch between Debug and Release mode for the Configuration that runs this script. The script can
be invoked: manually, on component activation, on build, on dependency check, etc.
 
Wow, I guess I wasn't missing anything, but it sure should be there! <g> It really is sad
that this isn't supported. Here's another thought that I doubt will work but I'll ask
anyway; if I had a component that had all the dependencies for the stuff needed for debug
then I could do a dep check and get them. The problem is if I disable that component, will
the things it brought it that now aren't needed go away? Looks to me like the only way is
the 'obvious way' :-) and that's just a problem waiting to happen because of the double
maintenance.

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Debug vs. Release
Date: Thu, 3 Feb 2005 10:26:02 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

A couple of facts:
- There is no Debug Repository provided by Microsoft for XPe (any SP). This is
Click to expand...
really, really sad but it is true :-(
- There is no Tool supported way to have Debug and Release component configurations in one build.

However you can:
- Have two similar configurations - Debug and Release (obvious way)
- In one configuration have two instances (Debug and Release instances) of a
Click to expand...
component and have one of them disabled/enabled at
one time.
- Create a CMI script that will go with the Configuration and/or some component (like
Click to expand...
"Debug support in the build" component).
The script will take care of the switch between Debug and Release mode for the
Click to expand...
Configuration that runs this script. The script can
 
Larry,
Wow, I guess I wasn't missing anything, but it sure should be there! <g> It really is sad
that this isn't supported. Here's another thought that I doubt will work but I'll ask
anyway; if I had a component that had all the dependencies for the stuff needed for debug
then I could do a dep check and get them. The problem is if I disable that component, will
the things it brought it that now aren't needed go away?
Click to expand...

No, they will stay. This is one more dev tool current (sad) limitation :-(
Add your vote through the Product Team feedback page:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

Again, all this things could be fixed (easy or hard) from CMI level but you really need to know the object model before even diving
in to that. Since it is undocumented I wouldn't recommend you to go this way unless you have much of free time :-)
 
Back
Top