Hi!

Attached is a patch that adds "fromframework" feature to all filesets.

When you include a file with fromframework="true" its full name will be
determined by Path.Combining it with current framework's assembly directory.

This is useful for compilation of .NET CF programs where you need to specify
your own corlib and System.dll paths.

This also helps you get rid of:

<includes name="System.Data.dll" asis="true" />

which relies on csc.exe being able to find its own framework assemblies.
When fromframework="true" is used, csc is given the fully qualified path
name where the assemblies reside and doesn't have to do any "guessing".

Basically, when you replace asis="true" with fromframework="true" in
references to system assemblies, your project should remain correct, yet it
would get the ability to be buildable for .NET CF.

Can someone review it and apply to CVS ? The patch was made against a fresh
anonymous CVS checkout.

Jarek

BTW. If someone can invent any better name (than fromframework), feel free
to change it.

Attachment: fromFramework.patch
Description: Binary data

Reply via email to