I ran across this and was wondering if someone could explain why this works in VB.NET when I would expect it should fail, just like it does in C# //The C# Version struct Person { public string name; } ... Person someone = null; //Nope! Can't do that!! Person? someoneElse = null; //No problem, just like expected But then in VB.NET...
As I understand things, the Scrum backlog is composed of a series of Stories that represent something for the end user and this is further decomposed into Features. If this is the case, where does all the behind the scenes features go that aren't really linked to a story but are still useful? For example, say I'm making an application ...
We're building a kiosk app that will have a fairly wide deployment. The app is in Flash running in a browser and requires the use of the webcam. As it stands, each kiosk will show the usual Flash "do you want to allow the use of your camera/microphone" dialog, which I suppose a local admin could click through, choose "remember," etc. Gi...