You're unlikely to get 100% coverage on all methods from a single unit test, you generally need a unit test per path through your code, and probably more on top. As well as the test that tests null arguments and exceptions you need tests that exercise the "happy path" and all other paths until you get 100% coverage. That's just what unit testing is.
Ah, that's a shame. When I open my VS on the Surface, I feel empowered. It really doesn't make much sense, I guess, but now I can code while I commute, while I'm at the coffee shop, or while I'm at my in-laws house ;P
Thank you Aescleal, I think I'll use the void pointer.
Aescleal wrote:
The idea is to have a window class that has a message handler interface pointer but I haven't tried that yet.
I'm trying that just yet, and I have already subclassed some existing common controls to get their WndProc and route the messages accordingly through boost::singal2, but on my own terms. I think this is what Windows.Forms do. Thanks for the help!
Yes, that's what I do, usually a "SP.UI.ModalDialog.showModalDialog parameter options site:msdn.microsoft.com" Google search. MSDN search sucks, I know. Still, this kind of documentation is usually only available at MSDN site, hence having the page down causes problems to good ol' me.
Hello I'm new with Sharepoint, so I may be wrong. I would define a Workflow setting a value every time a document will be changes. This value could be stored for example in a server-file. So your WebPart hasn't to go through all lists and documents - it wil read the value which identifies the newest document. Hope this will help :)
------------------------------ Author of Primary ROleplaying SysTem How do I take my coffee? Black as midnight on a moonless night. War doesn't determine who's right. War determines who's left.
Fernando A. Gomez F. wrote:
MSSQLSVR 2008
I should have read more carefully.. As I read, you did find 'em by now :)
Bastard Programmer from Hell :suss:
No, thanks to you. Really. I remember how CP looked like when I joined back in 2003, and it has changed a lot, and for good. You are way ahead of other sites, including MSDN. :thumbsup: Now, let's all get a beer, first round's on me. :beer:
We may actually be able to do that quite easily, actually. We've been thinking about this a lot over the years and it has it's pros and cons (as John has pointed out, so it'll need some thinking (and, obviously, time ;))
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Yeah you wish ;) actually ... - but that's not the story you expect
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server.
Yep, that did the trick. I found this article[^] that explains how to do it. And although it references VC6 it works quite well in VC9, the only difference being that autoexp.dat file is located at C:\Program Files\Microsoft Visual Studio 9.0\Common7\Packages\Debugger (in my machine, at least). Thanks for the help!
