Search Results

Search found 5 results on 1 pages for 'flynn1179'.

Page 1/1 | 1 

• Windows boots to Black Screen of Death — Is my HDD faulty?

  - by Flynn1179

  My wife's PC suddenly stopped booting up properly. It gets as far as the Windows 'loading' screen with the bar scrolling away, but that's as far as it gets for some time, then suddenly flashes up a BSoD barely long enough to see, then the display cuts out. We've got identical PCs, and after swapping components, I established that my PC suffers the same problem if I swap in the HDD. Even if I plug hers in as a second HDD on my machine, it still does the same thing, even though it's booting from mine. I can't even boot her machine from CD or DVD either, so I couldn't even use a recovery disc. I did manage to partially boot my PC into safe mode with the other HDD attached, and it got as far as loading 'crcdisk.sys' and froze. Anybody know what could be wrong with it, or at least how I can get the data off the disk? I'm assuming there's still data on the disk, given that it at least shows me the vista 'loading' screen.

  Read the article

• Stack Overflow problem transforming with a custom xslt

  - by Flynn1179

  I've got a system that allows the user the option of providing their own XSLT to apply to some data that's been retrieved, as a means of specifying how that data should be presented. However, if the user includes code in the XSLT equivalent to: <xsl:template match="/"> <xsl:element name="data"> <xsl:apply-templates select="." /> </xsl:element> </xsl:template> this causes .NET to infinitely recurse trying to process it, and produces a stack overflow error. I need to be able to trap this before it crashes the app, as the data that's been retrieved is occasionally quite time-consuming to obtain, and the data is lost when this happens. Is there any way of doing this? I know it's theoretically possible to identify any occurrences of xsl:apply-templates with "." in the select attribute, but this isn't the only way an infinite recursion could happen, I need a way of generically trapping it.

  Read the article

• What's the best way to unit test code that generates random output?

  - by Flynn1179

  Specifically, I've got a method picks n items from a list in such a way that a% of them meet one criterion, and b% meet a second, and so on. A simplified example would be to pick 5 items where 50% have a given property with the value 'true', and 50% 'false'; 50% of the time the method would return 2 true/3 false, and the other 50%, 3 true/2 false. Statistically speaking, this means that over 100 runs, I should get about 250 true/250 false, but because of the randomness, 240/260 is entirely possible. What's the best way to unit test this? I'm assuming that even though technically 300/200 is possible, it should probably fail the test if this happens. Is there a generally accepted tolerance for cases like this, and if so, how do you determine what that is?

  Read the article

• Constructing mocks in unit tests

  - by Flynn1179

  Is there any way to have a mock constructed instead of a real instance when testing code that calls a constructor? For example: public class ClassToTest { public void MethodToTest() { MyObject foo = new MyObject(); Console.WriteLine(foo.ToString()); } } In this example, I need to create a unit test that confirms that calling MethodToTest on an instance of ClassToTest will indeed output whatever the result of the ToString() method of a newly created instance of MyObject. I can't see a way of realistically testing the 'ClassToTest' class in isolation; testing this method would actually test the 'myObject.ToString()' method as well as the MethodToTest method.

  Read the article

• Combining XSLT transforms

  - by Flynn1179

  Is there a way to combine two XSLT documents into a single XSLT document that does the same as transforming using the original two in sequence? i.e. Combining XSLTA and XSLTB into XSLTC such that XSLTB( XSLTA( xml )) == XSLTC( xml )? There's three reasons I'd like to be able to do this: Simplifies development; some operations need sequential transforms, and although I can generate a combined one by hand, it's a lot more difficult to maintain that two much simpler, separate transforms. Speed; one transform is in most cases hopefully faster than two. I'm currently working on a program that literally just transforms a data file in XML into an XHTML page capable of editing it using one XSLT, and a second XSLT that transforms the XHTML page back into the data file when it's saved. One test I hope to be able to do is to combine the two, and easily confirm that the 'combined' XSLT should leave the data unchanged.

  Read the article

1