packetnet-devel Mailing List for Packet.Net
Brought to you by:
chrismorgan
Menu
▾
▴
packetnet-devel — Development mailing list
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
(22) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Chris M. <chm...@gm...> - 2013-08-25 12:13:52
|
Hi Max. You can email me directly if you don't want to subscribe to the mailing list. How are you using this null packet? I didn't see any changes to Packet.cs to add the null packet type to the parsing list of link layer types so I wanted to ask. Chris On Aug 25, 2013, at 8:03 AM, Max Maton <ma...@ma...> wrote: > Hi, > > I was trying to parse raw ip packets with PacketDotNet and noticed > that the null LinkLayer encapsulation was not yet implemented. > Attached is a patch that adds this functionality. > > Thanks for writing this! > > Max Maton > <0001-Added-Null-LinkLayer-packet-encapsulation-type.patch> > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel |
|
From: Max M. <ma...@ma...> - 2013-08-11 00:16:34
|
Hi, I was trying to parse raw ip packets with PacketDotNet and noticed that the null LinkLayer encapsulation was not yet implemented. Attached is a patch that adds this functionality. Thanks for writing this! Max Maton |
|
From: Chris M. <chm...@gm...> - 2010-03-22 02:00:21
|
Applied. Chris On Sun, Mar 21, 2010 at 5:02 AM, Evan Plaice <eva...@gm...> wrote: > Commit 4 - Changed ComputeChecksum's parameter from bool to > TransportChecksumOption > > Added > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel > > |
|
From: Evan P. <eva...@gm...> - 2010-03-21 10:02:17
|
Commit 4 - Changed ComputeChecksum's parameter from bool to TransportChecksumOption Added |
|
From: Chris M. <chm...@gm...> - 2010-03-20 03:11:09
|
All applied btw.
Chris
On Fri, Mar 19, 2010 at 10:08 PM, Chris Morgan <chm...@gm...> wrote:
> Fyi, in patch 2 you have code like:
>
> + log.Debug("ValidUDPChecksum");
>
>
> Part of the log4net output is the full class and method name/property
> so specifying the property name again is a bit redundant.
>
> Your patches keep having trailing whitespace and tabs in them. Have
> you configured monodevelop to use spaces only?
>
> Chris
>
>
> On Fri, Mar 19, 2010 at 9:55 PM, Evan Plaice <eva...@gm...> wrote:
>> Commit 1 - Modified CalculateUDPChecksum to work identically to
>> CalculateTCPChecksum
>>
>> Added
>>
>> Commit 2 - Added properties to UdpPacket to test Checksum Validity
>>
>> Added
>>
>> Commit 3 - Added a Unit test to check UDP Checksumming
>>
>> Added
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Packetnet-devel mailing list
>> Pac...@li...
>> https://lists.sourceforge.net/lists/listinfo/packetnet-devel
>>
>>
>
|
|
From: Chris M. <chm...@gm...> - 2010-03-20 03:09:07
|
Fyi, in patch 2 you have code like:
+ log.Debug("ValidUDPChecksum");
Part of the log4net output is the full class and method name/property
so specifying the property name again is a bit redundant.
Your patches keep having trailing whitespace and tabs in them. Have
you configured monodevelop to use spaces only?
Chris
On Fri, Mar 19, 2010 at 9:55 PM, Evan Plaice <eva...@gm...> wrote:
> Commit 1 - Modified CalculateUDPChecksum to work identically to
> CalculateTCPChecksum
>
> Added
>
> Commit 2 - Added properties to UdpPacket to test Checksum Validity
>
> Added
>
> Commit 3 - Added a Unit test to check UDP Checksumming
>
> Added
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Packetnet-devel mailing list
> Pac...@li...
> https://lists.sourceforge.net/lists/listinfo/packetnet-devel
>
>
|
|
From: Chris M. <chm...@gm...> - 2010-03-20 03:06:52
|
Applied. We really need to get rid of that boolean parameter to CalculateChecksum(). Can't tell what true vs. false means looking at the code without looking up the method definition. Chris On Fri, Mar 19, 2010 at 9:38 PM, Evan Plaice <eva...@gm...> wrote: > Added a few more patches to complete the updates to TCP/IP checksumming > > Commit 8: Add Checksum abstract to TransportPacket.cs for extensability > > Added > > Commit 9: Modify CalculateTcpChecksum to integrate the Checksum property and > simplify code > > Added > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel > > |
|
From: Evan P. <eva...@gm...> - 2010-03-20 02:55:34
|
Commit 1 - Modified CalculateUDPChecksum to work identically to CalculateTCPChecksum Added Commit 2 - Added properties to UdpPacket to test Checksum Validity Added Commit 3 - Added a Unit test to check UDP Checksumming Added |
|
From: Evan P. <eva...@gm...> - 2010-03-20 02:38:09
|
Added a few more patches to complete the updates to TCP/IP checksumming Commit 8: Add Checksum abstract to TransportPacket.cs for extensability Added Commit 9: Modify CalculateTcpChecksum to integrate the Checksum property and simplify code Added |
|
From: Chris M. <chm...@gm...> - 2010-03-20 02:06:28
|
Applied. The only warnings were from trailing whitespace. I thought monodevelop might be able to do this but I don't see the option right now. Chris On Fri, Mar 19, 2010 at 5:51 PM, Evan Plaice <eva...@gm...> wrote: > Commit 1: Forked ComputeTCPChecksum into UpdateTCPChecksum and > CalculateTCPChecksum > > Resubmitted > > Commit 4: Move Transport Checksumming to TransportPacket.cs > > Resubmitted > > Commit 5: Change all Compute[x]() to Calculate[x]() > > Resubmitted > > Commit 6: Shortened names on Transport Layer methods to eliminate excess > verbosity > > Resubmitted > > Commit 7: Forked CalculateUDPChecksum into UpdateUDPChecksum and > CalculateUDPChecksum > > Added > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel > > |
|
From: Evan P. <eva...@gm...> - 2010-03-19 22:52:04
|
Commit 1: Forked ComputeTCPChecksum into UpdateTCPChecksum and CalculateTCPChecksum Resubmitted Commit 4: Move Transport Checksumming to TransportPacket.cs Resubmitted Commit 5: Change all Compute[x]() to Calculate[x]() Resubmitted Commit 6: Shortened names on Transport Layer methods to eliminate excess verbosity Resubmitted Commit 7: Forked CalculateUDPChecksum into UpdateUDPChecksum and CalculateUDPChecksum Added |
|
From: Chris M. <chm...@gm...> - 2010-03-14 05:45:24
|
Patch 0001 doesn't apply for me. Git complains about conflicts on line 425 of TcpPacket.cs. 0002 and 0003 are applied. Chris On Sun, Mar 14, 2010 at 12:41 AM, Chris Morgan <chm...@gm...> wrote: > On Sun, Mar 14, 2010 at 12:05 AM, Evan Plaice <eva...@gm...> wrote: >> Commit 1: Fix Checksum updates >> >> TCPPacket.cs >> * Remove the logic fork from CalculateChecksum >> * Add UpdateChecksum to handle internal updates >> >> Commit 2: Cleanup IP Checksum Operations >> >> IpPacket.cs >> * Remove ValidIPChecksum abstract >> * IP checksums only apply to IPv4 >> * Remove UpdateIPChecksum abstract >> * IP checksums only apply to IPv4 >> * Remove ComputeIPChecksum abstract >> * IP checksums only apply to IPv4 >> >> IPv6Packet.cs >> * Remove ValidIPChecksum >> * IPv6 does not implement checksums >> *Remove UpdateIPChecksum >> * IPv6 does not implement checksums >> * Remove ComputeIPChecksum >> * IPv6 does not implement checksums >> >> IPv4Packet.cs >> * ValidIPChecksum override removed >> * Abstract no longer exists in IpPacket.cs >> * ComputeIPChecksum override removed >> * Abstract no longer exists in IpPacket.cs >> * UpdateIPChecksum override removed >> * Abstract no longer exists in IpPacket.cs >> >> TcpPacket.cs >> * Fixed ValidChecksum property >> * Only checks the IPChecksum of IPv4 packets now >> >> Commit 3: Join TcpPacket.cs to TransportPacket.cs >> >> TcpPacket.cs >> Make a subclass of TransportPacket.cs >> >> Commit 4: Move Transport Checksumming to TransportPacket.cs >> >> TransportPacket.cs >> * Added preprocessor directive to enable logging without crashing the build >> * Moved IsValidTransportLayerChecksum from IPPacket.cs >> * Moved ComputeTransportLayerChecksum from IPPacket.cs >> * Added using MiscUtil.Conversion >> * Need for EndianBitConverter >> * Renamed IsValidTransportLayerChecksum to IsValidChecksum >> * Renamed for simplicity >> * Renamed ComputeTransportLayerChecksum to ComputeChecksum >> * Renamed for simplicity >> >> IpPacket.cs >> * Changed access level of AttachPseudoHeader to public >> * Removed IsValidTransportLayerChecksum >> * Method is Transport Layer specific, therefore it should be in >> TransportPacket.cs >> * Removed ComputeTransportLayerChecksum >> * Method is Transport Layer specific, therefore it should be in >> TransportPacket.cs >> >> IPv4Packet.cs >> * Changed access level of AttachPseudoHeader to public >> >> IPv6Packet.cs >> * Changed access level of AttachPseudoHeader to public >> >> Commit 5: Change all Compute[x]() to Calculate[x]() >> >> IPv4Packet.cs >> * Renamed ComputeIPChecksum to CalculateIPChecksum >> * Renamed to match common naming convention >> * Updated comments to reflect changes >> * Updated method calls to reflect changes >> >> TransportPacket.cs >> * Renamed ComputeChecksum to CalculateChecksum >> * Renamed to match common naming convention >> * Updated comments to reflect changes >> * Updated method calls to reflect changes >> >> TcpPacket.cs >> * Updated method calls to reflect changes >> IpPacket.cs >> * Updated Comments to reflect changes >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Packetnet-devel mailing list >> Pac...@li... >> https://lists.sourceforge.net/lists/listinfo/packetnet-devel >> >> > > The subject name of the first patch isn't very descriptive. Plus you > are renaming methods in the same patch that you are changing the > logic. You've really got to stop mixing the two but patch 0001 will go > in. > > Patch 0002 looks like a good reduction in total lines of code. > > The subject for patch 0003 isn't very accurate. I'll fix it before > applying it since "join" isn't really a commonly used term when > describing inheritance. > > Why are you exposing the AttachPseudoIPHeader() methods as public? If > those aren't intended to be called by the end user then its best to > keep them hidden by marking them as something other than public. > > Patch 0005 looks good. > > > So 0004 is going to be holding up patch 0005. I'll apply the rest > right now. The Packet.Net api has to be carefully controlled. Users > should be presented with the minimal number of properties, methods and > constructors that they need and I didn't see the justification for > exposing the pseudo header methods to them. > > Chris > |
|
From: Chris M. <chm...@gm...> - 2010-03-14 05:41:58
|
On Sun, Mar 14, 2010 at 12:05 AM, Evan Plaice <eva...@gm...> wrote: > Commit 1: Fix Checksum updates > > TCPPacket.cs > * Remove the logic fork from CalculateChecksum > * Add UpdateChecksum to handle internal updates > > Commit 2: Cleanup IP Checksum Operations > > IpPacket.cs > * Remove ValidIPChecksum abstract > * IP checksums only apply to IPv4 > * Remove UpdateIPChecksum abstract > * IP checksums only apply to IPv4 > * Remove ComputeIPChecksum abstract > * IP checksums only apply to IPv4 > > IPv6Packet.cs > * Remove ValidIPChecksum > * IPv6 does not implement checksums > *Remove UpdateIPChecksum > * IPv6 does not implement checksums > * Remove ComputeIPChecksum > * IPv6 does not implement checksums > > IPv4Packet.cs > * ValidIPChecksum override removed > * Abstract no longer exists in IpPacket.cs > * ComputeIPChecksum override removed > * Abstract no longer exists in IpPacket.cs > * UpdateIPChecksum override removed > * Abstract no longer exists in IpPacket.cs > > TcpPacket.cs > * Fixed ValidChecksum property > * Only checks the IPChecksum of IPv4 packets now > > Commit 3: Join TcpPacket.cs to TransportPacket.cs > > TcpPacket.cs > Make a subclass of TransportPacket.cs > > Commit 4: Move Transport Checksumming to TransportPacket.cs > > TransportPacket.cs > * Added preprocessor directive to enable logging without crashing the build > * Moved IsValidTransportLayerChecksum from IPPacket.cs > * Moved ComputeTransportLayerChecksum from IPPacket.cs > * Added using MiscUtil.Conversion > * Need for EndianBitConverter > * Renamed IsValidTransportLayerChecksum to IsValidChecksum > * Renamed for simplicity > * Renamed ComputeTransportLayerChecksum to ComputeChecksum > * Renamed for simplicity > > IpPacket.cs > * Changed access level of AttachPseudoHeader to public > * Removed IsValidTransportLayerChecksum > * Method is Transport Layer specific, therefore it should be in > TransportPacket.cs > * Removed ComputeTransportLayerChecksum > * Method is Transport Layer specific, therefore it should be in > TransportPacket.cs > > IPv4Packet.cs > * Changed access level of AttachPseudoHeader to public > > IPv6Packet.cs > * Changed access level of AttachPseudoHeader to public > > Commit 5: Change all Compute[x]() to Calculate[x]() > > IPv4Packet.cs > * Renamed ComputeIPChecksum to CalculateIPChecksum > * Renamed to match common naming convention > * Updated comments to reflect changes > * Updated method calls to reflect changes > > TransportPacket.cs > * Renamed ComputeChecksum to CalculateChecksum > * Renamed to match common naming convention > * Updated comments to reflect changes > * Updated method calls to reflect changes > > TcpPacket.cs > * Updated method calls to reflect changes > IpPacket.cs > * Updated Comments to reflect changes > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel > > The subject name of the first patch isn't very descriptive. Plus you are renaming methods in the same patch that you are changing the logic. You've really got to stop mixing the two but patch 0001 will go in. Patch 0002 looks like a good reduction in total lines of code. The subject for patch 0003 isn't very accurate. I'll fix it before applying it since "join" isn't really a commonly used term when describing inheritance. Why are you exposing the AttachPseudoIPHeader() methods as public? If those aren't intended to be called by the end user then its best to keep them hidden by marking them as something other than public. Patch 0005 looks good. So 0004 is going to be holding up patch 0005. I'll apply the rest right now. The Packet.Net api has to be carefully controlled. Users should be presented with the minimal number of properties, methods and constructors that they need and I didn't see the justification for exposing the pseudo header methods to them. Chris |
|
From: Chris M. <chm...@gm...> - 2010-03-11 02:19:15
|
Hi Evan. Thank you for the patch. I'm going to strip off the changes to TcpPacket.ComputeTCPChecksum() though since they have nothing to do with fixing the checksum. If you could separate patches by their function they would be more modular and isolated. Chris On Wed, Mar 10, 2010 at 8:58 PM, Evan Plaice <eva...@gm...> wrote: > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel > > |
|
From: Chris M. <chm...@gm...> - 2010-03-04 01:31:14
|
If you want to take a look at the checksum issue that would be cool. I didn't really have much interest in debugging it at this point so have at it :-) Chris On Wed, Mar 3, 2010 at 8:19 PM, Chris Morgan <chm...@gm...> wrote: > Alright, all three of these are applied. Thanks man. > > I modified the one nunit patch to remove the "using System.XML;" > because that entry is only necessary if code needed it, it isn't > related to the missing reference to System.XML. > > Chris > > > On Wed, Mar 3, 2010 at 9:07 AM, Chris Morgan <chm...@gm...> wrote: >> Hi Evan. >> >> I can view these patches now. >> >> Sorry about not making the changes last night, I'll apply them as soon >> as I get home today because they are all perfectly reasonable things >> to fix. >> >> Chris >> >> >> >> On Mar 3, 2010, at 6:10 AM, Evan Plaice <eva...@gm...> wrote: >> >>> Resubmitting the NUnit fix for windows patch as well as the >>> Array.Copy vs Buffer.BlockCopy patch due to Windows end line conficts. >>> >>> Also added a patch to ignore unnecessary files generated by Visual >>> Studio. >>> >>> Patch 0001: >>> Modified .gitignore to exclude >>> - /obj/ folders and sub-folders which contain object files, >>> binaries, and dll files generated from build/debug >>> - .suo files which contain user-specific settings specific to Visual >>> Studio >>> >>> Patch 0002: >>> Fixed NUnit to work with Visual Studio >>> - Everything compiled fine before changing the methods to public but >>> all of the tests would crash using NUnit 2.5.3. >>> This is the error given on all of the tests: >>> Invalid signature for SetUp or TearDown method: RunBeforeAnyTests >>> >>> - log4net was needed System.Xml, so I added a using statement and a >>> reference to Test.csproj >>> Without this Test would not compile >>> >>> Patch 0003: >>> ByteCopyPerformance test added: >>> - This test compares Buffer.BlockCopy to Array.Copy >>> >>> Evan Plaice >>> <0001-.gitignore-entries-added-for-Visual-Studio.patch> >>> <0002-NUnit-Testing-fixed-in-Windows.patch> >>> <0003-ByteCopyPerformance-test-added.patch> >>> --- >>> --- >>> --- >>> --------------------------------------------------------------------- >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Packetnet-devel mailing list >>> Pac...@li... >>> https://lists.sourceforge.net/lists/listinfo/packetnet-devel >> > |
|
From: Chris M. <chm...@gm...> - 2010-03-04 01:20:06
|
Alright, all three of these are applied. Thanks man. I modified the one nunit patch to remove the "using System.XML;" because that entry is only necessary if code needed it, it isn't related to the missing reference to System.XML. Chris On Wed, Mar 3, 2010 at 9:07 AM, Chris Morgan <chm...@gm...> wrote: > Hi Evan. > > I can view these patches now. > > Sorry about not making the changes last night, I'll apply them as soon > as I get home today because they are all perfectly reasonable things > to fix. > > Chris > > > > On Mar 3, 2010, at 6:10 AM, Evan Plaice <eva...@gm...> wrote: > >> Resubmitting the NUnit fix for windows patch as well as the >> Array.Copy vs Buffer.BlockCopy patch due to Windows end line conficts. >> >> Also added a patch to ignore unnecessary files generated by Visual >> Studio. >> >> Patch 0001: >> Modified .gitignore to exclude >> - /obj/ folders and sub-folders which contain object files, >> binaries, and dll files generated from build/debug >> - .suo files which contain user-specific settings specific to Visual >> Studio >> >> Patch 0002: >> Fixed NUnit to work with Visual Studio >> - Everything compiled fine before changing the methods to public but >> all of the tests would crash using NUnit 2.5.3. >> This is the error given on all of the tests: >> Invalid signature for SetUp or TearDown method: RunBeforeAnyTests >> >> - log4net was needed System.Xml, so I added a using statement and a >> reference to Test.csproj >> Without this Test would not compile >> >> Patch 0003: >> ByteCopyPerformance test added: >> - This test compares Buffer.BlockCopy to Array.Copy >> >> Evan Plaice >> <0001-.gitignore-entries-added-for-Visual-Studio.patch> >> <0002-NUnit-Testing-fixed-in-Windows.patch> >> <0003-ByteCopyPerformance-test-added.patch> >> --- >> --- >> --- >> --------------------------------------------------------------------- >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Packetnet-devel mailing list >> Pac...@li... >> https://lists.sourceforge.net/lists/listinfo/packetnet-devel > |
|
From: Chris M. <chm...@gm...> - 2010-03-03 14:08:16
|
Hi Evan. I can view these patches now. Sorry about not making the changes last night, I'll apply them as soon as I get home today because they are all perfectly reasonable things to fix. Chris On Mar 3, 2010, at 6:10 AM, Evan Plaice <eva...@gm...> wrote: > Resubmitting the NUnit fix for windows patch as well as the > Array.Copy vs Buffer.BlockCopy patch due to Windows end line conficts. > > Also added a patch to ignore unnecessary files generated by Visual > Studio. > > Patch 0001: > Modified .gitignore to exclude > - /obj/ folders and sub-folders which contain object files, > binaries, and dll files generated from build/debug > - .suo files which contain user-specific settings specific to Visual > Studio > > Patch 0002: > Fixed NUnit to work with Visual Studio > - Everything compiled fine before changing the methods to public but > all of the tests would crash using NUnit 2.5.3. > This is the error given on all of the tests: > Invalid signature for SetUp or TearDown method: RunBeforeAnyTests > > - log4net was needed System.Xml, so I added a using statement and a > reference to Test.csproj > Without this Test would not compile > > Patch 0003: > ByteCopyPerformance test added: > - This test compares Buffer.BlockCopy to Array.Copy > > Evan Plaice > <0001-.gitignore-entries-added-for-Visual-Studio.patch> > <0002-NUnit-Testing-fixed-in-Windows.patch> > <0003-ByteCopyPerformance-test-added.patch> > --- > --- > --- > --------------------------------------------------------------------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Packetnet-devel mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetnet-devel |
7 messages has been excluded from this view by a project administrator.
