OpenSAML user discussion

Thanks Scott, I've been fiddling around myself, and just removed the 
SAML_EXPORTS from the Iterator and ArrayIterator definitions and it seems to 
have resolved the issue also.  Since they are being exported out by the 
declarations a little further down in the code, it doesn't seem to have had 
an impact.

I used this msdn bit

------------------
'identifier' : definition of dllimport function not allowed

Data, static data members, and functions can be declared as dllimports but 
not defined as dllimports. The following sample generates C2491:

        // C2491.cpp
        // function definition
        void __declspec(dllimport) funcB() {   // C2491
        }

        // function declaration
        void __declspec(dllimport) funcB();    // ok

------------------

and this article for initial investigation into the matter :)

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q168/9/58.asp&NoWebContent=1
> > You could try moving the implementations into the Iterator.cpp file, but I
> > think that might cause other problems.
> 
> I ran a quick rebuild with 6.0 with all the actual member function
> definitions moved into Iterator.cpp and it appears to generate the same code
> (the DLL's the same size anyway).
> 
> I'll have to try some gcc builds to see if it causes problems there before I
> commit that change to cvs, but it might in fact get you past this bug.
> 
> -- Scott
>