[nant-dev] ILASM Task
Hi all, are there any plans to implement the ILASM task? j3d. Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] ILASM Task
Its a good idea. Do you feel like taking a stab at it ? Ian Giuseppe Greco wrote: Hi all, are there any plans to implement the ILASM task? j3d. Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers -- Ian MacLean, Developer, ActiveState, a division of Sophos http://www.ActiveState.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] ILASM Task
Not immediately because I'm currently under pressure... I'll give a look at it as soon as possible. j3d. Its a good idea. Do you feel like taking a stab at it ? Ian Giuseppe Greco wrote: Hi all, are there any plans to implement the ILASM task? j3d. Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers -- Ian MacLean, Developer, ActiveState, a division of Sophos http://www.ActiveState.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] Case sensitive error in CompilerBase.cs GetManifestResourceName
Hello everyone. I'm new to this, so please bear with me.
I found what I believe to be a bug in NAnt, regarding compiling .resx
files to .resources files. Specifically, if the .resx file is really a
.resX file (ie, the case is not all lower), the output file will not
be created as a .resources file, leading to all kinds of problems
later on.
I fixed this error in my local copy by doing the following: in
NAnt.DotNet\Tasks\CompilerBase.cs, line 549 (in
GetManifestResourceName), I changed:
// determine the resource type
switch (Path.GetExtension(resourceFile)) {
case .resx:
to:
// determine the resource type
switch (Path.GetExtension(resourceFile).ToLower()) {
case .resx:
This worked for me -- NAnt built, tested, and ran just fine, and
equally important, I could then compile solutions that had strange
cases in the extensions of .resx files.
I don't know the proper way to put this change forward to the NAnt
team, so I'm just putting it here on the mailing list. If this is
wrong, please accept my apologies, and let me know what I should do
next.
Thanks,
Jeff Paulsen
---
This SF.Net email sponsored by Black Hat Briefings Training.
Attend Black Hat Briefings Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
