View Complete Post
With mutation testing, the system under test is changed to create a faulty version called a mutant. Here James McCaffrey explains how to do this in .NET.
MSDN Magazine April 2006
I have created an application in which there are few forms. Each form has fields which are linked to a backend table/tables. My application is supposed to be accessed by multiple users concurrently. I ran a test where I created a class file in windows application and i ran a for loop in it to call the url of my application. I wanted to test the effect of firing around 200 queries to my query engine.
The test code is :
After updating to .NET Framework 4.0 we have got some random crashes in our production environmnent.
We get a error in clr.dll but having problem to finding the root error. Do you have some tips and tricks?
The event logg looks like this:
Event Type: Error
Event Source: .NET Runtime 4.0 Error Reporting
Event Category: None
Event ID: 1000
Time: 12:45:08 AM
Computer: [The Computer]
Faulting application [TheApplication.exe], version 188.8.131.52, stamp 4c934361, faulting module clr.dll, version 4.0.30319.1, stamp 4ba1d9ef, debug? 0, fault address 0x00003e54.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e
I install vs2010 first in my system , and i used vs2010 to build one solution create by vs 2008 which was build and run very well, but there are some error. and days later, i install vs 2008, try to rebuilt it using vs 2008, but it warms that System.Xaml
was missing, I can only find a image in the folder of framework 4.0, and can't find one in the folder 3.5. I try to add reference path of 4.0 to projects, but just got more warns and the solution can be built through.
How can solve this issue?
I realize that this may sound like a bit of a dumb question, but here goes anyway...
ÃÂ Several months ago, I downloaded and installed the Visual Basic trial thinking that that was the program that I needed.ÃÂ As it turns out I have decided farm this part of my project out toÃÂ a professional, rather than spending countless hours frustrated with attempting to do it myself.ÃÂ At the time that I installed Visual Basic I was asked to .NET Framework 2.0ÃÂ I have since installed two updates, version 3.0 & 3.5.ÃÂ These programs are quite memory intensive and take up a great deal of hard drive space!ÃÂ I am currently running WinXP on my Intel-based MacBookPro under Bootcamp.ÃÂ Unfortunately, the way that the original Bootcamp beta version partitioned my hard drive, it only allows for 32 GB of my hard disk to be allocated to running WinXP This includes any & all applications, documents, etc... that you would by definition have on your computer!ÃÂ AsÃÂ it stands currently, the .NET Framework applications are occupying 0.5 gigabytes of my hard drive. Do I need to keep version 2.0 as well as versions 3.0 and 3.5?ÃÂ Also, since I had no longer using Visual Basic, do I even need to keep the .NET framework on my system at all?Thank you so much for your help!!!dftmweb
I'm using Remoting in a .NET 3.5 framework application of mine (running on windows 2008 r2). I'm opening port 8086 with the following code
BinaryServerFormatterSinkProvider serverProv = new BinaryServerFormatterSinkProvider();
serverProv.TypeFilterLevel = System.Runtime.Serialization.Formatters.TypeFilterLevel.Full;
BinaryClientFormatterSinkProvider clientProv = new BinaryClientFormatterSinkProvider();
IDictionary props = new Hashtable();
props["port"] = 8086
TcpChannel channel = new TcpChannel(props, clientProv, serverProv);
typeof(Remote), "Remote", WellKnownObjectMode.Singleton);
catch (Exception ex)
logger.Error("Failed to intialize service remoting: ", ex);
For some reason, when i restart my windows service that has the above code running, it throws an exception saying that "Only one usage of each socket address (protocol/network address/port) is normally permitted". Digging into this a little deaper it turns
out that "System" process is holding on to my port and it won't let it go. Even if i kill my process, the "System" process still owns the port.
string assemblyName = "MyAssembly";
string moduleName = "MyAssembly.dll";
string typeName = "MyType";
AssemblyName assemblyFullName = new AssemblyName(assemblyName);
AssemblyBuilder assemblyBuilder = AppDomain.CurrentDomain.DefineDynamicAssembly(assemblyFullName, AssemblyBuilderAccess.Run);
ModuleBuilder module = assemblyBuilder.DefineDynamicModule(moduleName);