Removing a dependencys

  • Thread starter Thread starter BJ
  • Start date Start date
B

BJ

I want to remove a Dependency from the .net Framework 1.1
component.

There is a dependency on the "Microsoft Message Queuing
service (MSMQ) core"

Can this dependency be removed?

I tried to disable the file that triggers the dependency
but TD still posts an error during the Dependency scan.
 
BJ,

Although it is a bit risky, you may want to turn off auto-resolve dependencies option in TD (Tools-->Options-->Dependency
Check-->Auto-resolve dependencies).

Another way (trick) is changing .Net Framework 1.1 component. From the .Net QFE package extract 'sld/netfxv1.1.sld' file and open it
within CD. Go to ".Net Framework 1.1 - Hotfix Q831558" component and disable (or delete but disabling is safer) the appropriate
dependency in the "Component and Group Dependency" section. E.g., disable "Message Queuing (MSMQ) Core". Then save and import the
component through CDM (you may notice that the component Revision number will be increased). When you add (or upgrade) the component
in your Configuration and run auto-resolve dependencies, it should not bring the MSMQ Core component in to your build.
Unfortunately, just disabling "Dependency upon 'mqrt.dll'" resource for .Net 1.1 directly in TD did not help me to remove the MSMQ
Core.

Please keep in mind that you are technically responsible (testing, testing, testing) for how your image works if you remove the
dependencies.
 
Please keep in mind that you are technically responsible (testing,
testing, testing) for how your image works if you remove the
dependencies.
Click to expand...

And who is responsible when things are not working and we resolve all
dependencies ;)
Guess who we are again responsible, so (testing, testing, testing, ........)
is something we must always do :-)

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

KM said:
BJ,

Although it is a bit risky, you may want to turn off auto-resolve
Click to expand...
dependencies option in TD (Tools-->Options-->Dependency
Check-->Auto-resolve dependencies).

Another way (trick) is changing .Net Framework 1.1 component. From the
Click to expand...
..Net QFE package extract 'sld/netfxv1.1.sld' file and open it
within CD. Go to ".Net Framework 1.1 - Hotfix Q831558" component and
Click to expand...
disable (or delete but disabling is safer) the appropriate
dependency in the "Component and Group Dependency" section. E.g., disable
Click to expand...
"Message Queuing (MSMQ) Core". Then save and import the
component through CDM (you may notice that the component Revision number
Click to expand...
will be increased). When you add (or upgrade) the component
in your Configuration and run auto-resolve dependencies, it should not
Click to expand...
bring the MSMQ Core component in to your build.
Unfortunately, just disabling "Dependency upon 'mqrt.dll'" resource for
Click to expand...
..Net 1.1 directly in TD did not help me to remove the MSMQ
Core.

Please keep in mind that you are technically responsible (testing,
Click to expand...
testing, testing) for how your image works if you remove the
 
Oh, yeah! No doubt :-)

I guess the major part of a XPe development process is the testing. Here it is even more important than, say, in Windows CE or Linux
Embedded development. The reason may be because XPe comes from desktop XP and it is very feature/application rich embedded OS. While
CE or LE comes from real embedded world where "embedded rules" are more known and devs think more about implementation (real time,
new device support, etc.) than componentization. Although, it may be very narrow view to the OSs as CE is well componentized OS.
 
Back
Top