geeyef

Yes, it was the streaming file. It's working now.  Happened several times in a row for me but it's ok now.

This video is corrupted.  It dies right at 8:16

Does Ping have enough active followers for you guys to reach 500 new followers each?  Maybe you should get some funding from one of the marketing departments and go on a C9 campaign trail, complete with a bus 

Wow, Paul.  You are an ultra geek.

I'm following Paul.  Laura's got big talk but does she have a cool music video?  I think not.

The two of you are completely insane, which is the only reason I watch the show.  At first I tuned in (somewhere in the 40s) to get the scoop on MS tech stuff then I realized it was so much more fun to watch you make fools of yourselves... in a good way of course

It's amazing how many people will comment for free swag.  Keep it coming.

Oh yeah, congrats on reaching 100!!!

@STL: Thanks for another great lecture.

> Is there anything else that people want to see?

Aside from what you've just mentioned, I'd like clarification on using r-value reference.  MSDN help doesn't really show how to use it effectively, just syntactically.

I'm trying to use unique_ptr but have run into a snag.  When I declare a unique_ptr in a container in a class that is exported I get an error:

using namespace std;

 
class __declspec( dllexport ) T
{
public:
 
    //unique_ptr<int> i;
    vector<unique_ptr<int>> v;
};

The error is as follows:

  error C2248: 'std::unique_ptr<_Ty>::operator =' :
      cannot access private member declared in class 'std::unique_ptr<_Ty>'

Oddly enough, if add in the line that is currently commented out the error goes away.

fyi, I'm also getting a warning that vector and unique_ptr need to have dll-interface to be used by clients, but I don't think that's a probelm since my clients will be linking with STL anyway:

warning C4251: 'T::v' : class 'std::unique_ptr<_Ty>'
     needs to have dll-interface to be used by clients of class 'T'