Error message from SSIS:
Warning: 0x80019002 at File Loader - Trans Package - Invoice: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (3); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Skit from Holy Grail:
Then, shalt thou count to three. No more. No less. Three shalt be the number thou shalt count, and the number of the counting shall be three. Four shalt thou not count, nor either count thou two, excepting that thou then proceed to three. Five is right out. Once the number three, being the third number, be reached, then, lobbest thou thy Holy Hand Grenade of Antioch towards thy foe, who, being naughty in My sight, shall snuff it.
Only their hairdresser knows for sure.
As part of my work at OmniPath, I need to create an LDAP provider that confirms credentials if they are not already in the ASP.NET Membership system. It seems that ADAM is the pathway to this, but I bet there are a bunch of tools out there that already will do this for me, maybe even already set up for Community Server. When I was at the Community Server Developers Conference last month, I talked to a few people that had done this, but did I write down their email? Nooooo.... Anyway, that's the next job that I need to look at.
Boy, it's nice to be back writing random thoughts in to a blogging engine. How did I not do this for the last four months?
A client reminded me of a project that we did together ten years ago that revolved around tracking scope points into requirements into designs into test plans. It was very slick. There was a way for people to comment on the document remotely, and then the author could mark down comments and accept the changes, and only the unhandled comments would be taken to the quality gate meetings.
Sound familiar? Sharepoint and Office 2007.
So, I am going to look at renewing that project using contemporary technology. There is a lot of stuff already out there - with a good set of templates, I bet I won't even have to write any code! W00t! Looking forward to that.
I am officially tired of the C# versus VB sniping, folks.
C# is just Microsoft's way of making code bigots program in VB.
Let's face the facts. VB has traditionally brought three things to the table that couldn't easily be accomplished in ASM or C++ or Java or whatever:
A ubiquitous runtime library
Guess what C# has. You guessed it.
The .NET Framework
Just. Like. VB.
I don't want to hear any more crap. Neither language is better, just as Blue isn't better than Green. They are both languages, they do the same thing, they compile to IL, there is no effective difference.
Want to impress me? Use both. Or write in C++. C# programmers don't impress me. I used it for three years and switched to VB because I like it better. Not because it is better, because I like it better.
There, I feel a lot better. Don't you??