When I use VS.NET 2003 I can have the following structure for my project Folder1 Folder2 File.xml
and on the properties screen choose the Compile Action to be an Embedded Resource and it will be compiled into the manifest as
.mresource public DefaultNamespace.Folder1.Folder2.File.xml
{
}I have been unable to duplicate that functionallity in NAnt using the Resource element and all of the various attributes.
I found the following bug http://sourceforge.net/tracker/index.php?func=detail&aid=805307&group_id=31650&atid=402868 that was geared towards fixing problems with as?x files and another posting of similar problem with crystal reports http://www.mail-archive.com/[EMAIL PROTECTED]/msg01691.html
The Crystal Reports mailing suggestion was to rename the file to DefaultNamespace.Folder1.Folder2.File.xml. If I do that and do a compile from VS.NET it ends up putting the following entry in the manifest
.mresource public DefaultNamespace.Folder1.Folder2.DefaultNamespace.Folder1.Folder2.File.xml
{
}
I don't want my NAnt build to put different resource names in the manifest than the VS.NET build does. I don't want to have to put all of the XML files at the root of the project with their namespace name in the file name. Is this a bug or am I just using NAnt (version 0.84) incorrectly?
Any help would be greatly appreciated! Thanks!
Mike Doerfler
_________________________________________________________________
Don’t worry if your Inbox will max out while you are enjoying the holidays. Get MSN Extra Storage! http://join.msn.com/?PAGE=features/es
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
